Short answer: Drop the "Basecamp → Create To-do" 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 |
|---|---|---|---|
Project ID project_id | string | Required | The Project ID assigned by Basecamp. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
To-do List ID todoset_id | string | Required | — |
Title content | string | Required | — |
Description (HTML) description | string | Optional | — |
Assignee user IDs assignee_ids | array | Optional | — |
Due Date due_on | string | Optional | YYYY-MM-DD |
{"project_id": "{{trigger.project_id}}","todoset_id": "{{trigger.todoset_id}}","content": "{{trigger.content}}","description": "{{trigger.description}}","assignee_ids": "{{trigger.assignee_ids}}"}
{"id": 9876,"url": "https://basecamp.com/...","status": "active","content": "Follow up"}
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.