Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
The node integrates with the Discuss Kit API to manage discussion boards and related content. Specifically, for the Board - Update operation, it updates the properties of an existing board by its ID. This is useful when you want to rename a board or modify its attributes in your workflow.
Practical examples include:
- Renaming a project discussion board after a rebranding.
- Updating board details dynamically based on external triggers or user input.
Properties
| Name | Meaning |
|---|---|
| Board ID | The unique identifier of the board to update. Must be provided to specify which board to modify. |
| Name | The new name to assign to the board. This will replace the current board name. |
Output
The output JSON contains the updated board object returned from the Discuss Kit API after the update operation. It typically includes fields such as the board's ID, name, color, text color, and other metadata reflecting the current state of the board.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Discuss Kit API endpoint.
- Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- Uses internal helper function to make HTTP requests to the Discuss Kit API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Board ID will result in an error from the API indicating the board was not found.
- Missing required parameters like Board ID or Name will cause the node to fail validation or the API to reject the request.
- Network or authentication errors if the API key credential is missing or incorrect.
Error messages:
"Board not found": Verify the Board ID is correct and exists."Unauthorized"or"Authentication failed": Check that the API key credential is properly set up."Validation error": Ensure all required fields are provided and valid.
Resolving these usually involves verifying input parameters and ensuring proper API credentials are configured.
Links and References
- Discuss Kit API Documentation (generic placeholder link)
- n8n documentation on creating custom nodes