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. It is useful when you want to reorder columns to better reflect priorities, workflows, or categorization of data. For example, if you have a table representing tasks with columns for status, priority, and due date, you might want to move the "Priority" column to appear before "Status" for easier visibility.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket (a container or grouping) where the card table resides. |
| Card Table Id | The identifier of the specific card table containing the column to be moved. |
| Source Id | The identifier of the column that you want to move (the source column). |
| Target Id | The identifier of the column relative to which the source column will be moved. |
| Position | The new position index for the source column relative to the target column (e.g., 1). |
Output
The output JSON contains the response from the API after moving the column. This typically includes confirmation of the move operation and possibly the updated state of the card table or the moved column. The exact structure depends on the external API's response but generally confirms success or failure.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing the card tables.
- The base URL for API requests is dynamically constructed using the authenticated user's account ID.
- The node relies on an OpenAPI specification to define its properties and request structure.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id, Card Table Id, Source Id, or Target Id can cause the operation to fail.
- Incorrect position values may result in unexpected ordering or errors.
- Authentication failures if the API key or OAuth token is invalid or expired.
Error Messages:
- "Resource not found" — Check that the Bucket Id and Card Table Id are correct and exist.
- "Invalid column identifiers" — Verify that Source Id and Target Id correspond to existing columns.
- "Unauthorized" — Ensure the API credentials are valid and have sufficient permissions.
Resolving these usually involves verifying input parameters and refreshing or reconfiguring credentials.
Links and References
- Refer to the external API documentation for "Card Tables" and column management for detailed behavior and additional options.
- Consult n8n documentation on setting up API credentials and using OpenAPI-based nodes.