Short answer: Drop the "Salesforce → Convert 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 |
|---|---|---|---|
Lead ID leadId | string | Required | — |
Converted Status convertedStatus | string | Required | — |
Skip Opportunity Creation doNotCreateOpportunity | options | Optional | — |
Opportunity Name (if creating) opportunityName | string | Optional | — |
{"leadId": "{{trigger.leadId}}","convertedStatus": "{{trigger.convertedStatus}}","doNotCreateOpportunity": "{{trigger.doNotCreateOpportunity}}","opportunityName": "{{trigger.opportunityName}}"}
[{"isSuccess": true,"actionName": "convertLead","outputValues": {"leadId": "00Q...","accountId": "001...","contactId": "003...","opportunityId": "006..."}}]
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.