PERSONAL PRODUCTIVITY

Reminder Loop for Promises Past Due in Linear

Each afternoon it checks Linear for commitment tasks whose due date has passed without being closed.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily afternoon schedule
  • ActionFetch overdue commitment tasksLinearLinear
  • LogicSplit recently overdue vs. 2+ days late
  • ActionDraft tailored nudges, sharper for escalationsOpenAI
  • OutputEmail reminders and flag escalationsGmailGmail

What it does

Capturing a commitment is only half the job; this workflow closes the loop. On a schedule it queries Linear for open tasks tagged as email commitments whose due date is in the past, then sends you a per-item nudge by Gmail. Items overdue by more than two days get an escalated, more urgent reminder.

When to use it

Use it as the enforcement layer on top of any commitment-capture workflow. It is for people who reliably log promises but then let them age silently. Pair it with the ClickUp or Notion capture templates, or point it at any Linear project you treat as a commitment backlog.

How it works

  1. 1A daily afternoon schedule fires the workflow.
  2. 2A Linear action fetches open commitment tasks past their due date.
  3. 3A logic branch splits items into recently overdue versus more than two days late.
  4. 4An OpenAI step drafts a tailored nudge for each item, sharper for the escalated set.
  5. 5A Gmail action sends the reminders to you.
  6. 6The escalation tier is noted back on each Linear issue for tracking.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.