Connect Agentql to Codemagic

When something happens in Agentql, Notis takes the next step in Codemagic. 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 Agentql to Codemagic

View example

Build after a website release signal

Use an incoming release signal to start a Codemagic build for the matching app and branch.

View example

Review recent Codemagic builds

On a schedule, check a website for release context and retrieve Codemagic build history for review.

View example

Check Codemagic app details for a release

When a release request arrives, retrieve the matching Codemagic application's details for a quick readiness check.

View example

Refresh your Codemagic app inventory

On a schedule, retrieve the applications in Codemagic and use Agentql to add relevant public website context.

View example

Start a rebuild after a website incident signal

Use an incoming incident signal and website evidence to identify the affected app and start a Codemagic build when requested.

View example

Review Codemagic application caches

On a schedule, retrieve an application's caches and use Agentql to collect relevant release or documentation context.

View example

Clear Codemagic caches on an explicit request

Use an incoming request to identify an application and clear its Codemagic caches when the request explicitly asks for it.

View example

Check Codemagic build machine IP ranges

Retrieve Codemagic public IP ranges on a schedule and use Agentql to gather relevant website or networking context.

View example

Add a public repository to Codemagic

Use an incoming onboarding request and website context to add a repository URL as a Codemagic application.

Supported Triggers and Actions

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

Agentql triggers

Codemagic actions

Recurring trigger

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

TriggerScheduled

Add Application from Private Repository

Adds an application from a private repository.

ActionInstant

Webhook trigger

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

TriggerInstant

Add New Application

Adds a Git repository as an application.

ActionInstant

Get Meta Information

Retrieves metadata, including public IP addresses.

ActionInstant

Get Variable Group Information

Retrieves information about a variable group.

ActionInstant

Update Variable Group

Changes the name and security settings of a variable group.

ActionInstant

Delete All Application Caches

Deletes all cached data for an application.

ActionInstant

Delete Specific Cache

Deletes a specific cached item from an application.

ActionInstant

Get All Builds

Lists builds for your applications.

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.