Short answer: Drop the "Salesforce → Update Contact" 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 |
|---|---|---|---|
Contact ID contact_id | string | Required | — |
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). |
Job Title Title | string | Optional | — |
Account ID AccountId | string | Optional | — |
{"contact_id": "{{trigger.contact_id}}","Email": "e.g. user@example.com","Phone": "e.g. +14155551234","Title": "{{trigger.Title}}","AccountId": "{{trigger.AccountId}}"}
{"id": "{{inputs.contact_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.