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 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 lets you reposition a column by specifying the source column, target column, and the desired position. This is useful for dynamically reorganizing data layouts without manually dragging columns in a UI.
Practical examples include:
- Automating the rearrangement of task columns based on priority changes.
- Programmatically adjusting views in dashboards or reports.
- Integrating with other workflows where column order needs to be updated based on external triggers.
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 identifier of the column to be moved (the source column). |
| Target Id | Numeric identifier of the column that will be the reference point for the move (target). |
| Position | Numeric value indicating the new position index for the source column relative to target. |
Output
The node outputs JSON data representing the result of the move column operation. This typically includes confirmation of the move, updated column order, or any relevant metadata returned by the API after repositioning the column.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing card tables.
- The node depends on a REST API endpoint that supports moving columns within card tables.
- Proper configuration of base URL and authentication headers 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 credentials may lead to authorization errors.
- Providing an out-of-range position value might result in errors or unexpected behavior.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and re-authenticate if needed.
- "Resource not found": Verify that Bucket Id, Card Table Id, Source Id, and Target Id are correct and exist.
- "Invalid position value": Ensure the position number is within the valid range for the card table columns.
Resolving these usually involves verifying input parameters, refreshing credentials, and consulting API documentation for valid ranges.
Links and References
- Refer to the official API documentation of the card table service for detailed information on column operations.
- n8n documentation on creating and using custom nodes with API integrations.