n8n
n8n automations can create, update, summarize, and route work.
What automation tools do
n8n fits workflows that create work, update work, generate reports, sync data, or react to workspace events.
Use 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/tasksChoose the REST API for workflows owned by your team that act for one workspace. Choose MCP when the workflow should call assistant-style tools through OAuth.
n8n and MCP
n8n connects through MCP. Workflows can create and update tasks, list planned or completed work, list blockers, generate team recaps, list teams, find members, and sync data between tools.
Use the MCP Client node in n8n 1.121.2 or later, point it at:
https://mcp.onehorizon.ai/mcpChoose MCP OAuth2 authentication and complete OAuth the first time the workflow runs.
Add an MCP Client node to the workflow before configuring credentials.
Point the node at the hosted MCP endpoint and select MCP OAuth2 authentication.
When the workflow first runs, complete OAuth in the browser.
The n8n MCP Access settings page exposes n8n workflows to MCP clients. It does not connect n8n to your workspace. To call the API from n8n, use the MCP Client node or an HTTP Request node.
MCP works best when the workflow needs assistant-style work tools rather than direct HTTP calls.
Other automation paths
If n8n is not the right automation surface, compare the available options in Build with One Horizon.