Short answer: Drop the "Salesforce → Update Lead" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Lead ID lead_id | string | Required | The Lead ID assigned by Salesforce. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
First Name FirstName | string | Optional | Contact's first (given) name. |
Last Name LastName | string | Optional | Contact's last (family) name. |
Company Company | string | Optional | — |
Email Email | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone Phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Status Status | string | Optional | — |
Rating Rating | string | Optional | — |
{"lead_id": "00Q5e...","FirstName": "e.g. Jane","LastName": "e.g. Doe","Company": "{{trigger.Company}}","Email": "e.g. user@example.com"}
{"id": "{{inputs.lead_id}}"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.