Bring Buildkite failure context into Slack
Give the team a clear place to review a failed build and its surrounding discussion.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Fetch conversation history
Fetches a chronological list of messages and events from a specified slack conversation, accessible by the authenticated user/bot, with options for pagination and time range filtering.
Why this helps
A failed build can leave you switching between Buildkite and Slack to understand what the team already knows.
- Gather recent Slack discussion when a Buildkite failure is reported.
- Reduce manual context switching during triage.
- Keep the update grounded in available Slack history.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Slack once in the Notis portal.
- 2Create an automation from Automations, New Automation, or by telling Notis what to do in plain language.
- 3In one instruction, ask Notis to use the Buildkite failure details to find and summarize relevant Slack conversation history.
- 4Choose a Notis webhook trigger and select where run reports should go.
- 5Test with one real Buildkite failure and confirm the Slack history supports the summary.
Questions about this workflow
Does Buildkite provide a trigger event for this workflow?
No. Start it with a Notis webhook, which accepts an HTTP request, and include the Buildkite failure details in the request.
Will this workflow post a message to Slack?
The selected action retrieves Slack conversation history. The automation can summarize the returned history in its run report, but this action does not post a Slack message.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Slack. A trigger fires from one place; an action lands in another.
Buildkite triggers
Slack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
Buildkite and Slack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Slack.