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

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 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 Get Permalink support batch operations?

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