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 interacts with the "Card Tables" resource of a service (likely Basecamp, based on the bundled code context) to retrieve information about a specific column within a card table. The "Get Column" operation fetches details for a single column identified by its unique ID within a specified bucket (card table). This is useful when you want to programmatically access metadata or properties of a particular column in a card table, such as its name, type, or other configuration details.
Practical examples include:
- Automating workflows that need to read column configurations before processing card data.
- Integrating card table structures into reporting or dashboard tools.
- Validating column existence or properties before performing updates or inserts.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (card table) containing the column to retrieve. |
| Column Id | The numeric identifier of the specific column within the bucket to fetch details for. |
Output
The output will contain a JSON object representing the details of the requested column. This typically includes properties such as the column's ID, name, type, and any other metadata defined by the API. The exact structure depends on the external API response but generally provides comprehensive information about the column.
No binary data output is indicated or expected from this operation.
Dependencies
- Requires an API key credential for authentication with the external service (e.g., Basecamp).
- The node uses a base URL constructed dynamically using credentials, indicating it needs proper configuration of authentication tokens and possibly a workspace or account ID.
- The node depends on an OpenAPI specification file (
Basecamp.api.json) and a helper library for building properties and making requests.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Column Id values will cause the API request to fail.
- Authentication errors if the API key or OAuth token is not configured correctly.
- Network or permission issues accessing the external API.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API credentials are set up properly.
- "Not Found" or "Column does not exist": Verify that the Bucket Id and Column Id are correct and that the column exists.
- "Bad Request": Ensure that the input parameters are valid numbers and conform to expected formats.
Resolving these usually involves verifying input parameters, checking credential validity, and ensuring network connectivity.
Links and References
- Basecamp API Documentation (for understanding card tables and columns)
- n8n documentation on creating custom nodes