Webhooks (Zapier, Make, n8n)

A webhook sends an application to an automation tool when it’s submitted, approved or rejected. Use it to add new applicants to a spreadsheet or CRM, post a message in your team chat, or start any workflow you build. Sami B2B Onboarding works with Zapier, Make, n8n and any other tool that gives you a webhook URL.

The store has one webhook URL, and every form that’s connected sends to it. Each form chooses which events it sends.

Get a webhook URL from your tool

The URL must start with https:// and be on the public internet.

1. In Zapier, create a Zap.
2. For the trigger, choose Webhooks by Zapier, with the event Catch Hook. Click Continue until you reach the Test step.
3. Copy the webhook URL Zapier shows. It starts with https://hooks.zapier.com/hooks/catch/.

Keep the Zap open. You’ll test it in a moment.

1. In Make, create a scenario.
2. Add the Webhooks module and choose Custom webhook.
3. Click Add, name the webhook and click Save.
4. Click Copy address to clipboard.

Make now waits for the first event, so it can learn the fields.

1. In n8n, start a workflow with a Webhook node.
2. Set HTTP Method to POST. The app sends its events as POST requests, and the node starts on GET.
3. Copy the Production URL, and activate the workflow so that URL listens.

While you build the workflow, you can use the Test URL instead. It only listens after you click Listen for test event, so switch to the Production URL when you’re done.

Connect the form

1. Open the Webhook panel

   Go to Forms and click Edit beside the form. In the rail on the left, click Integrations. Under Connected apps, click Connect on the Webhook (Zapier, Make, n8n) row.

   The Webhook panel opens with three sections: Account, This form and Payload.

2. Paste the URL

   Under Account, click Set up. In the Webhook dialog, paste the URL into Webhook URL and click Save.

   You see Keys saved. The Account row shows only the URL’s domain and its last few characters. Anyone who has the URL can send data to your workflow, so the app keeps the rest hidden.

   If the URL isn’t saved, the box under it says why. Check that you copied the whole URL and that it starts with https://. A URL that points to a local or private address gets Paste the webhook URL Zapier, Make or n8n gave you — a public address, not a local or private one.

3. Choose the events

   Under This form, below Send an event when, tick the events this form sends:

   • An application is submitted: ticked to start with.
   • An application is approved: ticked to start with.
   • An application is rejected: cleared to start with.

   Turn on Include the raw submission payload if your workflow needs every answer exactly as it was stored. See What each event contains.

   

   Each form chooses which events it sends, and Send a test event stays greyed out until a webhook URL is saved.

4. Connect and save

   At the bottom of the panel, click Connect. The button changes to Disconnect, and the row in Connected apps shows Connected. If no URL is saved yet, a banner reads Add your webhook URL first.

   Click Save in the save bar. You see Form saved. No event is sent until you save.

Send a test event

The test event lets your tool learn the form’s fields before a real buyer applies.

1. Save the form first

   The test event carries the questions of the form as it was last saved. Save after adding or removing questions.

2. Send it

   In the Payload section, click Send a test event. The button reads Sending…, then you see Test event sent. The button works as soon as a URL is saved, even before you click Connect.

   

   Once a URL is saved, Send a test event works even before you connect the form.

3. See it in your tool

   • Zapier: on the Test step, click Test trigger and pick the request that arrived.
   • Make: the webhook module says the data structure was determined.
   • n8n: the Webhook node shows the data it received. With the Test URL, click Listen for test event before you send.

   Then map the fields in your tool’s next steps.

If your tool doesn’t accept the test, a Test event failed banner appears with one of these messages:

Message	What to do
Add your webhook URL first.	Save a URL under Account first.
That webhook URL is not a public address. Change it, then try again.	Use the public https:// URL your tool gave you. Click Change under Account to replace it.
The webhook didn’t answer. Check the URL, then try again.	The address couldn’t be reached. Copy the URL from your tool again and paste it with Change.
The webhook answered with HTTP 404. Check that the scenario or workflow is on and listening, then try again. (The number can differ.)	Your tool refused the event. In Make, check that the scenario and its webhook still exist. In n8n, activate the workflow, or click Listen for test event when you use the Test URL. In Zapier, check that the Zap and its trigger still exist.
The test event wasn’t sent. Try again.	The app couldn’t send it. Try again in a moment.

The events

Event	Sent when
An application is submitted	A buyer sends a new application. It’s sent even if a rule decides the application straight after. A buyer who answers a request for more information doesn’t send it again.
An application is approved	Someone on your team approves the application, alone or with others selected, or adds the buyer to a company you already have. Also when a Shopify Flow workflow approves it.
An application is rejected	Someone on your team rejects the application, or a Shopify Flow workflow does.

Asking a buyer for more information sends no event.

Note

An application that a rule or the tax ID check approves or rejects on its own doesn’t send the approved or rejected event.

What each event contains

Each event arrives as one set of named fields. Your tool shows them under these names when you map them:

Field	What it holds
event	application.submitted, application.approved or application.rejected. Use it to filter one workflow to one event.
form	The form’s name, for example Wholesale application.
reference	The application’s reference, as shown under Reference on the application in the app.
status	The application’s status when the event was sent, for example pending, approved or rejected. A rule may already have decided a new application by then, so use event, not status, to tell events apart.
submitted_at	When the buyer submitted, as a date and time.
company_name, contact_name, contact_email	The company name, the buyer’s name and their email.
country	The buyer’s country, as a two-letter code such as US.
One field per answer	Each answer, under the field name the form gives its question, for example contact_title or shipping_city on the Wholesale application form. The Payload box and the test event show these names. Several choices are joined with commas, and an upload is sent as its file name.
raw	Only when Include the raw submission payload is on: every answer as it was stored, with lists kept as lists.

The Payload box in the panel shows the start of an event for your form, so you can see the names before you test.

The test event has the same fields, filled with example values. reference reads APP-TEST, each question holds its placeholder or its label, and an extra field, test, is set to true, so your workflow can skip it. Upload questions and raw are left out of the test.

See what was sent

Every event the app sends leaves an entry on the application’s Timeline, named Webhook and the company, for example Webhook · Acme Supply Co. Click it to see the result: Sent to the webhook, “The webhook answered with HTTP 410” or The webhook didn’t answer. The same entries appear under Recent runs on the Automations tab of Automation, and in Settings › Activity log on its Emails view. A test event leaves no entry.

Each delivery to your webhook shows under Recent runs, with its result and time.

Stop sending

• Stop one form: open its Webhook panel, click Disconnect, then Save. Its event choices stay.
• Change the URL: under Account, click Change, paste the new URL and click Save. Leave the box empty to keep the URL you already saved.
• Remove the URL for every form: under Account, click Change, then Remove keys. The dialog warns Every form in this store stops using Webhook until you add keys again. Click Remove keys to confirm. You see Keys removed. This takes effect at once.

Next steps

• Automations and Shopify Flow — build workflows inside Shopify instead, with the app’s Flow triggers.
• Klaviyo — add applicants or approved buyers to a Klaviyo list.
• Activity log — see every delivery the app made.