Short answer: You can cancel scheduled message in Slack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Slack Cancel Scheduled Message action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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. |
{"channel": "e.g. C0123456789","scheduled_message_id": "{{trigger.scheduled_message_id}}"}
{"ok": true,"raw": {}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.