Whop setup guide

Status	Kind	How you connect
Coming soon	Commerce and payments	A Make template or an n8n template

This guide is coming soon: bubbl3 is still checking it end to end. It shows how Whop will send leads to bubbl3, with nothing to install.

What it does

Whop posts a signed webhook when a payment succeeds or fails, or a membership starts. A Make or n8n template takes the event, signs it with your bubbl3 lead source's secret and sends the member on, so they become (or update) a bubbl3 contact and can start the source's workflow: a welcome text when a membership activates, or a reminder when a renewal fails.

Before you start

• A Whop webhook: in your Whop dashboard's Developer tab, Create webhook, with the events you want, such as membership.activated, payment.succeeded or payment.failed.
• A bubbl3 Lead URL for Whop: in Settings, Integrations, under Lead sources, add a Lead URL source, set its labels, owner, consent setting and workflow, and copy its id (src_...) and signing secret, which is shown once.

Setup

With Make or n8n

1. Import the Make blueprint or the n8n workflow below, and paste the source id and secret where the template says.
2. Copy the address of the template's first step (Make: the Webhooks module; n8n: the Webhook node's production URL), and use it as the Whop webhook's endpoint.
3. Send a test event from the webhook's menu in Whop. The lead shows on the source as received. The template's Lead fields step maps the event's data.user name, email and phone; check them against the test, since the fields depend on the event.
4. Turn the scenario on (Make) or activate the workflow (n8n).

Whop signs its webhooks (Standard Webhooks). If you want the template to check Whop's signature too, add a step before Lead fields that compares Whop's webhook-signature with an HMAC of webhook-id, webhook-timestamp and the body under your Whop webhook secret.

Templates

Each template takes Whop's webhook, sets the lead's fields, signs the lead with your lead source's secret and sends it to bubbl3, with Whop's record id as the idempotency key, so a retry is the same lead. It never texts anyone itself: your lead source's consent setting and workflow decide what happens next.

• Make blueprint: in Make, create a scenario, open the … menu, choose Import Blueprint and pick the file.
• n8n workflow: in n8n, open a new workflow, open the … menu, choose Import from File and pick the file.

In the n8n workflow's Webhook node, replace the path replace-with-a-long-random-value with a long random value (a new UUID is fine) before you activate it. Anyone who knows the address can post to it, and the workflow would sign what they post, so the path must be one nobody can guess.

After importing, replace PASTE_THE_SOURCE_ID with your lead source's id and PASTE_THE_SOURCE_SECRET with its signing secret. Anyone who can edit the scenario or workflow can read the secret, so share it only with people who could manage the lead source; rotate the secret in bubbl3 if it leaks.

Data shared

From Whop to bubbl3: each event's id and the member's name, email and phone, when the event has them.

From bubbl3 to Whop: nothing.

Sending rules that still apply

Whop never texts anyone itself. What it sends bubbl3 can start the lead source's workflow, and every workflow text goes through the same checks as a text you send from bubbl3. Nothing in Whop can turn them off.

• Consent. When you connect Whop or create a lead source, you confirm that everyone you send to bubbl3 has agreed to receive texts from you, so its contacts can be texted straight away. bubbl3 never texts a contact who opted out, and a workspace set to text only opted-in contacts texts only them.
• Opt-out. Replying STOP opts a contact out at once.
• Quiet hours. No texts from 8:00 PM to 9:00 AM in the contact's own time zone (from the phone's area code). A text due then waits until the morning.
• Pacing. Each line texts at most 15 new contacts an hour and 50 a day (fewer while a new line warms up), and spaces texts 20 to 90 seconds apart. A big import or batch is queued and sent as the limits allow, never dropped.
• First messages. Until a contact replies, a text can't include links, photos or files, phone numbers or email addresses, must be 300 characters or fewer, and at most 3 texts go out.

What Whop is told when bubbl3 doesn't send

Whop isn't told when bubbl3 doesn't send a text: the reason shows on the message in bubbl3, and in the message.status webhook if you use one.

Reason	Code	What you see
A link before the contact replies	pre_reply_link_blocked	Not sent: "Links can't be sent until the contact replies"
A photo or file before the contact replies	pre_reply_media_blocked	Not sent: "Photos and files can't be sent until the contact replies"
A phone number before the contact replies	pre_reply_phone_blocked	Not sent: "Phone numbers can't be sent until the contact replies"
An email address before the contact replies	pre_reply_email_blocked	Not sent: "Email addresses can't be sent until the contact replies"
A first message that is too long	pre_reply_too_long	Not sent: "First messages must be 300 characters or fewer"
Too many texts without a reply	pre_reply_message_limit	Not sent: "Already sent 3 texts without a reply. Wait for the contact to reply"
The same text to too many people today	identical_text_limit	Not sent: "This exact text went to 20 people from this line today"
The line is paused after unanswered texts	unanswered_streak_limit	Not sent: "This line is paused after too many unanswered texts"
The contact opted out	contact_opted_out	Not sent: "The contact opted out of texts"
The workspace texts only opted-in contacts	consent_required	Not sent: "This workspace only texts contacts who opted in"
No line can reach the contact	line_unavailable	Not sent: "bubbl3's line for this contact isn't available"
Quiet hours	quiet_hours	Held: "Scheduled for 9:00 AM America/Chicago, quiet hours"
The line's daily limit	daily_new_contact_cap	Held: "Scheduled for Oct 15, 9:00 AM America/Chicago: today's limit for this line is reached"
The line's hourly limit of new contacts	hourly_new_contact_cap	Held: "Scheduled for 2:00 PM America/Chicago: this hour's limit of new contacts for this line is reached"

The numbers are the default limits; a line's own limits change them. bubbl3's other checks (no phone number, a number that doesn't match) have their own plain reasons.

Limits and known gaps

• One lead per Whop event id: Whop retries an event with the same id, and bubbl3 counts it once.
• Whop's events carry a phone number only when the member has one. A lead without one is refused with "A lead needs a phone number".
• Whop expects an answer within 5 seconds and retries for about 3 days; Make and n8n answer at once.

Troubleshooting

• "A lead needs a phone number". The member has no phone in Whop, or the event names it differently: check the Lead fields mapping against a test event.
• 403 from bubbl3. Check the source id and secret, and that the source isn't paused.