phorus-group/Slack Pipeline Notify Action
Posts, updates, or recovers pipeline failure messages in Slack. Tracks failures per repo+branch with attempt counters. Optionally updates draft release messages on a separate releases channel.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Apr 20, 2026
- License
- Apache 2.0
Pinned Snippet
uses: phorus-group/slack-pipeline-notify-action@999b1129700560a94d527105ad6a361931787e82 # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| slack-token | Slack Bot User OAuth Token (xoxb-...). Required scopes: chat:write, channels:history (public channels), groups:history (private channels) | yes | — |
| notifications-channel | Slack channel ID for failure tracking notifications | no | "" |
| status | Pipeline status: running, failure, or success | yes | — |
| release | Set to 'true' to enable release notifications. When enabled: 'running' also does release-start, 'success'/'failure' also does release-end | no | false |
| releases-channel | Slack channel ID for release notifications. Required when release is true | no | "" |
| release-url | GitHub release HTML URL. Falls back to constructed URL from github context | no | "" |
Outputs
| name | description |
|---|---|
| notifications-thread-ts | Thread timestamp for the notifications channel message. Use as thread_ts to post replies in the same thread. Empty if no message was posted or found. |
| releases-thread-ts | Thread timestamp for the releases channel message. Use as thread_ts to post replies in the same thread. Empty if no release message was handled. |