Short answer: Drop the "Salesforce → Create Salesforce Task" 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 |
|---|---|---|---|
Subject Subject | string | Required | e.g. "e.g. Follow up with prospect" |
Status Status | options | Optional | Options: Not Started, In Progress, Completed, Waiting on someone else, Deferred |
Priority Priority | options | Optional | Options: High, Normal, Low |
Related Contact/Lead ID WhoId | string | Optional | ID of the Contact or Lead this task is related to |
Related Record ID WhatId | string | Optional | ID of the Account, Opportunity, or other record this task is related to |
Due Date ActivityDate | string | Optional | Task due date (YYYY-MM-DD) |
Description Description | string | Optional | e.g. "Additional details about this task" |
Owner ID OwnerId | string | Optional | Salesforce user ID to assign this task to. Defaults to the current user. |
{"Subject": "e.g. Follow up with prospect","Status": "{{trigger.Status}}","Priority": "{{trigger.Priority}}","WhoId": "e.g. 003Dn00000XXXXX","WhatId": "e.g. 001Dn00000XXXXX"}
{"id": "00TDn00000XXXXX","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.