Webhooks in workflows in Livespace allow you to automatically send data to external systems in response to specific events.
Data is sent only when defined conditions are met (e.g., a change in the sales opportunity status or completion of a custom field). This allows you to control which integrations are triggered.
In this article:
How do webhooks work in workflows?
A webhook in a workflow is an action that is triggered when specific conditions are met.
A trigger occurs (e.g., a change in the deal status)
Conditions are evaluated (e.g., which sales process the workflow should apply to)
If the conditions are met, the action is executed - the webhook is sent.
What does this mean in practice?
A webhook is not sent on every change, but only when the defined conditions you set in the workflow are met. This reduces the number of unnecessary calls to external systems.
When can a webhook be sent?
A webhook can be sent in response to specific events in Livespace.
Sending a webhook after completing a data field
A webhook can be sent when data fields in a deal are completed or updated.
Remember that a single field can be used in only one workflow.
Sending a webhook after a change in the deal status
A webhook can also be sent when the status of a deal changes.
This solution is especially useful when you want to trigger further processes after a deal is closed—for example, sending data to an invoicing system.
Filtering webhooks by sales process
In both of the cases above, you can further narrow the webhook’s action by setting a condition based on the sales process.
How to configure a webhook?
Go to Workflows.
2. Create a new workflow. Click the Create New button.
3. Add:
Trigger – a change in a data field or the deal status.
Condition (optional) – which sales process the workflow applies to.
Effect – Send data.
4. In the Effect section, paste the webhook URL.
Not sure where to find the URL? See the information below.
5. Save and activate the workflow. After saving, you can test the webhook’s operation. You will also see the Secret, which helps identify the data source and enhances security.
The same view allows you to manage workflows: edit, deactivate, or delete them.
What does a webhook contain?
A webhook sent from a workflow contains:
Deal data
System fields
Custom fields
When testing, keep in mind that the first request is a test notification to your endpoint to ensure it is configured correctly.
Security and operation
Webhooks in workflows in Livespace are designed to securely transmit data to external systems.
All data sent via webhooks is transmitted exclusively over an encrypted HTTPS connection.
Each webhook request includes a special verification header generated based on the subscription secret.
If the endpoint does not respond correctly (returns an error), Livespace automatically retries sending the webhook (2 retries).
You can manage, edit, or delete webhook workflows in Account Settings -> Webhooks.
You can find more information about security here:
Use cases
You can use webhooks in workflows to:
Send data to Zapier or Make after a deal is won. This allows you, for example, to automatically issue an invoice or update data in your accounting system.
Send data to marketing tools after a deal is lost, enabling you to launch a customer recovery campaign.
Synchronize data with another system only for a selected sales process. Information is sent only when it is truly needed.
Recommended reading: