Add or update a contact in GoHighLevel when a customer pays (checkout or payment link) in Stripe

When a customer pays (checkout or payment link) in Stripe, add or update a contact in GoHighLevel.

Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.

Starts: A customer pays (checkout or payment link) in Stripe, within seconds

UsesBeta

Every step, in order

When it happens in the first app, the step runs in the second, with the client’s own account.

A customer pays (checkout or payment link): A completed Stripe Checkout, including a payment link, within seconds. The restricted key needs Webhook Endpoints: write.
Add or update a contact: Creates the contact, or updates the one with the same email or phone (the sub-account’s duplicate rules).

Nothing. It needs only the accounts it connects to.

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.
GoHighLevel
In the client’s sub-account: Settings → Private Integrations → Create new integration → scopes contacts.write (and contacts.readonly) → copy the token. The Location ID is under Settings → Business Profile.

It lands switched off. The client’s checklist holds exactly this:

Get early access and you’ll be among the first in. Early members get a launch perk.