Automations feature

Send the sale to
your own code

Add a Send Webhook step to any sequence and Plandalf posts the order to your URL, with the payload and headers you choose.

No credit card required. No coding required.

PSend WebhookStep 2 · after Checkout CompletedTested
Webhook URLhttps://api.fieldkit.app/hooks/plandalf
HTTP MethodPOST
HeadersAuthorization: Bearer ••••
Payload
{
  "event": "{{trigger.event_type}}",
  "invoice": "{{trigger.invoice_number}}",
  "email": "{{trigger.customer_email}}",
  "total": "{{trigger.total}}",
  "items": "{{trigger.line_items}}"
}
200 OK · 182 ms

How it works

An event in, a request out

A webhook is a step in a sequence, so it runs on any trigger a sequence can start on.

  1. Trigger

    An event fires

    A checkout completes, an invoice is paid or refunded.

  2. Send Webhook

    Plandalf calls your URL

    Your method, your headers, a JSON body built from the order.

  3. Your app

    You do the rest

    Grant access, write a record, kick off your own job.

Set it up

Out to your app, or in from it

Both directions are built in Automation. There is nothing to register first.

  1. 1

    Start a sequence on the event

    Create a sequence with a trigger such as Checkout Completed, Invoice Paid or Upsell Accepted.

  2. 2

    Add a Send Webhook step

    Set the URL, the method, the JSON payload with fields from the order, and any headers.

  3. 3

    Test it and turn it on

    Run the step against a sample order, check your endpoint, then switch the sequence to Active.

  4. 4

    Going the other way

    Use the Webhook Trigger to get a catch URL. Posting to it starts the sequence with your data.

  5. Read the webhook docs →
PWebhook TriggerStarts this sequence when your system posts to it
Catch URLhttps://admin.plandalf.dev/hooks/catch/seq_8f2…/trg_31c…
curl -X POST "$CATCH_URL" \
  -H "Content-Type: application/json" \
  -d '{"email":"harriet@studio.co","plan":"pro"}'

Post once and pick the request as the sample, then map its fields into the next steps.

Details

Plain HTTP, built your way

No fixed schema to code against. You decide what is sent and how it is checked.

  • Your payload

    Write the JSON and drop in order fields: email, items, totals, invoice number.

  • Any method, any headers

    POST, PUT, PATCH, GET or DELETE, with the headers your endpoint expects.

  • Your own auth

    Requests are not signed by Plandalf. Add a secret header and check it on your server.

  • On any trigger

    Checkout, invoice, upsell and cart events, or chained after other steps.

  • Inbound catch URL

    Start a sequence from your system or a form tool by posting JSON to it.

  • Runs on record

    Each run of the sequence is listed, so you can see what was sent and when.

Integrations

Keep your site. Upgrade how it sells.

Plus a fully documented REST API and webhook layer for whatever’s not in the list.

Questions

Common questions about webhooks

The short answers. The docs have the long ones.

How do I send purchase data to my app?

Create a sequence on a trigger such as Checkout Completed or Invoice Paid and add a Send Webhook step pointing at your endpoint.

Are webhooks signed?

No. Add a secret header in the step and verify it on your server.

Can my system start a Plandalf automation?

Yes. The Webhook Trigger gives you a catch URL. Post JSON to it and the sequence starts with that data.

Are failed calls retried?

Do not rely on it. Make your endpoint idempotent and check the sequence’s runs.

The team

Built by a team obsessed with conversion.

AarogornBilbertBuildoFoundoLegoli

15+ years testing every pricing model under the sun. Every part of Plandalf comes from a real checkout problem we’ve had to solve ourselves.

No credit card required. Nothing to migrate.

Feature detail