Short answer: Drop the "Close → Create Lead" 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 |
|---|---|---|---|
Company Name name | string | Required | Company Name. Example: Acme Inc |
Website url | string | Optional | Website. Example: https://acme.com |
Description description | string | Optional | Description |
Contact Name contact_name | string | Optional | Contact Name. Example: John Doe |
Contact Email contact_email | string | Optional | Contact Email. e.g. "john@acme.com" |
Contact Phone contact_phone | string | Optional | Contact Phone. e.g. "+15551234567" |
Status ID status_id | string | Optional | Lead status ID from your Close pipeline |
{"name": "e.g. Acme Inc","url": "e.g. https://acme.com","description": "{{trigger.description}}","contact_name": "e.g. John Doe","contact_email": "john@acme.com"}
{"id": "lead_abc123","contacts": [{"id": "cont_abc","name": "John Doe"}],"status_id": "stat_abc123","display_name": "Acme Inc"}
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.