Signed contracts into Salesforce, through webhooks

Pick the record

• Lead or contact: create or update the person who signed, from data.recipient on recipient.completed.
• Opportunity: on envelope.completed, find the opportunity and move it to Closed Won with the contract amount. Put a reference both systems know, like the quote number, in a text box on the template, and it comes back in data.fields_by_label.
• Custom object: whatever your org tracks, like a Job or an Installation, with the job address and dates from the contract.

For example, a solar installer's sales team works opportunities in Salesforce. When the homeowner signs, the opportunity moves to Closed Won, the system size and financing choice from the contract land in custom fields, and the signed PDF is attached for the permitting team.

Set it up

1. 1

   Catch the webhook

   Create a Zapier Catch Hook, a Make Custom webhook or an n8n Webhook node, and add its URL in Settings › Developers › Webhooks with the events you need, usually recipient.completed and envelope.completed.

2. 2

   Sign a test contract

   Use the template you'll send for real, so field labels arrive with values the tool can map.

3. 3

   Find the record

   Look it up first: Zapier's Salesforce Find Record, Make's Search records (SOQL), or a search in the n8n Salesforce node. Match people on email and opportunities on your reference.

4. 4

   Create or update

   Use Create Record or Update Record in Zapier, or Create or update a record in Make, mapping from data.fields_by_label, data.recipient and data.envelope.

5. 5

   Attach the signed PDF

   On envelope.completed, fetch data.signed_pdf.url within 24 hours and attach the file to the record. In Zapier, Add File to Record does it in one step.

Things to know

• Salesforce only allows API connections on some editions. The automation tool's Salesforce connection needs one, so check yours first.
• Field-level security and validation rules still apply. The user the integration signs in as needs edit access to every field you map.
• Dates arrive as ISO timestamps, like data.envelope.completed_at. A Salesforce date field may need just the date part; use a formatter step.
• Checkboxes arrive as the text true or false, which most tools convert for a Salesforce checkbox field, but test it once.
• Each SignMaster message carries an id starting evt_ that stays the same on a retry. Store it on the record if a duplicate update would cause trouble.

Going the other way

Salesforce can also start a contract. A Flow with an HTTP callout, Apex, or a Zap triggered by a Salesforce change can call the SignMaster REST API to create and send an envelope from a template, prefilled with the opportunity's details, using an API key that holds the envelopes:write scope.