Zapier connects Socket to the rest of your stack in both directions. Socket events start Zaps, and Zaps create leads, clients, and notes in Socket.
Every Socket trigger is instant, so Zaps run as the event happens rather than on a polling interval.
Connecting Socket to Zapier
Socket's Zapier app requires connecting through the app list or when building a zap
Connect your Socket account to Zapier through the app page, or create a Zap and search for Socket.
Sign in to Socket when prompted to authorise the connection.
Actions run as the Socket user whose account authorised the connection. Notes added by a Zap are attributed to that user.
Reconnecting your account
Some releases require the Socket connection in Zapier to be reauthorised once. Until it is, Zaps using new triggers or fields will not see them.
Reconnect from App Connections in Zapier: find Socket, then reconnect and sign in again. Existing Zaps keep working and do not need rebuilding.
Lead triggers
Trigger | Fires when |
Lead Created | A lead is created by any route: a Socket form, the API, another Zap, or someone adding it by hand. |
Lead Stage Changed | A lead moves between pipeline stages, including your own custom stages. |
Lead Won | A lead reaches the Won stage, which happens when its proposal is won. |
Lead Lost | A lead reaches the Lost stage, whether it was marked lost directly or its proposal was lost or deleted. |
Three behaviours are worth knowing:
Lead Stage Changed also fires on won and lost, because both are stage changes. Use Lead Won or Lead Lost where only those outcomes matter.
Lead Stage Changed does not fire when a stage is deleted and its leads are moved to another stage. Bulk moves caused by a settings change are not treated as pipeline progress.
Lead Won does not fire for a lead created from an already-won proposal, because the win happened before the lead existed.
Stage names come from your own pipeline, configured in Setting up the Leads module.
Form triggers
Trigger | Fires when |
Form Response Submitted | A client submits one of your forms, on any submission route: a public link, a form sent directly, or an onboarding form attached to a proposal. |
Proposal triggers
Trigger | Fires when |
Proposal Created | A proposal is created. |
Proposal Status Changed | A proposal changes status, whatever the new status is. |
Proposal Sending | A proposal is in the process of being sent. |
Proposal Pending | A proposal has been sent and is awaiting the client's response. |
Proposal Resent | A proposal is sent to the client again. |
Proposal in Review | A proposal moves to in-review status. Pro Features only. |
Proposal Changes Requested | A team member requests changes to a proposal. Pro Features only. |
Proposal Reverted to Draft | A proposal is put back into draft. |
Proposal Won | A proposal is won, by either route. |
Proposal Won (Client Approved) | A proposal is won because the client approved it. |
Proposal Won (Internally Approved) | A proposal is won by internal approval. |
Proposal Lost | A proposal is marked as lost. |
Proposal Activated | A proposal becomes active. |
Proposal Closed | A proposal is closed. |
Proposal Deleted | A proposal is deleted. |
Proposal Superseded | A proposal is replaced by another proposal. |
Proposal Start Date Confirmed | A proposal's start date is confirmed. |
Proposal Renewal Started | A renewal is started on a proposal. |
Proposal Adjustment Started | An adjustment is started on a proposal. |
Proposal statuses
Proposal Status Changed reports the new status as one of the following values:
draft, in_review, sending, pending, won, active, lost, superseded, closed
in_review only occurs on practices with Pro Features enabled.
Where a Zap only needs one of these, the dedicated trigger for that status is a narrower starting point than filtering the output of Proposal Status Changed.
Actions
Three actions write into Socket, from a trigger in another app.
Create Lead
Creates a lead with its client and contact details, and optionally a first note.
Field | Required | Notes |
Client Name | Yes |
|
Contact Name | Yes |
|
Contact Email | Yes |
|
Pipeline Stage | No | Lists your own stages. The lead is created in the stage you choose. |
Lead Lane (legacy) | No | The earlier stage field, kept working for existing Zaps. |
Lead Title | No |
|
Lead Temperature | No |
|
Deal Size | No |
|
Deal Value | No |
|
Client Entity Type | No |
|
Registration Number | No |
|
Client Code | No |
|
Contact Phone Number | No |
|
Note Heading | No |
|
Note | No | Creates a note on the lead as it is created. |
Where no pipeline stage is chosen, the lead is created in the leftmost stage of your board.
Leads created through Zapier get Companies House enrichment in the same way as leads created in the app.
Add Note to Lead
Adds a note to a lead that already exists.
Field | Required |
Lead | Yes |
Note | Yes |
Note Heading | No |
The note is attributed to the Socket user whose account is connected to Zapier.
Create Client
Creates a client record without a lead or proposal attached.
Field | Required |
Client Name | Yes |
Primary Contact Name | Yes |
Primary Contact Email | Yes |
Entity Type | No |
Status | No |
Company Registration Number | No |
Tax Country Code | No |
Client Code | No |
Client Aliases | No |
Primary Contact Phone | No |
Webhooks and the API
The same events that start Zaps also fire on Socket's outgoing webhooks, so an automation platform other than Zapier can subscribe to them directly. Make.com reads them natively.
The lead write API updates lead details, moves leads between stages, and adds notes, covering the same ground as the Zapier actions. See Getting started with the Socket API.
Common questions
Why has my Zap stopped seeing a trigger or field that exists on the Zapier page? The Socket connection may need reauthorising. Reconnect Socket from App Connections in Zapier.
Why did a Zap on Lead Stage Changed run when a lead was won? Winning a lead is a stage change, so both Lead Stage Changed and Lead Won fire. Use Lead Won on its own where only the outcome matters.
Why did nothing fire when I deleted a stage and its leads moved? Leads moved by deleting a stage do not fire Lead Stage Changed.
Why did a lead created from a won proposal not fire Lead Won? The proposal was already won when the lead was created, so there was no win event for Socket to report.