Integrations

A webhook is a message Gadura sends to another tool the moment something happens: someone subscribes, buys, or fills in a form.

Examples

• New subscribers appear in a Google Sheet, through Zapier.
• A Slack message when someone buys.
• Contacts kept in sync with another CRM.

Where

Settings → Integrations → Webhooks.

• Payments: Stripe, connected under Sell → Payments.
• Automation tools: Zapier, Make, n8n and anything that accepts a webhook, through Settings → Integrations → Webhooks.
• Analytics and tracking: Google Analytics and a Facebook Pixel, from their IDs, attached to a funnel or landing page under Settings → Integrations. Other pasted scripts are not run, to protect your visitors' accounts.
• Calendars: Google Calendar, Microsoft 365 and Outlook for Bookings, under Bookings → Settings → Calendars. Google Calendar reads your busy times. Microsoft 365 and Outlook also receive your bookings.
• Email: built in. Gadura sends your email from its verified domain.

1. In Zapier, create a Zap with the trigger Webhooks by Zapier → Catch Hook, and copy the address it gives you.
2. In Gadura, Settings → Integrations → Webhooks → add a webhook: a name, the Zapier address, and the events to send.
3. Choose Send test and confirm the test arrives in Zapier.
4. Add your action in Zapier and turn the Zap on.

Copy the whole address; Zapier's are long.

1. Go to Sell → Payments (also under Settings → Payments).
2. Choose Connect with Stripe and complete Stripe's onboarding: business details, identity, bank account.
3. Set your default currency on the same page.

Cards, Apple Pay, Google Pay and Link work at checkout. Stripe pays your bank on its own schedule and charges its processing fee; Gadura adds no fee per sale.

Settings → Integrations → Analytics & Tracking.

1. Choose the funnel or landing page.
2. Enter your Google Analytics measurement ID (it starts with G-).
3. Enter your Facebook Pixel ID.
4. Other tracking scripts, such as Google Tag Manager, are not run on Gadura pages. A script on a Gadura page could reach your visitors' accounts, so Google Analytics and the Meta Pixel run from their IDs instead.

The tracking runs on every page of that funnel or landing page. Data can take a day or two to appear in the tools themselves.

• New Subscriber: someone joins your list.
• Form Submitted: someone submits a form on a page.
• Purchase Completed: a payment succeeds.
• Email Opened and Link Clicked: engagement with your emails.

Start with New Subscriber; it is the easiest to test.

Open the webhook under Settings → Integrations and expand Recent Activity.

• 404: the address is wrong or incomplete.
• 401 or 403: the receiving end requires authentication it did not get.
• 500: an error at the receiving end. Check its logs.
• Timeout: the receiving end took too long to answer. Gadura retries.

Check the address starts with https, the webhook is enabled, at least one event is selected, and Send test succeeds. Still stuck: message us from the Help launcher with the webhook's name.

Yes. Anything that accepts an HTTPS POST with JSON works.

• Make: add a Webhooks module, Custom webhook, and copy its address.
• n8n: add a Webhook node set to POST and copy its address.
• Others: Pabbly Connect, Pipedream, or your own server.

Paste the address into a webhook under Settings → Integrations and choose the events.

Under Settings → Integrations, open the webhook and choose Send test. A sample event is sent to your address; check it arrived in the receiving tool.

To see exactly what Gadura sends before wiring up a real tool, point a webhook at a request-inspection service, send a test, and read the delivery there.

Recent Activity on the webhook shows each delivery, whether it succeeded, and the response.

Every delivery is a JSON POST with the event name, a timestamp, and a data object for the event:

• subscriber.created: the contact's email, name and source.
• form.submitted: the submission's email and fields, and the page it came from.
• purchase.completed: the buyer's email, the amount and currency, and the offer.
• email.opened and email.clicked: the contact and the email.

Headers on every delivery: X-Webhook-Event, X-Webhook-Delivery, X-Webhook-Retry-Attempt on retries, and User-Agent: Gadura-Webhooks/1.0. Send a test to see the exact shape.

If you send to Zapier or Make, nothing extra is needed.

For your own endpoint, add an HMAC secret to the webhook. Gadura signs each delivery with it and sends the signature in X-Webhook-Signature; verify it on your server before trusting the payload. Gadura sends only to HTTPS addresses, and every delivery carries X-Webhook-Event and a unique X-Webhook-Delivery id.