Short answer: Drop the "Onfleet → Create Onfleet 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 |
|---|---|---|---|
Delivery Address address | string | Required | Delivery Address |
Recipient Name recipientName | string | Required | Recipient Name |
Recipient Phone recipientPhone | string | Required | Recipient Phone |
Notes notes | string | Optional | Notes |
{"address": "{{trigger.address}}","recipientName": "{{trigger.recipientName}}","recipientPhone": "{{trigger.recipientPhone}}","notes": "{{trigger.notes}}"}
{"id": "task_789","state": 0,"shortId": "def"}
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.