Experimental feature. The n8n integration has not yet been fully tested. An administrator must deliberately enable it under Settings → Advanced → Other; until it is enabled, the n8n tab and this Help Centre section remain hidden, and the /api/n8n/* endpoints are inactive.

What is n8n?

n8n is a process automation platform. The Task Manager integration works both ways:

  1. Outgoing webhooks (Task Manager → n8n) - the application automatically sends notifications to your n8n workflow when something happens (a task is created, a status changes, a message is added, a due date is approaching, etc.).
  2. Incoming API (n8n → Task Manager) - n8n can call the application to create tasks, add messages or retrieve data.

Enabling the integration

Click the cog icon (⚙) → the n8n tab. The tab is divided into two sections: “Personal automations” - configuration that applies only to you, and “Global automations” - system-wide settings shared by all users and visible only to administrators. To send events, an administrator must enable the “Enable n8n integration” switch in the global section.

A. Outgoing webhooks - notifications from the application to n8n

Configuration

  1. In the n8n tab, click “New webhook”.
  2. Enter a webhook name and the webhook URL copied from n8n (the Webhook node as the trigger, using the POST method).
  3. Select the events to be sent.
  4. (Optional) set a secret - the application will use it to sign requests (HMAC), allowing n8n to verify their authenticity.
  5. Save. You can send a test ping to check the connection.

Available events (selected)

  • Tasks: task.created, task.updated, task.status_changed, task.completed, task.deleted, task.deadline_approaching, task.overdue
  • Chats / messages: chat.message_sent, chat.mention, chat.file_uploaded
  • Users / workspace: user.created, user.login, user.logout, workspace.created
  • System: system.daily_summary, system.weekly_summary

Each request to n8n includes the event name and contextual data (data) (for example, the task ID, workspace and author).

B. Incoming API - n8n controls the application

Configuration

  1. In the n8n tab, click “New API key”.
  2. Copy the generated token (it is shown only once).
  3. In n8n, use the HTTP Request node with an authorisation header:
    Authorization: Bearer TWÓJ_TOKEN
    Actions run in the context of the user who created the key (their permissions and workspace access).

Available endpoints

  • GET /api/n8n/ping.php - token test and health check (returns information about the key and user).
  • GET /api/n8n/workspaces.php - list of available Workspaces.
  • GET /api/n8n/users.php - list of users (only for keys created by a global administrator).
  • GET /api/n8n/tasks.php?workspace_id=&status=&limit= - list of tasks.
  • POST /api/n8n/tasks.php - creates a task. JSON body:
    {
"workspace_id": 1,
"subject": "Nowe zadanie z n8n",
"description": "Opcjonalny opis",
"priority": "high",
"deadline_date": "2025-12-31",
"status": "none",
"assignees": [2, 5]
}
  • PATCH /api/n8n/tasks.php — updates an existing task, including changing its status. JSON body (task_id required, the rest of the fields are optional - you only need to supply what you want to change):
    {
"task_id": 42,
"status": "in_progress",
"priority": "high",
"deadline_date": "2026-08-01",
"subject": "Nowy temat",
"description": "Nowy opis"
}
    • status: none | in_progress | done | cancelled. Changing the status works exactly as it does from the app: an entry appears in the task's thread saying "changed the status to…", the assigned people receive an email notification, and n8n gets a task.status_changed webhook (plus task.completed when set to done).
    • deadline_date: null clears the due date. Changing the due date reschedules any reminders linked to it.
    • The remaining fields send the task.updated webhook.
    • Setting the same status again does not send anything (safe for retries in n8n).
    • If your HTTP node doesn't support the PATCH method - send the same body via POST: the presence of task_id switches the endpoint into update mode.
    • Error codes: 400 missing task_id or no fields to change, 422 invalid value (status/priority/date format), 404 the task doesn't exist or is outside the key's access, 403 no permission to change the status/edit.
  • POST /api/n8n/messages.php - adds a message to a task or chat. JSON body:
    {
"entity_type": "task",
"entity_id": 42,
"content": "Treść wiadomości"
}

Example automation workflows

  • Google Form → n8n → POST /api/n8n/tasks.php (new task in Task Manager)
  • Email from Gmail with a specific subject → n8n → task with the email content as its description
  • Status change in Jira → n8n → message/update in the linked task
  • Outgoing webhook task.created → n8n → entry in a Google Sheet / Slack notification
  • task.deadline_approaching → n8n → email/SMS reminder about an approaching due date

Troubleshooting

  • No notifications in n8n - check that the integration is enabled, the webhook is active and the URL is correct. Use a “test ping”.
  • Authorisation error (401) in the incoming API - the token is invalid or has been deleted. Create a new API key and update the Authorization header in n8n.
  • Task is not created - make sure that workspace_id exists and that the key owner has access to it and permission to add tasks.