When a CircleCI workflow completes, create a Notion page and notify the team in Slack

When a CircleCI workflow finishes, this workflow creates a Notion page with its details and then posts a message in Slack, giving your team a written record of each run and a heads-up in chat.

Circleci

Notion

Slack

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 529 sites Free to import

The When a CircleCI workflow completes, create a Notion page and notify the team in Slack workflow on the FlowMattic canvas, with 3 steps across Circleci, Notion, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Build results scroll past quickly in CircleCI, and the team often learns about a failed deploy only when someone asks. A written record of each run also helps when you look back at what shipped and when. This workflow keeps both: a Notion page per run and a Slack message for the team.

The CircleCI trigger, Workflow Completed, fires when a workflow reaches a terminal state, whether it passed or failed. FlowMattic then creates a page in Notion inside the parent page you choose, filled with run details from the trigger. Last, a message goes to the Slack channel you pick.

Every finished workflow takes this path, so you get a page and a message for successes as well as failures. To hear only about broken builds, use the Filter placement in the tips. Task History shows what Notion and Slack returned for each run.

Release log in Notion

Each finished deploy workflow gets a Notion page under a Releases parent page, which the team reads when writing release notes.

Build status in the dev channel

Developers see each CircleCI workflow result in Slack and open the Notion page for the details they map, such as branch and status.

Incident review material

When something breaks in production, the Notion pages give a dated list of the CircleCI runs that led up to it.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Circleci Workflow Completed
Fires when a CircleCI workflow reaches a terminal state, passed or failed. The run's details become data you can map into Notion and Slack.
Step 2Action
Notion Create Page
Creates a new Notion page inside a parent page you choose. Share that parent page with your Notion connection, then map CircleCI details into the page.
Step 3Action
Slack Send Channel Message
Sends a note about the finished CircleCI run to a Slack channel you select. Add the workflow name, status or other fields from the trigger to the text.

What you need

FlowMatticCore
CircleCI AccountAccount
Notion AccountAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Put a Filter between the CircleCI trigger and the Notion step that continues only when the status equals CircleCI's failure value, if the team only needs broken builds. Passed runs then get neither a Notion page nor a Slack message.
Put the status first in the Slack message, so people can tell a pass from a failure without opening Notion.
Let one CircleCI workflow finish after import, then map fields from that captured run into the Notion page and the Slack text.

Questions about this workflow

Does a successful CircleCI workflow also create a Notion page?

Yes. Workflow Completed fires for every terminal state, so passed and failed runs both create a page and a Slack message. A Filter between the CircleCI trigger and the Notion step can limit that to failures.

Where in Notion does the CircleCI page go?

Create Page adds the page inside a parent page you pick during setup. Your Notion connection needs access to that parent page.

Which CircleCI details can go on the Notion page?

Whatever the Workflow Completed trigger sends, such as the workflow name and status. The Create Page step ships unmapped, so let one workflow finish after import and map the captured fields into the page.