Get Lead: Salesforce action

Inputs

The fields this action accepts.

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.

Sample request

{
  "lead_id": "{{trigger.lead_id}}"
}

Returns

{
  "Id": "00Q5e...",
  "Email": "jane@acme.com",
  "Phone": "+1-555-0100",
  "Status": "Open - Not Contacted",
  "Company": "Acme Inc",
  "LastName": "Doe",
  "FirstName": "Jane"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Lead.

What does the Get Lead action do in Salesforce?

Retrieves a single Salesforce Lead record by ID with all of its standard and custom fields. The standard read after a lead trigger fires.

What inputs does Get Lead require?

Required: Lead ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Salesforce returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Lead support batch operations?

Yes. Run Get Lead inside a Loop node to process arrays. Tiny Command handles Salesforce's rate limits automatically so you don't have to throttle manually.

More actions