Skip to content
Kibi Connect
Manual Kibi Connect

n8n Integration: Automate Kibi Connect

Updated Reading time: 3 min

On this page

n8n is a workflow automation tool that you can self-host or use as n8n Cloud. Since September 19, 2026, there has been an official Community Node for Kibi Connect: It connects your platform to other systems without requiring any code to be written.

What is the n8n integration?#

Package: @weslink/n8n-nodes-kibi-connect, Version 1.0.1, MIT License, available on npm.

Source and full reference (English): https://github.com/weslinkde/n8n-nodes-kibi-connect

The package contains two nodes:

  • Kibi Connect (Action Node): 18 resources with a total of 129 operations covering the entire REST API v1 as well as the Files API — posts (feed), wiki pages, tasks, appointments, chat, groups, notifications, polls, search, meeting links, files and folders, share links, documents (DMS), media upload, time tracking, and user directory.

  • Kibi Connect Trigger: Starts a workflow as soon as Kibi delivers a webhook event — for example, a new post, a completed task, or a new file.

Prerequisites#

The REST API must be enabled. How a system administrator sets this up, as well as everything about tokens and permissions (scopes), is described on the page Kibi API.

Warnung

Note modules: For the Document resource, the Document Management module must be installed; for the Time Tracking resource, the Time Tracking module must be installed. If the respective module is not installed, Kibi responds with a 404 on the affected routes — deliberately the same response as for an unknown ID.

Setup#

1. Enable REST API#

A system administrator enables the REST API under Administration → API. The optional IP allowlist is also located there.

2. Create token#

Each person creates their own token under My Profile → Integrations, with the permissions (scopes) required for the planned operations.

Info

Tokens cannot be modified afterward. If a permission is missing later, a new token is required.

3. Assign integration slug#

If you want the trigger to be registered automatically (see below), assign an integration slug when creating the token. The slug cannot be changed afterward.

4. Install Community Node in n8n#

  1. In n8n: Settings → Community Nodes → Install, then enter the package name @weslink/n8n-nodes-kibi-connect.

  2. In the node, create the access data: Base URL (the tenant address, without a trailing slash and without /api), API Token, and Integration Slug.

  3. The connection test in the dialog confirms the setup.

The Trigger: Two Modes of Operation#

Automatic (Standard)#

When activating the workflow, the node creates the webhook endpoint in Kibi itself; when deactivating, it removes it again. This requires the token to have:

  • The permissions webhooks:read and webhooks:write

  • An integration slug

  • A person with system administrator role as the owner of the token

Info

Requires Kibi Connect 6.8.0 or newer.

Manual#

An administrator creates the endpoint themselves under Administration → Webhook Endpoints and enters the one-time displayed signature secret in the node. This method works with any Kibi Connect version that supports outgoing webhooks.

Signature verification#

Each delivery is verified via HMAC-SHA256 against the header X-Kibi-Signature. A delivery without a valid signature is responded to by the node with a 401 and does not start the workflow.

Avoid infinite loops#

Warnung

This is where customers are most likely to get into trouble: A workflow that reads from and writes to Kibi would otherwise trigger itself endlessly.

Each webhook message contains data.origin. This indicates whether the change was triggered via the API (source: api) or by a person or background process (source: ui), and which integration slug is behind it.

The option “Ignore Own Writes” in the trigger is therefore enabled by default and discards deliveries with its own slug.

Example Workflows#

Two example workflows are available in the GitHub repository under examples/ and can be loaded into n8n via Workflow → Import from File:

  • Feed announcement in chat

    Automatically announces new feed posts in a chat channel.

  • Invoice filing from mailbox

    Files PDF invoices from an email mailbox in document management and then notifies accounting via chat message.

Availability#

As of September 20, 2026: The package is available on npm and can be installed immediately in self-hosted n8n instances. Verification by n8n, which additionally enables installation directly on n8n Cloud, has been submitted and is currently under review.

See also