ActionSlackUpdated September 2026

How do I get a permalink URL to a Slack message?

Short answer: You can get permalink in Slack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Slack Get Permalink 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.

Get Permalink in Slack — start free All 45 Slack actions

Get Permalink in Slack — start free

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 ID 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 message_ts	string	Required	The 'ts' value of the message

Sample request

{
  "channel": "C1234567890",
  "message_ts": "1234567890.123456"
}

Returns

{
  "ok": true,
  "channel": "C1234567890",
  "permalink": "https://myteam.slack.com/archives/C1234567890/p1234567890123456"
}

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

Triggered by

Apps that pair well as the trigger for Get Permalink.

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 Get Permalink.

What does the Get Permalink action do in Slack?

Retrieves a permanent URL for a specific message in a channel. Used in cross-system links (e.g., adding a Slack message link to a Jira issue).

What inputs does Get Permalink require?

Required: Channel ID, Message Timestamp. 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 run history shows the failed step with its input and the error message Slack returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Permalink support batch operations?

Run Get Permalink inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Slack's rate limits.

More actions