Actions119
- 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
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Card Table → Create a Card
AI-generatedOverview
This node operation creates a new card in a specified column within a project (bucket) in Basecamp's Card Table resource. It is useful for automating task or item creation in project management workflows, such as adding new tasks with titles, content, due dates, and notification preferences to a project board.
Use Case Examples
- Automatically create a task card in a project column when a new issue is reported.
- Add a reminder card with a due date to a project board based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the card will be created. Used in the API endpoint path. |
| Column ID | The ID of the column within the project where the card will be placed. Used in the API endpoint path. |
| Title | The title of the card to be created. This is a required field and is sent in the request body. |
| Content | The HTML content or description of the card. This is optional and sent in the request body. |
| Due Date | The due date for the card, formatted as a date string (YYYY-MM-DD). This is optional and sent in the request body. |
| Send Notifications | Boolean flag indicating whether to send notifications about the card creation. Sent in the request body. |
| Return Full Response | Boolean flag to determine if the full HTTP response (status code, headers, body) should be returned instead of just the response body. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
id- The unique identifier of the created card.title- The title of the created card.content- The content or description of the created card.due_on- The due date of the created card.notify- Indicates if notifications were sent for the card creation.created_at- Timestamp when the card was created.updated_at- Timestamp when the card was last updated.
Dependencies
- Basecamp API authentication via OAuth2
Troubleshooting
- Ensure the Project ID and Column ID are correct and accessible with the provided credentials.
- Verify that the Title field is not empty as it is required.
- Check network connectivity and proxy settings if requests fail.
- If SSL errors occur, consider enabling the option to ignore SSL issues, but only if safe to do so.
- If the API returns errors, review the full response if the 'Return Full Response' option is enabled to diagnose issues.
Links
- Basecamp API Documentation - Official documentation for Basecamp API endpoints and usage.