App integrations

email

Connect Zapier to the platforms you already sell with

Use Plandalf to connect Zapier with checkout pages, payment flows, email tools, CRM records, access systems, tax engines, and webhooks.

Popular connections

Zapier works with…

Use these as practical recipes, not just directory entries. Each one should explain the checkout, automation, payment, email, CRM, tax, or API handoff that matters.

How it works

Plandalf is the commerce layer between apps

Zapier keeps doing what it is best at. Plandalf handles the offer, checkout, buyer fields, payment context, invoice data, and post-purchase events that every other app needs.

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.

Search paths

Pages this hub can feed

Product surfaces to check before wiring Zapier

A useful Zapier integration page should show where the operator configures Offers, payment options, invoices, Automations, integrations, and API settings before a developer ships the flow.

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

Offer setup before anything syncs

Zapier receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.

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

Follow-up starts from the purchase event

Zapier should get buyer, product, coupon, invoice, and offer context from the purchase event instead of a disconnected form submit.

The Numi offer editor showing hosted checkout mode controls.

Checkout can live on the site or app

Zapier can launch a hosted checkout, buy button, embedded flow, or SDK checkout depending on where the buyer starts.

Feature detail