Subscriptions to webhooks in Livespace CRM allow your application to receive real-time information about important events in the system: for example, the creation of a new deal or a change in its status. This makes it easy to integrate Livespace with other tools or automate your processes.
In this article:
Key Concepts
In Livespace, we distinguish between two concepts: a webhook subscription and a webhook.
A webhook subscription is a configuration in which you specify:
when the data should be sent (which events),
where it should be sent (URL),
what information should be included.
A webhook is a single message sent by Livespace at the moment an event occurs, according to the subscription settings.
Remember that the subscription defines the sending rules, while the webhook is the message that is actually sent.
How Webhooks Work
Webhooks work in a simple way: when something important happens in Livespace, the system sends a webhook (a message) to the specified URL, according to the subscription configuration.
Each notification includes:
information about the event (e.g., transaction ID, status, owners, value, products),
a header for authenticity verification,
a special secret (secret key) that ensures security.
After saving and activating a subscription, Livespace first sends a test notification to your endpoint to ensure it is correctly configured and ready to receive data. Only then are actual webhooks sent for real events.
You can find the technical documentation here:
Overview of Webhooks in Livespace
Administrators can manage webhook subscriptions in Account Settings -> Webhooks.
On the subscription list, you can check:
whether the subscription is active,
its name and URL,
the selected events,
the last time it was triggered.
Creating a New Subscription
For Livespace to be able to send webhooks to your application or an external tool, you need to create and configure a webhook subscription.
A webhook can send data to any tool or system that supports receiving webhooks. This can be either a ready-made integration tool or your own API.
In Account Settings -> Webhooks, select Add subscription.
2. In the Connect section, provide basic information:
Name this subscription – give it a name that you will easily recognize later.
Where should we send the data? – paste the webhook endpoint URL.
3. Next, click Next: Set triggers.
4. Select the event for which Livespace should send data.
5. Next, click Activate subscription.
At this point, your subscription becomes active - in the example above, webhooks will be sent when a deal is created.
If you add a new deal in Livespace, the external tool will receive information about it.
Example of receiving data in Zapier:
Remember that the first request is a test notification sent to your endpoint to make sure it is correctly configured.
What does the notification contain?
The actual notification contains the most important information about the deal: ID, name, status, owners, value, products, costs, and tags.
Where to get the webhook URL?
The webhook URL (endpoint URL) is generated by the tool or system that will receive notifications from Livespace. This can be an automation platform or your own API.
Below you’ll find instructions for the most commonly used tools.
Zapier
Go to Zaps.
Click Create and select New Zap.
Click the Trigger block.
Select Webhooks from the app list.
Choose the Catch Hook trigger event.
Go to the Test tab.
Copy the generated webhook URL.
Example configuration in Zapier:
Make
Go to Scenarios.
Click Create a new scenario.
Select Webhooks -> Custom webhook.
Add a new webhook or select an existing one.
Copy the generated URL.
N8N
Select Create workflow.
Click Add first step… and choose On webhook call.
Copy the Test URL or Production URL:
Test URL is used for testing,
Production URL can only be used after publishing the workflow.
Security and functionality
All data sent via webhooks is transmitted exclusively over an encrypted HTTPS connection. This ensures that information is protected while being transferred over the network.
Each notification contains a special verification header generated based on the subscription secret. This allows you to verify that the data truly comes from Livespace and not from a third party. It is an additional safeguard that increases the security of the integration.
If your endpoint (the address to which webhooks are sent) does not respond correctly, Livespace will automatically attempt to deliver the notification two more times at short intervals.
Webhooks work in such a way that:
the same event may be sent more than once,
events may arrive in a different order than they actually occurred.
Therefore, your application should be prepared for this - for example, by checking unique event identifiers and responding accordingly to avoid duplicate operations.
You can find more information about security here:
Best Practices
Your endpoint should respond quickly.
If you expect a large number of notifications, use queues or additional servers.
Monitor your endpoint to make sure notifications are being received.
What to Do If a Webhook Doesn’t Work?
Webhook issues are most often caused by an incorrect subscription configuration or an unavailable endpoint. If a webhook is not working, check the following:
Check the URL:
Make sure the URL starts with https://.
If you are using external tools (e.g. Zapier, Make), verify that the correct URL was copied from their platform.
Check the endpoint:
Livespace sends a test notification after the subscription is activated.
Your endpoint must respond with a 200 OK or 204 No Content status within 3 seconds.
If it does not respond, check your server configuration.
Check selected events:
Make sure the appropriate events are selected in the subscription.
If the webhook was previously configured (e.g. in Zapier) and you then try to create an identical subscription in another Zapier account or for another user, the webhook may not be created correctly.
Test and monitor:
Test webhook reception using tools such as Zapier, Make, or your own test endpoint.
Monitor logs on the receiving side to verify that notifications are arriving and are being processed correctly.
If, after checking the points above, the webhook still does not work, contact Livespace Support - we’ll help you identify the cause and get the notifications up and running.
Supported Events
Currently, Livespace supports:
Event | Description |
| Triggered when a new deal is created |
| Triggered when the status of a deal changes |