Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node operation creates a new card within a specified card table in Basecamp. Cards are individual items or tasks organized into columns and buckets, commonly used for project management and task tracking. This operation is useful when you want to programmatically add new cards with specific details such as title, content, due date, and notification preferences.
Practical examples include:
- Automatically creating task cards from form submissions.
- Adding reminder cards based on calendar events.
- Generating cards from issue trackers or other external systems integrated via n8n.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the card will be created. |
| Column Id | Numeric identifier of the column within the bucket where the card will be placed. |
| Title | The title or name of the card. This is a required string that identifies the card. |
| Content | Optional detailed description or content of the card. |
| Due On | Optional due date for the card, typically formatted as a string (e.g., ISO date). |
| Notify | Boolean flag indicating whether to send notifications related to this card creation. |
Output
The node outputs JSON data representing the newly created card object as returned by the Basecamp API. This includes all relevant card details such as its ID, title, content, associated bucket and column IDs, due date, and any metadata provided by the API.
If the node supports binary data output, it would typically relate to attachments or files linked to the card, but this operation focuses on card creation and does not handle binary data directly.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the user's Basecamp account ID.
- Proper permissions on the Basecamp account to create cards in the specified buckets and columns.
Troubleshooting
- Invalid Bucket or Column Id: If the provided bucket or column ID does not exist or the user lacks access, the API will return an error. Verify IDs and permissions.
- Missing Required Fields: The "Title", "Bucket Id", and "Column Id" fields are mandatory. Omitting these will cause validation errors.
- Authentication Errors: Ensure the API key or OAuth token is valid and has not expired.
- Date Format Issues: The "Due On" field should be in a proper date string format; otherwise, the API may reject it.
- Notification Flag Misuse: The "Notify" boolean should be true or false; invalid values might cause unexpected behavior.