Connect Codemagic to Linear

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

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Codemagic to Linear

View example

Turn a failed Codemagic build into a Linear issue

Create a Linear issue with the failed build details so the fix has a clear home.

View example

Post a Codemagic deployment result to Linear

Add a deployment summary to the relevant Linear issue so the team can see what shipped.

View example

Update a Linear issue with a Codemagic build status

Refresh an existing issue with the latest build status when you request it.

View example

Create a Linear handoff for a Codemagic build artifact

Turn an artifact handoff request into a Linear issue with the available artifact details.

View example

Create Linear follow-ups for recent failed builds

On a schedule, review recent Codemagic build results and open issues for failures that need attention.

View example

Add scheduled deployment summaries to Linear

Review recent Codemagic deployments on a schedule and comment on the related Linear issues.

View example

Refresh Linear issues for long-running Codemagic builds

Check selected in-progress builds on a schedule and update their Linear issues with current status.

View example

Add Codemagic troubleshooting context to a Linear issue

Fetch requested build details and add a concise troubleshooting summary to an existing issue.

Supported Triggers and Actions

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

Codemagic triggers

Linear actions

Recurring trigger

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

TriggerScheduled

Archive issue

ActionInstant

Webhook trigger

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

TriggerInstant

Create a comment

Add a comment to an issue; this shared workspace change cannot be undone.

ActionInstant

Archive Project

ActionInstant

Create linear issue

Creates an issue in the specified team and project.

ActionInstant

Archive Project Update

ActionInstant

Get create issue default params

Retrieve a team's default issue estimate and workflow state for new issue forms.

ActionInstant

Create attachment

ActionInstant

Create a label

Create a team label or return the existing label with the same name.

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

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.

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.