Basecamp icon

Basecamp

Interact with the Basecamp API
Join our community

Actions68

Overview

This node operation allows you to move a column within a card table in a project management or organizational tool that uses "Card Tables" as a resource. Specifically, it moves a column from one position to another by specifying source and target column IDs along with the desired position. This is useful for dynamically reorganizing columns to better reflect priorities, workflows, or categorization without manually dragging columns in a UI.

Practical examples include:

  • Reordering task categories in a project board.
  • Adjusting columns in a kanban-style card table to match changing team workflows.
  • Automating column rearrangement based on external triggers or conditions.

Properties

Name Meaning
Bucket Id Numeric identifier of the bucket containing the card table.
Card Table Id Numeric identifier of the specific card table where the column move will occur.
Source Id Numeric ID of the column to be moved (the source column).
Target Id Numeric ID of the column that will be the reference point for the move (the target column).
Position Numeric value indicating the new position index for the moved column relative to the target.

Output

The node outputs JSON data representing the result of the move column operation. This typically includes confirmation details such as updated column order or metadata about the affected columns. The output does not include binary data.

Dependencies

  • Requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the external service managing the card tables.
  • The node depends on the Basecamp API or a similar project management API that supports card table manipulation.
  • Proper configuration of the base URL and authentication credentials is necessary for successful API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing Bucket Id, Card Table Id, Source Id, or Target Id can cause the operation to fail.
    • Insufficient permissions or expired API tokens may lead to authorization errors.
    • Providing an out-of-range position number might result in unexpected behavior or errors.

  • Error messages:

    • "Unauthorized" or "Authentication failed": Check API credentials and refresh tokens if needed.
    • "Resource not found": Verify that the Bucket Id, Card Table Id, Source Id, and Target Id are correct and exist.
    • "Invalid position value": Ensure the position is within the valid range for the card table columns.

Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring the API endpoint is reachable.

Links and References

Discussion