Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node integrates with the Basecamp API to create a new card in a specified Card Table within a project. It is useful for automating task or note creation workflows inside Basecamp projects, especially when you want to programmatically add cards to organize work items, ideas, or reminders.
Typical use cases include:
- Automatically creating task cards from form submissions or other triggers.
- Adding notes or content cards to specific columns in a project’s card table.
- Setting due dates and sending notifications to team members upon card creation.
For example, you might use this node to create a new card titled "Design Review" in the "In Progress" column of a project, with detailed content and a due date, notifying relevant collaborators.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the card will be created. Used in the API path. |
| Column ID | The numeric ID of the column within the card table where the card will be placed. Used in path. |
| Title | The title of the card. This is a required string that names the card. |
| Content | The HTML content/body of the card. Optional rich text describing details or notes. |
| Due Date | The due date for the card in YYYY-MM-DD format. If provided, it sets the deadline. |
| Send Notifications | Boolean flag indicating whether to send notifications about the new card to relevant users. |
| Return Full Response | Boolean flag to determine if the node returns the full HTTP response (status, headers, body) or just the body. |
Output
The node outputs JSON data representing the newly created card as returned by the Basecamp API. This typically includes fields such as the card's ID, title, content, due date, creation timestamps, and other metadata.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, including status code and headers, which can be useful for debugging or advanced workflows.
The node does not output binary data.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The user must provide valid credentials with access to the target Basecamp account and project.
- The node uses the Basecamp API base URL constructed dynamically from the authenticated account ID.
- No additional external dependencies beyond the Basecamp API and n8n's OAuth2 credential setup.
Troubleshooting
- Invalid Project or Column ID: If the provided project or column IDs do not exist or are incorrect, the API will return an error. Verify these IDs in Basecamp before running the node.
- Missing Required Fields: The node requires
Project ID,Column ID, andTitle. Omitting any will cause validation errors. - Authentication Errors: Ensure the OAuth2 credentials are valid and have sufficient permissions to create cards.
- Date Format Issues: The due date must be in ISO date format (
YYYY-MM-DD). Incorrect formats may cause API rejection. - Notification Failures: If notifications are enabled but fail, check user permissions and notification settings in Basecamp.
Common error messages usually relate to invalid input parameters or authentication failures. Reviewing the full response (if enabled) helps diagnose issues.