Connect Adrapid to Carbone

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

View example

Check Carbone before turning an Adrapid campaign into a report

When an Adrapid webhook supplies campaign output and report requirements, confirm Carbone is healthy before document generation.

View example

Find the right Carbone template for Adrapid campaign output

Search Carbone templates using an Adrapid webhook payload that includes the campaign type, report name, and required format.

View example

Render Adrapid campaign data into a document in one call

Use an Adrapid webhook payload with a supplied base64 template and data to render a Carbone document directly.

View example

Generate a Carbone performance report from Adrapid results

Turn campaign metrics and asset details in an Adrapid webhook into a structured Carbone report using a named template.

View example

Review Carbone templates used by Adrapid each week

On a schedule, search Carbone for templates named in a supplied Adrapid export and flag missing or unmatched report layouts.

View example

Upload an approved reporting template from an Adrapid request

When an Adrapid webhook includes an approved template file and replacement instructions, upload it to Carbone.

View example

Update Carbone metadata from an Adrapid template brief

Apply explicit name, comment, tags, category, or lifecycle metadata from an Adrapid webhook to an existing Carbone template.

View example

Retrieve a Carbone template for an Adrapid revision request

Download the exact Carbone template named in an Adrapid webhook so it can be reviewed or revised.

View example

Prepare a Carbone template ID for a new Adrapid report layout

Generate a unique Carbone template ID when an Adrapid webhook requests a new report layout.

Supported Triggers and Actions

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

Adrapid triggers

Carbone actions

Recurring trigger

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

TriggerScheduled

Delete Carbone Template

Permanently deletes a template; this action cannot be undone.

ActionInstant

Webhook trigger

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

TriggerInstant

Download Template

Downloads the original template file.

ActionInstant

Generate Carbone Report

Generates a document in the chosen format from a template.

ActionInstant

Get Carbone Server Status

Checks the server’s current status and health.

ActionInstant

List Templates

Retrieves templates stored in the workspace.

ActionInstant

Set Carbone API Version

Sets the Carbone API version for subsequent requests.

ActionInstant

List Template Categories

Lists the categories used to organize templates.

ActionInstant

Upload a template

Uploads a template for document generation.

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.