Skip to Content
ReferenceActionsSLACK

Slack Action

The Slack action posts a message to a Slack channel: the notes of a run, a text the workflow writes, or both.

An action can leave notes for people besides whether its step passed, and a later step reads them as notes, with the job and the step of each and the secrets hidden. Probe does not post them anywhere. This action posts them to Slack, so that a team hears of a critical note, or of a failed run on a schedule, where it talks. Posting a message is all it does with Slack.

It is an external action, published in mozership/probe-slack . Probe downloads it the first time a workflow uses it, and runs the executable whose SHA-256 the action.yml at the pinned commit names. It needs Probe v1.32.0 or later, the first with the notes context. The examples write <commit SHA> for the commit to pin: probe guide slack prints the uses line of the latest release, and so do the notes of each release.

Basic Syntax

A step pins the action by a full commit SHA. The notes of each release  start with the uses line to copy. The step belongs to a last job, which needs the others with always, so that it runs once they are over, however they ended, and reads the notes of them all:

name: Nightly actions: slack: github.com/mozership/probe-slack@<commit SHA> secrets: - SLACK_WEBHOOK_URL vars: slack_webhook: "{{SLACK_WEBHOOK_URL}}" jobs: # hello returns what it is given as res, as an action that leaves notes # would return them. - name: Checkout id: checkout steps: - name: A first-time shopper uses: hello with: notes: - level: critical title: The checkout button is under the cookie banner body: On a 390px wide screen the banner covers the button until it is closed. - level: info body: The search took 4s to show results. - name: Tell the team needs: [checkout] always: true steps: - name: Post the critical notes uses: slack with: webhook_url: "{{vars.slack_webhook}}" text: Critical notes of the nightly run notes: "{{ filter(notes, .level == 'critical') }}" test: status == 0

Two Ways to Post

webhook_urltoken and channel
What it isAn Incoming Webhook A bot token with chat:write, for chat.postMessage
The channelThe one the webhook was made forchannel, by id or #name, of those the bot was invited to
What it returnsres.postedres.posted, and res.channel and res.ts of the message

A webhook needs nothing else, and is the way for one channel. A token posts to the channel each step names. Give one of the two, not both, and list the URL of the webhook, or the token, under secrets: the URL of a webhook is all it takes to post to it.

- name: The critical notes, to the channel of the team on call uses: slack with: token: "{{vars.slack_token}}" channel: "#oncall" notes: "{{ filter(notes, .level == 'critical') }}"

Each run posts a new message. The action does not edit one, nor reply in a thread: a message kept up to date for each push belongs on the pull request, with github-notes.

Parameters

ParameterTypeRequiredDefaultDescription
webhook_urlStringOne of the two ways-The URL of an Incoming Webhook
tokenStringOne of the two ways-A bot token with chat:write
channelStringWith token-The channel, by id such as C0123456789 or as #name
textStringtext or notes-Markdown written above the notes, or alone
notesArraytext or notes-Entries of the notes context, such as "{{ notes }}"
api_urlStringNohttps://slack.com/apiThe Web API, for token
timeoutDurationNo30sTime limit for the step, as 10s or a number of seconds

A key that is none of these fails the step. Its action.yml declares them as params, so probe check reports such a key with its line.

When notes is empty and there is no text, nothing is posted, and res.posted is false: a message each night saying a run left no notes is noise. A text with no notes is posted alone, such as to say that a run on a schedule failed.

notes takes entries as the notes context has them; an entry without a level of info, warning or critical, or without a body, fails the step. Give it the context, or a part of it, as filter(notes, .level == 'critical'), rather than a list written by hand.

What It Posts

The message is made of Block Kit markdown blocks, so that the Markdown of a note shows as written: the text, a line counting the notes of each level, and a block for each note with an emoji of its level, its title, its body, and a line naming its job, its step, the status of the step and, for a job with repeat, the run. The workflow above posts:

Critical notes of the nightly run **The run left 1 note: 1 critical.** 🚨 **critical · The checkout button is under the cookie banner** On a 390px wide screen the banner covers the button until it is closed. _Checkout › A first-time shopper · passed_

The plain text of the message holds the same: the text, the line counting the notes, and each note shown, with its level, title, job, step and body. Slack shows it in a notification, and a screen reader reads it in place of the blocks.

A value Probe hides is <secret:NAME> or <redacted> in a note, which Slack would take for a link or a mention, so the action puts it in code, where it shows as it is.

Slack takes at most 50 blocks, and 12000 characters in all the markdown blocks of a message. The last notes of a longer message are left out, and a block says how many. A text too long to fit even without the notes fails the step.

Response Object

PropertyTypeDescription
res.postedBooleanWhether a message was posted
res.channelStringThe channel of the message, with token; empty with a webhook
res.tsStringThe timestamp of the message, which names it in the Web API, with token; empty with a webhook
res.codeIntegerThe status code of the response, 0 when nothing was posted
reqObjectvia (webhook or token), channel and api_url with a token, text and the number of notes; neither the URL of the webhook nor the token
rtDurationHow long the step took
statusInteger0

An error of Slack fails the step with what Slack answered: channel_not_found or not_in_channel of chat.postMessage, a 404 no_service of a webhook that was removed, or a 429 with the seconds Slack asks to wait. So does a post that Slack redirects with a 301 or a 302, which would be sent again as a GET. The URL of a webhook is not told in an error, nor a path a redirect gave: an error names the host alone.

The action does not return the notes it posts as res.notes, so that they are not left again for the steps after it.

Under a Guard

The action keeps to the guard of the run, and its action.yml declares guard: [read-only, allow-host], so Probe runs it under either without --allow-action. A step it refuses fails with the kind refused before any request.

  • Under --read-only, every step is refused, as posting writes.
  • Under --allow-host, the host of webhook_url or api_url, and of each redirect, must be one the run allows: hooks.slack.com for a webhook, and slack.com for a token. A URL without a port is taken at the port of its scheme.

See Guard.

See Also

  • Notes - How actions leave notes and later steps read them
  • GitHub Notes - Put the notes on a pull request, the job summary or an issue
  • External Actions - How Probe resolves and checks an external action
Updated at