Short answer: You can create onfleet task in Onfleet by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Onfleet Create Onfleet Task action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.