Connect Slack to Buildkite
When something happens in Slack, Notis takes the next step in Buildkite. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Slack to Buildkite
Check Buildkite agents when a release channel starts
When a Slack release channel is created, check which Buildkite agents are connected and share the result in the run report.
Answer Slack requests for Buildkite agent status
When a channel message asks about Buildkite agents, list connected agents and report the result for a quick availability check.
Check Buildkite token details from a Slack DM
When a direct message asks whether the Buildkite API token is valid or what scopes it has, retrieve the current token details for the run report.
Look up Buildkite token details for a channel question
When a Slack channel message asks about Buildkite token validity or scopes, retrieve the current authenticated token details for the run report.
Check agents when a Slack message gets an approval reaction
When a team adds an agreed approval reaction to a Slack message, list connected Buildkite agents and share the check in the run report.
Check Buildkite token access after an approval reaction
When an agreed reaction approves an access-related Slack message, retrieve current Buildkite token details for the run report.
Fetch Buildkite API metadata after a firewall reaction
When an agreed reaction marks a Slack firewall discussion for follow-up, fetch Buildkite API metadata, including webhook IP addresses, for the run report.
Fetch Buildkite webhook metadata from a firewall discussion
When a Slack channel message asks for Buildkite webhook IPs or API metadata for firewall work, fetch the metadata and share the result in the run report.
Answer a private firewall question with Buildkite metadata
When a direct message requests Buildkite webhook IPs or API metadata for firewall work, fetch the metadata for the run report.
Supported Triggers and Actions
Notis builds workflows that link Slack to Buildkite. A trigger fires from one place; an action lands in another.
Slack triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Slack and Buildkite
Connect any two apps with Notis in the middle.
Slack and Buildkite, 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 Buildkite.