n8n Integration: Automate Kibi Connect
Updated Reading time: 5 min
On this page
- Set up webhooks
- Available events
- Test and monitor endpoint
- Check signature
- What is the n8n integration?
- Setting up n8n
- 1. Enable the REST API
- 2. Create a token
- 3. Install the Community Node
- The Trigger: Two Operating Modes
- Automatic (Default)
- Manual
- Signature Verification
- Avoiding infinite loops
- Example Workflows
- Availability
- Further Links
With webhooks, your platform reports events such as new posts or completed tasks to other systems in real time. n8n is a workflow automation tool that you can self-host or use as n8n Cloud. With the official Community Node for Kibi Connect, you connect your platform to other systems without writing code.
Info
Webhooks and the REST API are enabled by system admins. Webhook endpoints in the administration are also managed only by system admins.
Set up webhooks#
A webhook endpoint is an address to which the platform sends a signed message for the selected events.
Open Administration → Integrations → Webhooks.
Set the switch for Outgoing Webhooks to Active. By default, it is off, meaning the platform sends nothing.
Click Create Webhook Endpoint.
Enter Name and URL, and select at least one event under Subscribed Events.
Click Create.
Immediately copy the Webhook Secret and click Done. It is only displayed once.
Warning
The URL must be publicly accessible. The platform rejects addresses in the internal network: "Please provide a publicly accessible address." Redirects are not followed, so respond directly at the registered URL with a success status (2xx). If you lose the Secret, delete the endpoint and create a new one.
Available events#
You can subscribe to events in these areas:
Users: created, updated, deactivated
Posts: created, updated, deleted
Calendar entries: created, updated, canceled, restored
Tasks: created, updated, completed, assigned, plus comments, attachments, and logged task times
Groups: created, member added, member removed
Wiki pages: created, updated, deleted
Forms: form response received
Contacts: created, updated, deleted
Companies: created, updated, deleted
Info
Events for contacts and companies do not include names or contact details, only the IDs and visibility. Your receiver reads the actual data using a token with the contacts:read permission. The data visible depends on the permissions of the user to whom the token belongs.
Test and monitor endpoint#
The table displays for each endpoint: Name, URL, subscribed Events, whether it is Active, the number of Errors, and the last delivery time. On the right of each row are action icons: Edit, Send test, Deactivate, and Delete. With Only faulty, you hide all endpoints without errors.
Click Send test (paper airplane icon) in the endpoint's row.
Confirm in the dialog with Send test. The platform sends a test.ping event via the real delivery path and reports Test webhook sent.
Click Edit in the row and open the Delivery Log tab. There you see for each delivery: timestamp, event, attempt, success, status, duration, and errors. Use the search field Event to find deliveries for a specific event.
Retries: If a delivery fails or your receiver does not respond within 10 seconds, the platform tries a total of three times.
Automatically deactivated: After 10 consecutive failures, the platform deactivates the endpoint and notifies the system admins. Then check the address and reactivate the endpoint.
Delete: Deletes the endpoint along with its delivery log. This cannot be undone.
Check signature#
Each delivery includes the header X-Kibi-Signature (HMAC-SHA256). Verify it in your receiver using the Secret and a timing-safe comparison, such as hash_equals in PHP or crypto.timingSafeEqual in Node.js. This ensures the message is genuinely from your platform. You do not need to adjust the n8n trigger for this, as it checks the signature itself.
What is the n8n integration?#
Package: @weslink/n8n-nodes-kibi-connect, MIT license, available on npm. Source and full reference (English): GitHub repository.
The package contains two nodes:
Kibi Connect (action node): 18 resources with a total of 129 operations covering the REST API: posts, 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 the platform delivers a webhook event, for example a new post or a completed task.
Warning
For the Document resource, the document management module must be installed; for Time Tracking, the time tracking module. If the module is not installed, the platform responds to the affected routes with 404, deliberately just as with an unknown ID.
Setting up n8n#
The n8n card under Integrations → Overview shows whether everything is ready. As long as the REST API is disabled, it shows Not set up and Requires the REST API. Set up takes you directly to the correct page, Instructions to the npm package.

1. Enable the REST API#
Open Administration → Integrations → API.
Turn on Enable REST API and click on Save.

On the same page, you can use Enable IP restriction to limit the addresses and Restrict token creation to specific roles to define who is allowed to create tokens. More about this can be found on the page Kibi API.
2. Create a token#
Open your profile and the Integrations tab.
In the API section, click on Create new token.
Enter a Name and, under Permissions, check the scopes your operations need. For the automatic trigger, these are webhooks:read and webhooks:write.
Enter an Integration identifier, for example n8n. The node calls this field Integration Slug.
Click on Create token and copy the token.

Info
Token and integration identifier cannot be changed later. If a permission is missing later, a new token is needed. A token always acts as the person to whom it belongs.
3. Install the Community Node#
In n8n, open Settings → Community Nodes → Install and enter the package name @weslink/n8n-nodes-kibi-connect.
In the node, create the credentials Kibi Connect API: Base URL (the address of your platform, without a trailing slash and without /api), API Token, and Integration Slug.
The connection test in the dialog confirms the setup.
The Trigger: Two Operating Modes#
Automatic (Default)#
When the workflow is activated, the node creates the webhook endpoint on your platform itself; when deactivated, it removes it again. The endpoint also appears in the table under Webhooks. This requires:
The Outgoing Webhooks switch is set to Active.
The token has the permissions
webhooks:readandwebhooks:write.The token has an integration identifier.
The token belongs to a person with the System Admin role.
Manual#
Turn off Register Webhook Automatically in the node if the token does not meet these requirements or if the administration wants to manage the endpoints itself:
Copy the webhook URL of the node from the n8n editor.
Use it to create an endpoint under Webhooks as described above.
Enter the one-time displayed secret in the node in the Webhook Secret field.
Signature Verification#
Each delivery is verified using HMAC-SHA256 against the X-Kibi-Signature header. The node responds to a delivery without a valid signature with 401 and does not start the workflow.
Avoiding infinite loops#
Warning
A workflow that reads and writes to the platform would otherwise trigger itself endlessly. Every webhook message carries data.origin. This indicates whether the change was triggered via the API (source: api) or by a person or a background process (source: ui), and which integration identifier is behind it.
The Ignore Own Writes option in the trigger is therefore enabled by default and discards deliveries with your own identifier. This has two consequences:
A token without an integration identifier cannot recognize anything as its own change. The option then has no effect.
Two workflows with the same identifier also ignore each other's changes. Give each integration its own identifier if you do not want this.
Example Workflows#
Two example workflows are located in the GitHub repository under examples/ and can be loaded in n8n via Workflow → Import from File:
Feed announcement in chat (
announce-new-posts-in-chat.json): Automatically announces new posts in a chat.Invoice filing from the mailbox (
file-invoices-from-email-into-the-dms.json): Files PDF invoices from an email mailbox in the document management system and subsequently notifies the accounting department via chat message.
Availability#
The package is available on npm and can be installed immediately in self-hosted n8n instances. The package documentation also mentions the same installation for n8n Cloud. If your n8n Cloud instance does not offer the package, use a self-hosted instance or webhooks with your own receiver.