Connect Runway to Buildkite
When something happens in Runway, 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 Runway to Buildkite
Check Buildkite agents before Runway production work
Receive a Runway production-start webhook and check whether Buildkite has connected agents ready for the next media pipeline.
Review Buildkite agents for Runway workflows
On a recurring schedule, review connected Buildkite agents and receive a concise status report for Runway-related production planning.
Check Buildkite access when Runway work starts
When a Runway workflow signals a deployment or pipeline handoff, verify the current Buildkite token details and report access issues.
Review Buildkite API access for Runway operations
Run a daily access check for Buildkite and send a simple report so Runway operations do not stall unexpectedly.
Check Buildkite capacity before a Runway render queue
Use a Runway render-queue webhook to check connected Buildkite agents and report whether capacity looks constrained.
Verify Buildkite access before Runway delivery
At a Runway delivery milestone, retrieve Buildkite token details and report whether the pipeline connection is ready for handoff.
Inventory Buildkite agents for Runway production
Generate a monthly inventory of connected Buildkite agents to support Runway production planning and capacity decisions.
Capture Buildkite agent status for Runway incidents
When a Runway media workflow reports an incident, retrieve connected Buildkite agents and send a focused diagnostic snapshot.
Check Buildkite access before the weekend
Run a Friday Buildkite token check for Runway operations and report issues while there is still time to resolve them.
Supported Triggers and Actions
Notis builds workflows that link Runway to Buildkite. A trigger fires from one place; an action lands in another.
Runway triggers
Buildkite actions
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.
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
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 trough 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 Runway and Buildkite
Connect any two apps with Notis in the middle.
Not just Runway and Buildkite. Any 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.