Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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 | The numeric identifier of the bucket where the card will be created (required). |
| Column Id | The numeric identifier of the column within the bucket where the card will be placed (required). |
| Title | The title of the card; serves as the main label or headline for the card (required). |
| Content | Additional descriptive text or details for the card. |
| Due On | The due date for the card, typically formatted as a string date (e.g., "YYYY-MM-DD"). |
| 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 properties of the card 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 media 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 bucket and column are necessary.
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: Omitting required fields like Bucket Id, Column Id, or Title will cause validation errors. Ensure these are provided.
- Authentication Errors: Invalid or expired API credentials will prevent the request from succeeding. Refresh or reconfigure the API authentication token.
- Date Format Issues: The "Due On" field should be in a valid date string format. Incorrect formats may cause the API to reject the request.