Get Lead: Close action · Tiny Command

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

Sample request

{
  "lead_id": "e.g. lead_abc123"
}

Returns

{
  "id": "lead_abc123",
  "contacts": [
    {
      "id": "cont_abc",
      "name": "John Doe",
      "emails": [
        {
          "email": "john@acme.com"
        }
      ]
    }
  ],
  "display_name": "Acme Inc"
}

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 Close?

Returns a lead by ID with contacts, custom fields, opportunities, and recent activities. The standard lookup for enrichment workflows or for round-trip operations that need the current lead state.

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 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 Get Lead support batch operations?

Yes. Run Get 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