Cancel Scheduled Message: Slack action

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 #.
Scheduled Message ID scheduled_message_id	string	Required	The scheduled_message_id returned by the Schedule Message action.

Sample request

{
  "channel": "e.g. C0123456789",
  "scheduled_message_id": "{{trigger.scheduled_message_id}}"
}

Returns

{
  "ok": true,
  "raw": {}
}

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

FAQ

Questions about Cancel Scheduled Message.

What does the Cancel Scheduled Message action do in Slack?

Cancels a previously-scheduled Slack message before it's sent. Use it when conditions change after a Schedule Message action ran.

What inputs does Cancel Scheduled Message require?

Required: Channel, Scheduled Message ID. 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 Cancel Scheduled Message support batch operations?

Yes. Run Cancel Scheduled 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