Connect Active campaign to Craftmypdf

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

View example

Generate a PDF for a campaign contact

Turn an ActiveCampaign webhook request into a PDF for a contact using your chosen CraftMyPDF template.

View example

Review available PDF templates on a schedule

Have Notis periodically retrieve the CraftMyPDF template list and send a run report for review.

View example

Queue a document request from campaign data

Use an ActiveCampaign webhook to queue CraftMyPDF generation with supplied JSON data and a callback URL.

View example

Check CraftMyPDF account usage regularly

Retrieve CraftMyPDF account and usage information on a schedule and send the results to your run report channel.

View example

Fill a PDF form from a campaign request

Use supplied form field values in an ActiveCampaign webhook request to update a fillable PDF in CraftMyPDF.

View example

Review recent PDF generation transactions

Retrieve CraftMyPDF transaction history on a schedule and send the returned results to your chosen run report channel.

View example

Generate a batch of campaign document PDFs

Start parallel PDF generation for multiple supplied requests and optionally merge the generated files into one PDF.

View example

Review PDF template usage statistics

Retrieve usage counts and credit consumption for specified CraftMyPDF templates over a date range on a recurring schedule.

Supported Triggers and Actions

Notis builds workflows that link Active campaign to Craftmypdf. A trigger fires from one place; an action lands in another.

Active campaign triggers

Craftmypdf actions

Recurring trigger

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

TriggerScheduled

Create Editor Session

Creates an embeddable editor session for a PDF template.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Text to PDF

Add text annotations, such as page numbers, watermarks, headers, or footers, to a PDF.

ActionInstant

Add Watermark to PDF

Overlay a customizable text watermark on a PDF.

ActionInstant

List PDF Templates

Lists the available PDF templates.

ActionInstant

Create PDF Asynchronously (Extended)

Start PDF creation in the background and return a transaction reference; a callback reports when it is ready.

ActionInstant

Create PDFs in Parallel

Generate multiple PDFs concurrently from templates and optionally merge them into one file.

ActionInstant

Get Account Information

Retrieve account subscription, usage, quota, and creation details.

ActionInstant

Get PDF Information

Retrieve PDF metadata and page count without downloading the full document.

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.