Webhooks are a way for Socket to send real-time notifications to an application when specific events happen in your workspace.
Instead of continuously checking (polling) for updates via the API, webhooks let Socket push event data to your server as it happens.
In Socket, webhooks help you automate workflows like:
Notifying your systems when a proposal is approved
Triggering internal processes when a proposal is closed
Syncing proposal status changes with your CRM, analytics, or billing systems
Webhooks make your integrations faster, more reliable, and much more efficient than polling.
Supported Webhook Events
Socket currently supports the following proposal lifecycle events:
Event | When It Fires | Typical Use |
| A recipient confirms they're starting the proposal | Trigger internal notifications or kickoff workflows |
| A proposal has been fully approved | Update CRM, generate documents, notify teams |
| A proposal has been closed (signed or completed) | Finalize records, billing, reporting |
| A new version replaces an existing proposal | Archive old data, sync to versioning systems |
Where to Find Webhooks
Log into your Socket account, access the 'Practice Settings' menu then choose 'Integrations'. Finally choose to 'Show All Available Integrations' and scroll to 'Outgoing Webhook'.
Can I add multiple webhook URLs?
Socket currently supports one active webhook endpoint at a time. If you need to send events to multiple destinations — for example, both a CRM and an internal logging service — the recommended approach is to set up a single intermediary endpoint (such as a Zapier webhook or a small relay service) that receives the Socket event and forwards it on to multiple targets.
If you have a specific use case that requires multiple native endpoints, get in touch with the team at [email protected] and we can discuss options.
Support
For any queries contact [email protected]