Add a Delay before a follow-up message

This recipe sends an initial Slack message, waits, and then sends a follow-up using the stored Workflow data.

Trigger → Slack: Send Message → Delay → Slack: Send Message

1. Build the immediate route

1. Create a Workflow with a controlled Trigger such as a test Webhook Source.
2. Add Slack → Send Message.
3. Select a test channel and map a stable event or customer identifier into the message.
4. Test the immediate message before adding the wait.

2. Add the Delay

1. Add a Delay after the first Slack Action.
2. Use 60 seconds while testing.
3. After verification, change it to the business interval. The supported range is 1 to 2,592,000 seconds, or 30 days.

When execution reaches the Delay, the run returns to Queued. Long waits are scheduled in chunks without restarting the original elapsed time on each queue delivery.

3. Add the follow-up

Add a second Slack → Send Message after the Delay. Map identifiers from the Trigger or an earlier successful Step. For example:

Follow-up for event {{trigger.body.id}}.
The initial notification was accepted; review the current state before taking action.

The Delay passes its input through unchanged. It does not refresh provider data. If the follow-up must reflect current state, add a provider lookup Action after the Delay and map from that lookup instead.

4. Verify timing and evidence

Activate the Workflow and trigger it once. Confirm:

• The first Slack message arrives immediately.
• Audit shows the Delay Step and a Queued run while time remains.
• The second Action does not execute before the Delay completes.
• The follow-up arrives once and carries the expected event identifier.

Operational considerations

• An account can be revoked and a target channel can disappear during a long wait; connect an error route to the follow-up Action when needed.
• Workflow edits create versioned behavior. Inspect the run's saved version instead of assuming an in-flight run uses the latest graph.
• Delayed side effects can still retry, so keep the follow-up idempotent.
• Use a provider lookup after the Delay when cancellation or already-completed state should suppress the message.

See Workflow delays, Slack integration, and Workflow Audit.