message/getPermalink

When to Use

• Ticket cross-referencing: After posting an incident alert to Slack, retrieve its permalink and store it on the associated Jira issue, PagerDuty incident, or ServiceNow ticket so responders can quickly navigate to the full Slack conversation.
• Audit trail records: When a workflow captures an approval decision via message/sendAndWait, store the permalink to the approval message in an audit log database as proof of the decision context and chain of evidence.
• Email escalation context: Include the Slack message permalink in escalation emails so recipients who prefer email can click directly to the originating Slack discussion without having to search for it.
• Status dashboard links: A operations dashboard displays links to recent Slack messages related to ongoing incidents, deployments, or system events, enabling one-click navigation to the full context.
• Notification threading: Include the permalink to an original announcement in follow-up notifications sent via email or other channels, creating a traceable reference back to the source discussion.

Configuration

Connection

Operation

Sample Configuration

{
  "resource": "message",
  "operation": "getPermalink",
  "botToken": "{{ $credentials.slackBotToken }}",
  "channel": "{{ $output.postAlert.channel }}",
  "messageTs": "{{ $output.postAlert.messageTs }}"
}

Validation Errors

Output

Success Port

Fires with the permanent URL to the message. The permalink is stable as long as the message is not deleted.

Error Port

Fires when the message or channel cannot be found, or the bot lacks channel access.

Sample Output

{
  "permalink": "https://acmecorp.slack.com/archives/C04X9ABCDEF/p1716700412087200",
  "channel": "C04X9ABCDEF",
  "messageTs": "1716700412.087200",
  "status": "ok",
  "errorCode": "",
  "payload": {
    "ok": true,
    "channel": "C04X9ABCDEF",
    "permalink": "https://acmecorp.slack.com/archives/C04X9ABCDEF/p1716700412087200"
  }
}

Expression Reference

Node Policies & GuardRails

Examples

Jira Issue Cross-Reference

// Step 1 — Post incident alert to Slack (message/send node named "postAlert")
{
  "resource": "message",
  "operation": "send",
  "botToken": "{{ $credentials.slackBotToken }}",
  "channel": "C04INCIDENTS",
  "text": "*P1 Incident:* {{ $input.serviceName }} is down"
}

// Step 2 — Get the permalink (message/getPermalink node named "getLink")
{
  "resource": "message",
  "operation": "getPermalink",
  "botToken": "{{ $credentials.slackBotToken }}",
  "channel": "{{ $output.postAlert.channel }}",
  "messageTs": "{{ $output.postAlert.messageTs }}"
}

// Step 3 — Update the Jira issue with the Slack permalink (Jira node)
{
  "resource": "issue",
  "operation": "update",
  "issueKey": "{{ $input.jiraIssueKey }}",
  "fields": {
    "comment": {
      "body": "Slack incident discussion: {{ $output.getLink.permalink }}"
    }
  }
}

A three-step incident intake workflow: post to Slack, retrieve the permalink, then update the corresponding Jira issue with a direct link to the Slack discussion. Responders can navigate between Jira and Slack with a single click.

Approval Audit Record

{
  "resource": "message",
  "operation": "getPermalink",
  "botToken": "{{ $credentials.slackBotToken }}",
  "channel": "{{ $output.waitApproval.channel }}",
  "messageTs": "{{ $output.waitApproval.messageTs }}"
}

After an approval decision is captured via message/sendAndWait, this node retrieves the permalink to the approval message. The permalink is then written to an audit database record alongside the approver ID, decision, and timestamp — providing an immutable link back to the original Slack approval context for compliance audits.

Email Escalation with Slack Context

{
  "resource": "message",
  "operation": "getPermalink",
  "botToken": "{{ $credentials.slackBotToken }}",
  "channel": "C04INCIDENTS",
  "messageTs": "{{ $vars.incidentMessageTs }}"
}

When an incident timeout escalation fires (e.g. no acknowledgement within 15 minutes), this node fetches the permalink to the original Slack incident message. The permalink is then included in the escalation email body so the executive on-call can click directly to the full incident discussion in Slack without needing to search for it.