Short answer: You can get message by timestamp in Slack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Slack Get Message by Timestamp 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 #. |
Message Timestamp (ts) timestamp | string | Required | Slack message timestamp (the `ts` field returned when sending or by triggers). |
{"channel": "e.g. C0123456789","timestamp": "1712835600.000100"}
{"ok": true,"raw": {},"text": "Hello team","user": "U0123","thread_ts": null,"timestamp": "1712835600.000100"}
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.