Update Lead: Close 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	Lead ID. Example: lead_abc123
Company Name name	string	Optional	Company Name
Website url	string	Optional	A fully qualified URL (https://...) for the website.
Description description	string	Optional	Description
Status ID status_id	string	Optional	Status ID. Example: stat_abc123

Sample request

{
  "lead_id": "e.g. lead_abc123",
  "name": "{{trigger.name}}",
  "url": "e.g. https://example.com/path",
  "description": "{{trigger.description}}",
  "status_id": "e.g. stat_abc123"
}

Returns

{
  "id": "lead_abc123",
  "display_name": "Acme Inc"
}

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

FAQ

Questions about Update Lead.

What does the Update Lead action do in Close?

Partial update on lead fields — only passed fields change. For "Apollo enriched this lead → write back to Close" augmentation patterns and for "stage change in external system → reflect in Close" sync workflows.

What inputs does Update 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 Close 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 Update Lead support batch operations?

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

More actions