The Stripe webhook integration connects your own Stripe account to CamBuildr. Once it's set up, activity in Stripe — whether a checkout started on a CamBuildr landing page or somewhere else entirely — flows into CamBuildr automatically. Every event is matched to a person and recorded as an action on their profile, so you can automate on any Stripe event, filter those automations by the exact product, and browse your live Stripe catalog without leaving CamBuildr.
How it works
Whenever something happens in your Stripe account, Stripe notifies CamBuildr. For every event it receives, CamBuildr finds the matching person by email (creating or updating them, including name, and — for checkouts — phone and address), and records what happened as an action on that person. Completed checkouts additionally update the related purchase or donation. From there, the action is available to your triggers and target audiences just like any other action in CamBuildr.
The Stripe integration must be enabled for your instance. This is an internal setting, so ask your CamBuildr contact to switch it on — there is no self-serve toggle for it.
Automate on any Stripe event
This is the heart of the integration: every Stripe event becomes an action you can build automations on — not just completed checkouts, but invoices, charges, subscription changes, and more.
Each received event creates a "Stripe event received" action on the matching person, carrying the event type, the amount, and the IDs of any products involved.
In the Triggers editor you can start an automation from "Stripe event received" (or from "Has purchased" for completed CamBuildr checkouts) and narrow it with the Products field — a multi-select of your Stripe products labelled "Products (any if empty)". Leave it empty to react to any product, or pick one or more to fire only for those.
Because these are normal CamBuildr actions, you can also use them to build target audiences and segment people by what (and how much) they bought.
Example: send one onboarding sequence when someone buys Product A and a different one for Product B — by creating two triggers on "Has purchased" / "Stripe event received", each scoped to the relevant product.
A note on consent: completed checkouts respect your double opt-in settings — an unconfirmed person receives an opt-in request first. The general event-tracking action only records once a person is opted in, so CamBuildr never sends opt-in emails on routine Stripe events.
Browse your Stripe products
A new Products page in the admin lists all products from your connected Stripe account, pulled live from Stripe:
See each product's image, name, price, and status (active / inactive).
Use Open in Stripe to jump straight to that product in your Stripe dashboard.
The same catalog powers the product filter on the Purchases overview and the product multi-select on triggers, so every part of CamBuildr references the same source of truth. Update a product in Stripe and the change shows everywhere automatically.
What happens when a checkout completes
For completed Stripe checkouts (checkout.session.completed), CamBuildr does a little more than record a generic action:
If the payment came from a CamBuildr purchase block, the matching purchase is marked paid and linked to the person.
If it came from a CamBuildr donation, the donation is marked paid and linked to the person.
For everything else (e.g. a Stripe Payment Link or a checkout you built yourself), it records a "paid" action, including the total amount, the product names, every line item, and — for Payment Links — the link URL as the source.
It also fully supports cross-sells / multiple products: every line item in the checkout is captured, not just the main product, and the recorded value is the combined total.
What you need to set up
In Stripe
Products & prices — set up the products you sell (and optionally Payment Links). The names, prices, and images CamBuildr shows come straight from Stripe.
Add a webhook endpoint — in Developers → Webhooks, add an endpoint pointing to your CamBuildr instance:
https://<your-cambuildr-domain>/api/v1/hooks/stripeChoose the events to send:
checkout.session.completedis required for purchases and donations to be marked paid.To automate on other activity (invoices, subscriptions, refunds, etc.), also subscribe to those events — or simply choose "Send all events".
Copy the signing secret that Stripe generates for that endpoint (it starts with
whsec_).
In CamBuildr
The Stripe integration must be enabled for your instance. This is an internal setting, so ask your CamBuildr contact to switch it on — there is no self-serve toggle for it.
Your Stripe secret API key and the webhook signing secret from the step above must be stored in CamBuildr. If you don't see where to enter these, our team can configure them with you.
Once both sides are connected, the next Stripe event will appear as a person + action in CamBuildr automatically — no further action needed.