Short answer: Drop the "Basecamp → Post Message to Board" 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. |
Message Board ID message_board_id | string | Required | — |
Subject subject | string | Required | Message subject line. |
Body (HTML) content | string | Required | — |
Status status | options | Optional | — |
{"project_id": "{{trigger.project_id}}","message_board_id": "{{trigger.message_board_id}}","subject": "e.g. Quick update","content": "{{trigger.content}}","status": "{{trigger.status}}"}
{"id": 1111,"url": "https://basecamp.com/...","subject": "FYI"}
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.