download dots
AI WorkflowsCategoriesLinear

⏳ Speak Up When Dated Work Goes Quiet with AI

A due date is set, the flow waits, then reads the linked issue and has an agent comment if nothing has moved.

  • Event-triggered
  • 100+ integrations
  • Branching logic
  • Schedule + monitor
UNIT · TASKADE.FLOW6 STEPS

How this flow runs

When

When a due date is added

Taskade

Then 1

Delay

wait 5 days before checking progress

Wait before continuing. The wait is durable — it survives a restart of the machine running it, so a two-day follow-up still fires.

Then 2

Get Issue

Linear

Then 3

Filter

Continue only if nothing has moved on the issue since the date was set

Stop a run cleanly when a condition is not met. A filtered run is not a failure, so it never shows up as an error — inside a loop it skips just that item and keeps going.

Then 4

Agent

Delivery Watch

Ask an agent · Taskade AI

Knows
your cycle dates, your commitments and who owns each issue
Remembers
which issues have gone quiet before and what unblocked them

Then 5

Add Comment

Linear

This agent carries its knowledge and memory between runs, and can call your other automations as its own tools. How custom agents work

Delay and Filter are steps you add in the builder, in the same list as an app step — there is no separate scripting surface. All automation actions

Build this flow with AI

Opens the builder with these steps already described. Free to start, no card.

What does this automation do?

A due date is set, the flow waits, then reads the linked issue and has an agent comment if nothing has moved.

What can you do with it?

  • Notice the silence instead of remembering to check
  • Wait a real number of days without holding it in your head
  • Leave the nudge on the issue, where the owner will see it

The Steps

This automation runs in 6 steps:

  1. When Taskade — When a due date is added
  2. Then Delay — wait 5 days before checking progress
  3. Then Linear — Get Issue
  4. Then Filter — continue only when nothing has moved on the issue since the date was set
  5. Then Taskade AI — Ask an agent ("Delivery Watch")
  6. Then Linear — Add Comment

What makes this different from a Zapier-style flow?

The "Delivery Watch" step is not a one-off model call. It is a Taskade AI agent that knows your cycle dates, your commitments and who owns each issue, remembers which issues have gone quiet before and what unblocked them, so every run builds on the last one instead of starting from an empty prompt.

A stateless "ask the model" step forgets everything the moment it returns. An agent keeps its knowledge and its memory between runs, carries its own tools, and can be handed work by other automations.

Who is this automation for?

Built for delivery leads chasing dates by hand. A due date is set, the flow waits, then reads the linked issue and has an agent comment if nothing has moved.

How do you set it up?

  • Open the "Automations" tab in your workspace.
  • Click ➕ Add automation, then start from scratch.
  • Add the trigger "When a due date is added" from Taskade.
  • Add a Delay step: Delay — wait 5 days before checking progress.
  • Add the action "Get Issue" from Linear.
  • Add a Filter step: Filter — continue only when nothing has moved on the issue since the date was set.
  • Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Delivery Watch".
  • Add the action "Add Comment" from Linear.
  • Enable the toggle in the top-right corner to activate the automation.

Prefer to describe it instead? Click Build this flow with AI above and Taskade wires the trigger, the steps, and the agent for you.

Related from the blog

Discover more

More Linear Workflows

View all Linear Workflows