n8n

n8n workflows can create, update, summarize, and route work, or react to workspace events, through the REST API or the MCP server. For other automation options, see Build with One Horizon.

Call the REST API

The REST API handles direct HTTP requests from n8n, such as creating a bug from an alert, adding a comment, updating work, or pulling data into a report.

Create an API key, store it in n8n credentials, then use the HTTP Request node with bearer authentication:

Authorization: Bearer <api-key>

For workspace routes, use current as the workspace ID:

https://onehorizon.ai/api/v1/workspaces/current/tasks

Choose the REST API for workflows your team owns that act on one workspace. Choose MCP when the workflow should use assistant-style tools under a person's account.

Connect through MCP

Through MCP, workflows can create and update tasks, list planned or completed work, list blockers, generate team recaps, list teams, and find members. You need n8n 1.121.2 or later. The MCP endpoint is:

https://mcp.onehorizon.ai/mcp

1. Add an MCP Client node to the workflow.

2. Point the node at the endpoint above and select MCP OAuth2 authentication.

3. When the workflow first runs, complete sign-in in the browser.

n8n's MCP Access settings page does the opposite: it exposes n8n workflows to MCP clients. It does not connect n8n to your workspace.

Frequently asked questions