Connect Airtop to Codemagic

When something happens in Airtop, 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 Airtop to Codemagic

View example

Build After Airtop Finds a Release Update

Use an Airtop page check to start a Codemagic build when a release page reports a new version. Include the app, workflow, and branch or tag details in the request.

View example

Review Codemagic Builds Alongside Airtop Checks

On a schedule, retrieve Codemagic build history for an app, workflow, or branch so Notis can summarize it alongside Airtop findings you provide.

View example

Check Whether an Airtop-Found Repository Is in Codemagic

Submit a repository or project lead from an Airtop check and retrieve the Codemagic application list to identify whether it is already present.

View example

Add a Repository Found Through Airtop

When an Airtop research result identifies a repository you have decided to use, submit its repository URL to add it to Codemagic.

View example

Review Codemagic Caches After Airtop Monitoring

Schedule a Codemagic cache inventory and have Notis summarize it alongside any Airtop monitoring notes you supply, highlighting entries to review.

View example

Review Codemagic Team Apps with Airtop Research

On a schedule, list apps for a Codemagic team and summarize the results with Airtop research notes you provide, including leads needing attention.

View example

Check a Codemagic App After Airtop Finds a Build Issue

Submit an Airtop-observed build concern and retrieve the relevant Codemagic application's details for a focused follow-up report.

View example

Check Codemagic Build IPs Against Airtop Network Needs

Retrieve Codemagic's public IP ranges on a schedule and summarize them against network requirements or Airtop observations you provide.

Supported Triggers and Actions

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

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