Skip to content
Notis

Connect Slack to CircleCI

When something happens in Slack, Notis takes the next step in CircleCI. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Triggers when a new channel is created.

Do this · Action

Retrieves files produced by a job.

Examples

Ways Notis can move work from Slack to CircleCI

Start a CircleCI release pipeline from Slack

Turn a clear Slack release request into a CircleCI pipeline run, so release work begins without copying commands between tools.

Start a pipeline after a ship approval reaction

Use a designated reaction on a Slack message to signal approval and have Notis start the requested CircleCI pipeline.

Look up CircleCI pipelines from Slack

When someone asks for recent pipeline status in a Slack channel, retrieve the project's CircleCI pipelines to answer in context.

Get CircleCI job details from a Slack DM

Use a direct request to retrieve status, timing, and executor details for a specific CircleCI job number.

Inspect CircleCI test failures requested in Slack

When a teammate asks about failed tests in Slack, retrieve CircleCI test metadata for the referenced completed job.

Retrieve CircleCI artifacts on request

When a Slack channel request points to a completed CircleCI job, retrieve its artifacts so the team can find its outputs.

List workflows for a CircleCI pipeline

Answer a Slack request for a pipeline breakdown by retrieving the workflows associated with its pipeline ID.

Inspect CircleCI pipeline configuration from Slack

Retrieve source or compiled configuration for a specific CircleCI pipeline when a team member asks about its setup in Slack.

Check CircleCI self-hosted runner availability

Use a Slack request to retrieve the organization's configured CircleCI self-hosted runners and help the team check runner availability.

Supported Triggers and Actions

Notis builds workflows that link Slack to CircleCI. A trigger fires from one place; an action lands in another.

Slack triggers

CircleCI actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Job Artifacts

Retrieves files produced by a job.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Context

Creates a context for sharing environment variables securely across projects.

ActionInstant

New Channel Created Trigger

Triggers when a new channel is created.

TriggerInstant

Cancel Workflow

Cancels a running CircleCI workflow.

ActionInstant

Channel Message Received

Triggers when a message is posted in a channel, excluding direct messages.

TriggerInstant

Get Job Details

Retrieves status, timing, and executor details for a job.

ActionInstant

Direct Message Received

Triggers when a new direct message, including a thread reply, is sent to a user.

TriggerInstant

Create Context (GraphQL)

Creates a CircleCI context for an organization.

ActionInstant

Message Reaction Added

Triggers when a reaction is added to a message.

TriggerInstant

Get Pipeline Config

Retrieves the source or compiled configuration for a pipeline.

ActionInstant

Message Reaction Removed

Triggers when a reaction is removed from a message.

TriggerInstant

Create Context Restriction

Creates a context restriction to limit access by project, rules, or group.

ActionInstant

New Bot Message Received Trigger

Triggers when a bot posts a new message in a channel.

TriggerInstant

Get Test Metadata

Retrieves test results, run times, and failure details for a job.

ActionInstant
Trigger Types

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
Why AI automation

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.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

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.

Notis

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:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

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

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

Related pairs

More ways to connect Slack and CircleCI

Connect any two apps with Notis in the middle.

Slack and CircleCI, or any other combination from 1,600+ 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 CircleCI.