Skip to main content
Who can use this?
  • Gallabox users who need to connect Gallabox to external systems.
  • Roles: Owners and Admins (and roles with the relevant permission). Custom Roles with the “Can view and manage webhooks, API keys” permission (Developer modules) can also configure webhooks.
  • Plans: Essential and Advanced plans. Basic plan does not include webhooks.
This article explains webhooks in plain language. For technical implementation details, see the Developer Resources.

​
Plan Availability

Webhooks require the Essential or Advanced plan.

​
What is a Webhook?

A webhook is a real-time notification — a way for Gallabox to tell another system (like your CRM, ERP, or custom software) when something happens, the moment it happens. Think of it like a phone call: instead of the other system constantly asking “Did anything happen? Did anything happen? Did anything happen?” — Gallabox calls them the instant something happens. For example: when a new contact is created in Gallabox, a webhook fires → your CRM gets notified → the CRM automatically creates a lead record. No manual export, no delay.

​
How Webhooks Work — Step by Step

1

You give Gallabox a URL

You give Gallabox a URL (called the “Request URL”) — this is the address of your receiving system.
2

You choose which events to notify

You tell Gallabox which events to notify you about (e.g., “new contact”, “message sent”, “broadcast completed”).
3

Gallabox sends a request

When one of those events happens in Gallabox, Gallabox sends an HTTP request using the method configured for that webhook. The event name is sent in the x-event-name header.
4

Your system receives and responds

Your system receives it, processes it, and responds with “Got it!”This all happens in real time — typically within seconds of the event.

​
When to Use Webhooks

Webhooks are useful when you need Gallabox to talk to systems that don’t have a native Gallabox integration. Common use cases:

​
What Events Can You Subscribe To?

Gallabox supports webhooks for these event categories:

​
Contact Events

​
Conversation Events

​
Message Events

​
Template & Broadcast Events

The webhook configuration screen in Settings → Webhooks shows the events available for your account.

​
What Does the Webhook Send?

When an event fires, Gallabox sends the event data in the request body using the HTTP method configured for that webhook. The event name is sent separately in the x-event-name header; it is not wrapped inside the body. For example, a contact-created event includes:
The request body contains the event data:
Your system receives this payload and can extract the data it needs. For example, a CRM would take the name, phone, and email fields and create a new lead record.

​
Setting Up a Webhook

1

Have your endpoint ready

Before configuring in Gallabox, you need a receiving URL. This is typically an endpoint in your CRM, custom application, or an automation tool like Zapier or Make (which can act as a receiver and forward to other apps).If using Zapier or Make:
  1. Create a new Zap/Webhook in Zapier.
  2. Choose “Webhooks by Zapier → Catch Hook” as the trigger.
  3. Zapier will give you a unique URL — copy it.
  4. Paste it into Gallabox.
If using a custom application, your developer will create an endpoint that:
  • Accepts the HTTP method you configure for the webhook
  • Reads the JSON payload
  • Responds with HTTP 200 (success)
2

Configure in Gallabox

  1. Go to Settings → Webhooks → Add Webhook.
  2. Enter your Request URL — the endpoint you prepared in Step 1.
  3. Select the HTTP method your endpoint accepts.
  4. (Optional) Add a Secret — a shared key used to verify requests are actually from Gallabox and not from a third party.
  5. (Optional) Add Custom Headers — e.g., an authorization token if your endpoint requires one.
  6. Select the Events you want to subscribe to.
  7. Click Save.
3

Test your webhook

  1. In Gallabox, trigger the event (e.g., create a test contact).
  2. Check your receiving system — you should see the payload arrive within seconds.
  3. If nothing arrives, check:
    • The URL is correct and publicly accessible
    • Your endpoint is responding with HTTP 200
    • The event is selected in your webhook configuration

​
Security

​
Verifying webhook authenticity

If you set a Secret in your webhook configuration, Gallabox includes a signature header in every request. Your endpoint should verify this signature to confirm the request came from Gallabox:
Your developer can compute the HMAC-SHA256 of the payload using your secret (base64-encoded) and compare it to the signature header. If they don’t match, the request is not from Gallabox and should be rejected.

​
Common security practices

  • Always use HTTPS for your Request URL
  • Verify the signature on every request
  • Return HTTP 200 quickly and process asynchronously (don’t block the request while doing heavy processing)
  • Log incoming webhook payloads for debugging

​
Example

Scenario: You use HubSpot as your CRM and want every new Gallabox contact to automatically become a lead in HubSpot — without manual exports. Here’s how you’d set it up:
  1. In HubSpot, create an incoming webhook or use a Zapier/Make integration that accepts webhook data and creates a HubSpot contact.
  2. Copy the webhook URL from HubSpot/Zapier.
  3. In Gallabox: Settings → Webhooks → Add Webhook
    • Request URL: [paste URL from step 2]
    • Events: Contact.Created
    • Secret: [set a secret for verification]
  4. Save.
  5. Now whenever a new contact is created in Gallabox (via any channel), Gallabox fires a webhook → HubSpot receives it → a lead is created automatically.

​
Webhooks vs Native Integrations

If Gallabox has a native integration for your tool (see Integrations), use that instead of webhooks — it’s faster to set up and requires no code.

​
Webhook Logs

To check if your webhook is working: go to Settings → Webhooks and open the Logs tab. Each entry shows:
  • Webhook name
  • Webhook log ID
  • Event — which event triggered the delivery
  • Created At — when the delivery happened
  • Status — SUCCESS or FAILED
  • Payload — click View info to see the JSON sent to your endpoint (masked if you don’t have PII permission)
Logs are kept for 7 days. If you see failures, check your endpoint logs alongside the payload for details.

​
FAQs

Gallabox retries failed webhook deliveries automatically — up to 5 attempts with increasing delays between them. Retry details aren’t shown in the UI. If your endpoint is consistently unavailable, events may be lost. For critical events, implement a queue or logging system so nothing is missed.
A webhook is Gallabox pushing data to you when something happens. An API is you pulling data from Gallabox when you ask for it. Webhooks are real-time and event-driven. APIs are on-demand. Use webhooks for real-time notifications; use the API for querying historical data or taking actions in Gallabox.
Yes — both Zapier and Make (formerly Integromat) have a “Catch Webhook” trigger that generates a URL you can paste into Gallabox. From there, you can connect to thousands of other apps — e.g., webhook → Zapier → Google Sheets, Notion, Slack, etc. This is the no-code way to use webhooks.
See the Webhook Logs section above.