Short answer: Drop the "AgencyHandy → 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 |
|---|---|---|---|
First Name firstName | string | Required | Contact's first (given) name. |
Last Name lastName | string | Required | Contact's last (family) name. |
Email email | Required | The email address. Used as the recipient or identifier depending on context. | |
Source source | string | Optional | Source. Example: Website, Referral |
Lead Value leadValue | string | Optional | Lead Value. Example: 5000 |
Status status | options | Optional | Status. Options: New, Contacted, Qualified, Proposal Sent, Won, Lost |
Country country | string | Optional | Country |
City city | string | Optional | City |
Website website | string | Optional | Website |
Address address | string | Optional | Address |
{"firstName": "e.g. Jane","lastName": "e.g. Doe","email": "e.g. user@example.com","source": "e.g. Website, Referral","leadValue": "e.g. 5000"}
{"data": [{"_id": "abc123","email": "john@example.com","lastName": "Doe","firstName": "John"}],"success": true}
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.