Yes. Krokul CRM has a verified node package for n8n. Krokul Trigger starts a workflow from any of eleven Krokul events, and the Krokul node creates, updates and finds client companies, contacts, deals, documents, payments, tasks and tickets. Both nodes work on n8n Cloud and on a self-hosted n8n.
On a self-hosted n8n, the Krokul Trigger node subscribes to Deal Won and Invoice Paid. The workflow writes the deal and the payment into your own database or warehouse, and no third-party cloud sits between Krokul and your server.
A Schedule Trigger starts the workflow, and the Krokul node with the operation Get Many on deals returns every deal changed since the last run, page by page. Later nodes upsert the rows into the target system, and the Krokul operation Save External Key stores their IDs next to the Krokul deals.
A form node or a helpdesk trigger passes the request to the Krokul node. The operation Find Contact by email links the request to the right person, Create Ticket opens the ticket in Krokul, and Create Task gives the account manager a follow-up with a due date.
The Krokul node can be attached as a tool to an n8n AI Agent node. The agent looks up a client company, reads its debt and drafts a reminder, while the Krokul key scope decides which operations the agent may run.
| n8n | Direction | Krokul | When |
|---|---|---|---|
| Krokul Trigger node (production URL) | Krokul → n8n | Any of the 11 Krokul events, filtered by pipeline and stage | At the moment of the event, while the workflow is active |
| Krokul Trigger node (test URL) | Krokul → n8n | One sample event for the editor | While you listen for a test event |
| Krokul node, Create / Update operations | n8n → Krokul | Client company, contact, deal, task, ticket, payment, project hours | A step of the workflow |
| Krokul node, Get Many operations | Krokul → n8n | Lists of deals, payments, documents with paging | Scheduled syncs |
| Krokul node, Find operations | Krokul → n8n | Contact by email or phone, company by EDRPOU, record by external key | Before a write step |
| Krokul API credential | n8n → Krokul | API key with scope and role | On every request |
https://app.krokul.com/api/v1/<object>/api-<action>.Search for Krokul in the nodes panel. It is a verified community node, so on n8n Cloud it appears like a built-in node, and on a self-hosted instance the owner allows community nodes first.
Only through a public HTTPS URL. Krokul refuses receivers on localhost and private networks such as 10.x or 192.168.x, so put n8n behind a public address or a tunnel.
n8n has a test URL and a production URL. The test URL listens only while the editor waits for a test event. Activate the workflow so Krokul Trigger switches to the production URL.
Yes. The Krokul node works as a tool of the AI Agent node, and the scope of the Krokul key limits what the agent can read or write.
Krokul delivers events only to public HTTPS addresses, so an n8n that runs on localhost or inside an office network needs a public URL for Krokul Trigger. Logic, branching and code stay in the core nodes of n8n.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
n8n is a trademark of n8n GmbH. Krokul is not affiliated with n8n.