Connect external apps
Wire Feedjolt into automation tools with a workspace API key. n8n ships today as n8n-nodes-feedjolt on npm. Cursor and other agents use MCP OAuth, not an API key in plugin settings.
Use this section when you want Feedjolt inside an automation tool — n8n today, more later. Native Slack and Linear stay under Integrations. Coding agents stay under MCP.
Pick the right door
| You want… | Use |
|---|---|
| Slack channels or Linear issues | Integrations |
| A workflow tool talking to boards and posts | A workspace API key (fjk_) against https://api.feedjolt.com/api/v1 |
| Cursor, Claude, or another MCP client | OAuth 2.1 on /mcp/reader/ and /mcp/writer/ — MCP setup |
Do not paste a Feedjolt API key into Cursor MCP or plugin settings. Cursor connects with OAuth. The key is for REST clients such as n8n.
Available today
- n8n — community nodes for boards, posts, roadmap, changelog, statuses, and tags. Install
n8n-nodes-feedjoltfrom npm (Settings → Community nodes).
HTTP clients, scripts, and anything else that can send Authorization: Bearer fjk_… use the same REST API. Start at Developers and the OpenAPI spec at https://api.feedjolt.com/openapi.json.
Auth
- Create a key at Dashboard -> Settings -> API keys -> New key. It starts with
fjk_and is shown once. - Send it as
Authorization: Bearer fjk_…. - The workspace slug you pass must match the workspace that minted the key.
Keys need the Startup or Scale plan (same gate as the REST API). Details: API authentication.
Coming later
Zapier, Make, and Activepieces are not documented here yet. Vote on the roadmap if you want them next.
What next
MCP Troubleshooting
Fix common Feedjolt MCP errors: 402 plan required, 401 unauthorized, 403 missing scope, 429 rate limited, tag-not-found, and the delete guards on boards and statuses.
n8n
Connect n8n to Feedjolt with a workspace API key. Install n8n-nodes-feedjolt from npm via Settings → Community nodes, or npm install under ~/.n8n/nodes.