n8n
The official Scoold community node for n8n lets you trigger workflows from Scoold events and manage Scoold content - all without writing any code.
The package provides two nodes:
- Scoold Trigger - starts a workflow when a Scoold event fires (new question, answer, comment, report, etc.)
- Scoold - create, read, update, and delete posts, comments, tags, and reports; search Scoold content
Installation
Section titled “Installation”- In n8n, go to Settings → Community Nodes
- Click Install and enter the package name:
@erudika/n8n-nodes-scoold
- Confirm the installation and restart n8n if prompted
npm i @erudika/n8n-nodes-scooldThen restart your n8n instance.
Setting up credentials
Section titled “Setting up credentials”- In your Scoold Admin panel, go to the API section and generate a new JWT API key. Copy it.
- In n8n, go to Credentials → Create → Scoold API and fill in:
- Base URL - the public URL of your Scoold instance, e.g.
https://qna.cloud.scoold.com(without the trailing slash) - API Key - the JWT key you just copied
- Base URL - the public URL of your Scoold instance, e.g.
- Click Test credential. n8n calls
/api/statsto verify the key is valid.
Scoold Trigger
Section titled “Scoold Trigger”The Scoold Trigger node automatically registers a webhook in Scoold when the workflow is activated, and removes it when the workflow is deactivated. No manual webhook setup is required.
Configuration
| Parameter | Description |
|---|---|
| Event Names or IDs | One or more Scoold events to subscribe to. Loaded from your Scoold instance at /api/events. |
| Property Filter (optional) | Narrow events by object property, e.g. space:general or tags:bug|security |
You can subscribe to any Scoold event, e.g. question.create, answer.create etc.
Each trigger execution emits one n8n item per object in the event payload.
Every item includes a _scoold metadata field with the event name, timestamp, app ID, and webhook ID.
Scoold node
Section titled “Scoold node”The Scoold node lets you manage content and search your community from anywhere in a workflow. Select a Resource and an Operation to configure what the node does.
Resource: Post
Section titled “Resource: Post”| Operation | Description |
|---|---|
| Create | Create a question, answer (reply), or sticky post |
| Get | Fetch a post by ID, including its children and similar posts |
| Update | Edit the title, body, tags, or other fields of a post |
| Delete | Delete a post permanently |
| List | List questions on the front page with optional filters |
| Get Answers | Fetch the answers for a given question |
| Get Comments | Fetch the comments on a post |
| Get Revisions | Fetch the edit history of a post |
Post: Create — key parameters:
| Parameter | Description |
|---|---|
| Post Type | question, reply (answer), or sticky |
| Title | Title of the post |
| Body | Post body; supports GitHub-flavored Markdown |
| Tags | Comma-separated tags, e.g. java, spring |
| Parent Post ID | Required when Post Type is reply — the ID of the parent question |
| Additional Fields | creatorid, space, wiki, location, disable notifications |
Resource: Comment
Section titled “Resource: Comment”| Operation | Description |
|---|---|
| Create | Add a comment to a post |
| Get | Fetch a comment by ID |
| Delete | Delete a comment |
| List | List comments for a given post (paginated) |
Resource: Tag
Section titled “Resource: Tag”| Operation | Description |
|---|---|
| Create | Create a new tag |
| Get | Fetch a tag by ID |
| Update | Rename a tag or update its description |
| Delete | Delete a tag |
| List | List all tags (paginated) |
Resource: Report
Section titled “Resource: Report”| Operation | Description |
|---|---|
| Create | Submit a report for a piece of content |
| Get | Fetch a report by ID |
| Delete | Delete a report |
| List | List all reports (paginated) |
| Close | Close a report with an optional resolution note |
Report: Create — key parameters:
| Parameter | Description |
|---|---|
| Link | URL of the content being reported |
| Report Type | SPAM, OFFENSIVE, DUPLICATE, INCORRECT, or OTHER |
Resource: Search — Operation: Query
Section titled “Resource: Search — Operation: Query”| Parameter | Description |
|---|---|
| Type | Object type: question, answer, user, profile, comment, report, revision, badge, feedback |
| Query | Full-text search string (supports Lucene syntax) |
| Return All | Automatically page through all results using cursor pagination |
| Limit | Max results per page (default 50, used when Return All is off) |
| Page | Page number to fetch (used when Return All is off) |
| Sort By | Field to sort by, e.g. timestamp or votes |
| Descending | Sort order (default: newest first) |
| Split Out Items | On (default): emit one item per result. Off: emit one item with the raw { items, page, totalHits } envelope |
Example: find all unanswered questions tagged “bug”
Set Resource to Search, Type to question, Query to tags:bug AND answercount:0, enable Return All, and leave Split Out Items on.
Each question becomes a separate n8n item ready for further processing.