ActionSlackUpdated May 2026

How do I schedule a future Slack message?

Short answer: Drop the "Slack → Schedule Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 45 Slack actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Channel channel	string	Required	Slack channel ID (starts with C for public, G for private group, D for DM). Find via List Channels. Not the channel name with #.
Message text	string	Required	Message text to post. Supports Slack mrkdwn (e.g. bold, <@U123> mentions, <#C123> channel links).
Send at post_at	datetime	Required	When to post the message. Must be in the future and within 120 days.

Sample request

{
  "channel": "e.g. C0123456789",
  "text": "e.g. Hello team :wave:",
  "post_at": "{{trigger.post_at}}"
}

Returns

{
  "ok": true,
  "raw": {},
  "channel": "C0123",
  "post_at": 1712925600,
  "scheduled_message_id": "Q1298393284"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Schedule Message.

Any of these apps can fire this action as part of a workflow.

Gmail → Slack

1 Gmail triggers

Google Sheets → Slack

2 Google Sheets triggers

FAQ

Questions about Schedule Message.

What does the Schedule Message action do in Slack?

Schedules a message to be posted to a Slack channel at a future time. Use it for daily stand-ups, reminders, or timed announcements.

What inputs does Schedule Message require?

Required: Channel, Message, Send at. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Slack returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Schedule Message support batch operations?

Yes. Run Schedule Message inside a Loop node to process arrays. Tiny Command handles Slack's rate limits automatically so you don't have to throttle manually.

More actions