Short answer: Drop the "Outreach → Create Outreach 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 | Task subject. |
Note note | string | Optional | Free-form task body / notes. |
Due At dueAt | string | Optional | Due timestamp in ISO 8601 (UTC). |
Task Type ID taskTypeId | string | Required | Outreach task type ID. Common defaults: 1 (Call), 2 (Email), 3 (General). |
Owner User ID ownerId | string | Required | Outreach user the task is assigned to. |
Prospect ID prospectId | string | Optional | Optional prospect to attach the task to. |
{"subject": "Follow up with Jane re: pricing","note": "{{trigger.note}}","dueAt": "2026-04-15T17:00:00Z","taskTypeId": "3","ownerId": "12345"}
{"data": {"id": "778899","type": "task","attributes": {"note": "She asked about enterprise pricing.","dueAt": "2026-04-15T17:00:00Z","state": "incomplete","subject": "Follow up with Jane re: pricing","createdAt": "2026-04-11T10:00:00.000Z"}}}
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.