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, documentation, comments, labels, boards, and search queries. Specifically for the Discussion - Publish operation, it publishes a draft discussion post by sending a publish request to the API.
Typical use cases include:
- Automating the publishing of drafted discussion posts after review or enrichment.
- Integrating discussion content publishing into larger workflows, e.g., content approval pipelines.
- Managing community or forum discussions programmatically.
Example: After creating a draft discussion post in a previous step, this node can be used to publish that post publicly by providing its Content ID.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the discussion content (post) to be published. This is required. |
Output
The node outputs the JSON response returned by the Discuss Kit API after publishing the discussion post. This typically includes the full details of the published discussion post, such as its ID, title, content, status, timestamps, and any metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Discuss Kit API endpoint.
- Optionally uses an API authentication token or key configured in n8n credentials to authorize requests.
- Relies on the internal helper function to make HTTP requests to the Discuss Kit API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Content ID will likely result in an error from the API indicating the post was not found.
- Missing or incorrect API authentication may cause authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Post not found"or similar indicates the Content ID does not correspond to any existing draft."Unauthorized"or"Authentication failed"suggests missing or invalid API credentials.- Timeout or network errors indicate connectivity issues; verify network and API availability.
Resolutions:
- Double-check the Content ID value and ensure the post exists and is in a draft state.
- Confirm API credentials are correctly set up in n8n.
- Test API connectivity outside n8n to isolate network issues.
Links and References
- Discuss Kit API Documentation (general reference for API endpoints)
- n8n Documentation for configuring credentials and HTTP request nodes