Create Task: 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
Task Description text	string	Required	Task Description. Example: Follow up on proposal
Due Date date	string	Required	YYYY-MM-DD format
Assigned To (User ID) assigned_to	string	Optional	Assigned To (User ID). Example: user_abc

Sample request

{
  "lead_id": "e.g. lead_abc123",
  "text": "e.g. Follow up on proposal",
  "date": "e.g. 2025-01-20",
  "assigned_to": "e.g. user_abc"
}

Returns

{
  "id": "task_abc",
  "date": "2025-01-20",
  "text": "Follow up on proposal",
  "is_complete": false
}

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

FAQ

Questions about Create Task.

What does the Create Task action do in Close?

Creates a follow-up task for a sales rep tied to a lead with due date and notes. Useful for "deal stagnant for N days → create follow-up task for the AE" hygiene automation.

What inputs does Create Task require?

Required: Lead ID, Task Description, Due Date. 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 Create Task support batch operations?

Yes. Run Create Task 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