Short answer: Drop the "Salesforce → Create Salesforce 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 | Optional | First Name. e.g. "John" |
Last Name LastName | string | Required | Last Name. e.g. "Doe" |
Company Company | string | Required | e.g. "Acme Inc" |
Email Email | string | Optional | e.g. "john@acme.com" |
Phone Phone | string | Optional | e.g. "+15551234567" |
Title Title | string | Optional | e.g. "e.g. VP of Sales" |
Lead Source LeadSource | options | Optional | Lead Source. Options: Web, Phone Inquiry, Partner Referral, Purchased List, Other |
Status Status | options | Optional | Options: Open - Not Contacted, Working - Contacted, Closed - Converted, Closed - Not Converted |
Description Description | string | Optional | e.g. "Additional notes about this lead" |
{"FirstName": "John","LastName": "Doe","Company": "Acme Inc","Email": "john@acme.com","Phone": "+15551234567"}
{"id": "00QDn00000XXXXX","errors": [],"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.