Integration

Zapier

Plandalf integrates with Zapier as a marketing, sdk platform.

marketing sdk

Visit Zapier →

What it does

Runs automationsAutomation Purchase automations
Trigger on form submitAutomation Purchase automations

Product surfaces

Where Zapier fits in the buying workflow

Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Zapier receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer configuration stays visible

Use Offers to decide what Zapier receives: product, price, buyer, checkout mode, invoice, and automation context.

Offers Products Prices Checkout templates

The Numi checkout elements palette showing content, interactive, and selling blocks.

Checkout layout and selling blocks stay editable

Before Zapier enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.

Checkout templates Order bumps Upsells Coupons

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Zapier should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

Purchase automations Automations Sequences Webhooks

The Numi offer editor showing hosted checkout mode controls.

The buying surface can live where the buyer is

Zapier can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.

Hosted checkout Buy button SDK checkout API-first stack

Builder paths

Stack guides that use Zapier

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

The Checkout Optimization LabTest checkout layouts, sessions, mobile flow, and recovery without turning the sales page into a custom app.The Coupon Deadline FunnelRun a deadline offer with coupon rules and follow-up paths that stay attached to the checkout.The Course CreatorEnrol each buyer into the right cohort sequence the moment they pay.The Drop ShopRun a time-boxed drop with a real countdown, a bundle upsell, and segmented re-engagement.The Kajabi Course LaunchSell a Kajabi course through a more flexible offer and send each buyer into the right follow-up path.The Newsletter CreatorMonetise an existing newsletter audience by selling one-off products from inside the same list tool.

Plandalf vs Zapier Zapier alternatives

Zapier stack recipes

Find full stack guides that pair Zapier with checkout, payment, automation, fulfilment, records, and downstream integrations.

Offers overview

Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.

Hosted checkout

Use hosted checkout when Zapier should hand the buyer to a branded Plandalf checkout page.

SDK checkout

Use SDK checkout when Zapier belongs inside an app, custom site, or API-first stack.

Webhooks

Route checkout events, purchase events, payment state, invoices, and customer context into another tool.

Checkout completed fulfilment

Turn a completed checkout into access, receipts, CRM updates, support context, and records.

Plandalf vs Zapier

Compare how Zapier fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.

Zapier alternatives

Compare how Zapier fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.

Overview

Zapier connects thousands of apps via webhooks and pre-built triggers. For promos, we use it as a universal bridge: whatever system generates your leads, Zapier can forward them into Plandalf’s catch URL and start each participant’s deadline automatically.

What Plandalf does here

Enrolment bridge — a single Webhooks-by-Zapier step POSTs new leads into your promo’s catch URL. No Plandalf-specific Zapier app required.
Universal trigger — any Zapier trigger (form submission, ESP event, row added, Slack message, payment received, …) can feed enrolment, so the same pattern works regardless of the tools earlier in the funnel.

What Plandalf does not do

We don’t currently publish a native Plandalf Zapier app — enrolment uses Zapier’s generic Webhooks action, which works everywhere.
Zapier itself isn’t an email platform — pick it as an automation tool, not an email tool.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire Zapier into Plandalf.

promo · automation

Enrol participants via Zapier

Wire any trigger you already have in Zapier — a new form response, a new subscriber in your ESP, a row added to a spreadsheet — to POST into Plandalf's catch URL. Each incoming payload starts a new participant's deadline.

In Zapier, Create a Zap.
Pick your trigger. Any app that can signal "a new promo participant just arrived" — a form, an ESP, a CRM, anything.
Add an action step: Webhooks by Zapier → Custom Request.
Method: POST. URL:
```
{{ promo.catch_url }}
```
Content type: application/json. Data:
```
{"email": "{{ trigger.email }}", "ref": "{{ trigger.email }}"}
```
(replace {{ trigger.email }} with whichever field in your trigger step carries the email address.)
Test and publish the Zap.

Automation graph

Connecting Zapier

How Zapier participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Zapier

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

zapier.automation_step_reached: Fires when a contact reaches a designated step in a Zapier automation.
zapier.form_submitted: Fires when a form on Zapier is submitted.

Actions on Zapier

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

zapier.start_automation: Enrol a contact into a Zapier automation.

Example sequence

trigger: plandalf.checkout.completed
actions:
  - zapier.custom_api_call:
      endpoint: /v1/event
      payload:
        email: ${customer.email}
        plan: ${product_slug}

Pair it with

Connect Zapier with…

Platforms whose roles complement Zapier inside a Plandalf sequence.

Zapier + ActiveCampaign

Compose Zapier and ActiveCampaign programmatically via the Plandalf SDK.

Zapier + beehiiv

Compose Zapier and beehiiv programmatically via the Plandalf SDK.

Zapier + Kit (ConvertKit)

Compose Zapier and Kit (ConvertKit) programmatically via the Plandalf SDK.

Zapier + Customer.io

Compose Zapier and Customer.io programmatically via the Plandalf SDK.

Zapier + Drip

Compose Zapier and Drip programmatically via the Plandalf SDK.

Zapier + Flodesk

Compose Zapier and Flodesk programmatically via the Plandalf SDK.

See all integrations →

Integration methods

How Zapier connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use Zapier with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

Method 1
Trigger a sequence from a form
Point a Zapier form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.
```
curl -X POST https://api.plandalf.com/v1/intake/zapier \
  -H "Content-Type: application/json" \
  -d '{"email": "{{ form.email }}", "source": "zapier"}'
```
Method 2
Enrol from an automation step
Inside Zapier's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Zapier journey logic into Plandalf without re-building the segmentation.
```
{
  "email": "{{ contact.email }}",
  "sequence": "post-signup-onboarding",
  "source": "zapier"
}
```

Official Zapier docs and sign-up: zapier.com

FAQ

Common questions about the Zapier integration

Do I need a paid plan to use Zapier with Plandalf?

Plandalf itself is free to connect. Zapier's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.

How long does setup take?

Under 10 minutes — paste a webhook URL into Zapier, point it at the Plandalf endpoint, and trigger a test event to confirm.

Can I disconnect Zapier later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Zapier's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store Zapier data?

Plandalf stores the minimum IDs needed to address a record in Zapier plus a log of events Plandalf fired. Source-of-truth data stays in Zapier.

What if my marketing need isn't covered by the actions or triggers listed here?

Drop into the Plandalf REST API and call Zapier directly from your sequence's HTTP action. Anything Zapier's public surface exposes is reachable.

Is there a usage limit?

There's no Plandalf-side limit. Zapier's own plan limits apply.

Where do I find Zapier's own documentation?

Zapier's homepage at https://zapier.com links to their developer docs. For Plandalf-side questions about the Zapier integration, see the Plandalf docs.

Sequences for Zapier

Sequence

Checkout started to abandonment recovery

Recover a checkout that opened but did not complete by sending the buyer and offer context to the email or automation tool.