Inbound Webhooks let other booking tools — like HoneyBook, Dubsado, or any platform connected through Zapier — automatically create performances in your BookLive group the moment a booking comes in. No manual entry, no copy-pasting: a new confirmed performance appears in BookLive as soon as the booking is recorded in your other tool.
Before You Begin #
- You must be a group leader to create or revoke webhook keys.
- You will need a Zapier account. A free plan is sufficient for basic use.
- Your booking tool (e.g. HoneyBook) must be connected to Zapier as a trigger source.
Step 1: Open Inbound Webhooks in Group Settings #
- Log in at https://booklive.com/login.
- Navigate to your group and click Settings in the left sidebar.
- Click the Inbound Webhooks tab.
You will see the Create Performance webhook card, which includes your group’s unique Webhook URL and key management tools.
Step 2: Generate a Webhook Key #
Webhook keys authenticate incoming requests and tie them to your group. You can create multiple keys — for example, one per integration — and revoke any of them independently if needed.
- Under Webhook keys, enter a descriptive name for the key in the Key name field (e.g. HoneyBook (Zapier)).
- Choose an expiry from the Expires dropdown. No expiration is recommended for ongoing integrations.
- Click Generate key.
- A dialog will display your new key. Copy it immediately and store it somewhere safe — this is the only time BookLive will show the full key. If you lose it, you will need to revoke the key and generate a new one.
Step 3: Copy the Webhook URL #
In the same Inbound Webhooks tab, click Copy next to the Webhook URL field. This URL is where Zapier will send each new booking. The URL is the same for all keys in your group — your key is what authenticates the request.
Step 4: Set Up the Zap in Zapier #
With your Webhook URL and key ready, head to Zapier to build the automation.
- Create a new Zap with your booking tool (e.g. HoneyBook) as the Trigger. Configure it to fire when a new booking or project is created.
- Add an Action step and search for Webhooks by Zapier. Select the POST event.
- In the URL field, paste the Webhook URL you copied from BookLive.
- Set Payload Type to Form.
- Under Data, map fields from your booking tool to BookLive field names. Add one row per field — see the field reference table below.
- Leave Wrap Request In Array set to No.
- Under Headers, add one row:
- Left box:
Authorization - Right box:
Bearerfollowed immediately by your webhook key (example:Bearer abc123…)
- Left box:
- Click Test step. If everything is configured correctly, a new performance will appear in your BookLive group within a few seconds.
Webhook Field Reference #
When mapping data in Zapier, use these field names in the left column of the Data section. Only the required fields are needed to create a performance — all others are optional but recommended for a complete record.
| Field name | Required? | Description |
|---|---|---|
external_id |
Yes | A unique ID for the booking from your tool (e.g. the HoneyBook project ID). Prevents duplicate performances if Zapier retries the request. |
title |
Yes | The name of the performance — typically the event or couple’s name. |
date |
Yes | The event date. Most formats work: 2027-05-14, 05/14/2027, or May 14, 2027. |
start_time |
Yes | The start time, e.g. 5:30 pm or 17:30. |
end_time |
No | The end time. If omitted, BookLive defaults to one hour after the start. |
event_type |
No | The event type, e.g. Wedding. If it’s new to your group, it will be added automatically. |
amount |
No | Total fee in dollars, e.g. 2500. |
notes |
No | Any additional details to include on the performance record. |
venue_name |
No | The venue name. |
venue_city / venue_state |
No | Venue city and state. A venue record is created in your group when both are provided. |
venue_address / venue_zip |
No | Venue street address and ZIP code. |
client_first_name / client_last_name |
No | The client’s first and last name. |
client_email |
No | Client email address. Used to match an existing client in your group, or create a new one. |
client_phone / client_company / client_address |
No | Additional client contact details. |
source |
No | A label for where the booking came from, e.g. honeybook. Used for lead source tracking. |
timezone |
No | Only needed if the event is in a different timezone than your group’s default. |
Managing Your Webhook Keys #
All active keys are listed in the Webhook keys table, showing the key name, creation date, last used date, and expiration status.
- To revoke a key, click Revoke next to its row and confirm. This immediately invalidates the key — any Zap using it will stop creating performances until it is updated with a new key.
- Keys that have expired are shown with a red Expired label. Revoke and regenerate them to restore the integration.
- You can create multiple keys for different integrations or team members. Revoking one key does not affect the others.
Tips & Notes #
- Idempotency: The
external_idfield prevents duplicate performances. If Zapier retries a failed request, BookLive will recognize the same external ID and skip creating a second record. - Existing clients: If the
client_emailyou send matches a client already in your group, BookLive links the performance to that existing client rather than creating a duplicate. - Advanced use: If you prefer to send structured JSON rather than form fields, set Payload Type to JSON in Zapier and send a body with nested
clientandlocationobjects. Both formats are accepted. - Inbound Webhooks is available to group leaders only. Non-leaders can view the tab but cannot generate or revoke keys.
