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 in a specified card table within a project management or organizational tool that uses "Card Tables" as a resource. It allows users to add structured information such as title, content, due date, and notification preferences to a particular bucket and column in the card table.
Common scenarios where this node is beneficial include:
- Automating task creation in project management workflows.
- Adding new items or notes to categorized lists or boards.
- Integrating with other systems to dynamically generate cards based on external events or data.
For example, you could use this node to automatically create a task card in a specific project bucket and column when a new issue is reported in a bug tracking system.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (a container or grouping) where the card will be added. |
| Column Id | Numeric identifier of the column within the bucket where the card should be placed. |
| Title | The title or main heading of the card. |
| Content | Additional descriptive text or details for the card. |
| Due On | Due date for the card, typically in string format (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. This output typically includes all properties of the card such as its unique ID, title, content, associated bucket and column IDs, due date, and any metadata returned by the API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the card, but this operation focuses on JSON data only.
Dependencies
- Requires an API key credential for authenticating with the external service managing the card tables.
- Needs the Basecamp API configured with the appropriate base URL and authentication token.
- The node depends on the "@devlikeapro/n8n-openapi-node" package for building request properties from the OpenAPI specification.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like Bucket Id, Column Id, or Title are not provided. Ensure these are set before execution.
- Authentication Failures: If the API key or OAuth2 credentials are invalid or expired, the node will fail to connect. Verify and refresh credentials as needed.
- Invalid Date Format: Providing an incorrectly formatted "Due On" date string might cause API errors. Use ISO 8601 date format (e.g., "2024-12-31T23:59:59Z").
- Permission Issues: Lack of permissions to create cards in the specified bucket or column can result in authorization errors. Confirm user access rights.
- API Rate Limits: Frequent requests might hit rate limits imposed by the external service, causing temporary failures.