Basecamp icon

Basecamp

Interact with the Basecamp API
Join our community

Actions80

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 is useful for users who want to programmatically add task cards, notes, or items into a specific bucket and column of a card table, enabling automation of task tracking, project updates, or content organization.

Practical examples include:

  • Automatically creating a task card when a new issue is reported.
  • Adding reminder cards with due dates for upcoming deadlines.
  • Generating content cards based on form submissions or external triggers.

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 text of the card (required).
Content Optional detailed content or description for the card.
Due On Optional due date for the card, typically formatted as a string 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 JSON typically includes details such as the card's unique ID, title, content, associated bucket and column IDs, due date, and any metadata returned by the API after creation.

If the node supports binary data output, it would represent attachments or media linked to the card, but this operation focuses on JSON data describing the card itself.

Dependencies

  • Requires an API key credential for authenticating with the Basecamp API or equivalent service managing the card tables.
  • The node depends on the Basecamp API endpoint configured with the correct base URL including the user's account or project ID.
  • Proper permissions are needed to create cards within the specified buckets and columns.

Troubleshooting

  • Missing Required Fields: Errors may occur if Bucket Id, Column Id, or Title are not provided. Ensure these fields are set correctly.
  • Invalid IDs: Using non-existent bucket or column IDs will cause API errors. Verify IDs before execution.
  • Authentication Failures: If the API key or OAuth token is invalid or expired, authentication errors will appear. Refresh or reconfigure credentials.
  • Notification Issues: Setting Notify to true without proper notification setup might not trigger alerts; check notification settings in the external system.
  • Date Format Errors: The Due On field must be in a valid date string format accepted by the API; otherwise, the request may fail.

Links and References

Discussion