Short answer: Drop the "Google Tasks → Create Google 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 |
|---|---|---|---|
Task List ID tasklist | string | Required | Task List ID |
Title title | string | Required | Title |
Notes notes | string | Optional | Notes |
Due Date due | datetime | Optional | Due Date. (date/time) |
{"tasklist": "{{trigger.tasklist}}","title": "{{trigger.title}}","notes": "{{trigger.notes}}","due": "{{trigger.due}}"}
{"id": "task123","title": "Buy groceries","status": "needsAction"}
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.