Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
This node integrates with the Discuss Kit API to manage various content types such as discussions, blogs, bookmarks, and documentation. Specifically for the Documentation resource with the Pin operation, it allows users to pin a documentation item by its ID. Pinning typically highlights or prioritizes the document within the system.
Common scenarios where this node is beneficial include:
- Automatically pinning important documentation after creation or update.
- Managing document visibility or priority programmatically in workflows.
- Integrating pin actions into larger automation pipelines involving content management.
Example: After creating a new documentation page, you can use this node to pin it so that it appears prominently in your knowledge base.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the content (documentation) to pin. This is required. |
Output
The node outputs the JSON response returned by the Discuss Kit API after attempting to pin the specified documentation content. This output typically includes details about the pinned document or confirmation of the pin action.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Discuss Kit API.
- Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- The node uses internal helper functions to make HTTP requests to the Discuss Kit endpoints.
Troubleshooting
Common issues:
- Invalid or missing Content ID will cause the API request to fail.
- Lack of proper API authentication or expired tokens will result in authorization errors.
- Attempting to pin a non-existent or already pinned document may return errors from the API.
Error messages:
"error": "Content not found"— Verify the Content ID is correct."error": "Unauthorized"— Check API credentials and permissions.- Network or timeout errors — Ensure network connectivity and API availability.
To resolve these, confirm the Content ID is valid, ensure API credentials are correctly set up in n8n, and verify the Discuss Kit service is reachable.
Links and References
- Discuss Kit API Documentation (generic link, replace with actual if available)
- n8n HTTP Request Node documentation for understanding API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/