Yes. Krokul CRM integrates with Albato through the Krokul app in the Albato library. Krokul events such as a new client company, a won deal or a received payment start an Albato automation, and Krokul actions create or update records when something happens in another app. You connect Krokul to Albato with an API key, without writing requests by hand.
The Krokul trigger New Company starts the automation the moment someone adds a client company. The action of a messenger app posts the name, the EDRPOU code and the manager to the sales group, so nobody asks in chat who took the client.
An automation starts with the order trigger of a shop or marketplace app in Albato. The Krokul action Find Contact checks the buyer by phone, and Create Deal adds the order to the chosen pipeline with the amount and the source. The deal appears in Krokul with the client already attached.
The Krokul trigger Payment Received fires when a payment fact is recorded on a deal. The automation notifies the warehouse, starts a shipment in a delivery app or updates a row in an accounting sheet.
When the other app has done its part, the Krokul action Add Comment writes the result into the deal feed, for example a shipment number or a sent message. Change Deal Stage moves the deal on, so the pipeline reflects work done in another service.
| Albato | Direction | Krokul | When |
|---|---|---|---|
| Trigger New Company, New Contact, Contacts Merged | Krokul → Albato | clientCompany.created, contact.created, contact.merged | At the moment of the Krokul event |
| Trigger New Deal, Deal Stage Changed, Deal Won, Deal Lost | Krokul → Albato | Deal events with pipeline and stage | When the deal changes |
| Trigger Document Created, Invoice Paid, Payment Received, Task Created | Krokul → Albato | Document, payment and task events | When the event happens |
| Action Create or Update Company, Contact, Deal, Task, Ticket | Albato → Krokul | The matching Krokul record | A step of the automation |
| Action Change Deal Stage, Record Payment, Add Comment, Log Hours | Albato → Krokul | Deal stage, payment fact, deal feed, project hours | A step of the automation |
| Search Find Contact, Find Company, Find Deal | Krokul → Albato | Existing records by email, phone, EDRPOU or external key | Before a write step |
https://app.krokul.com/api/v1/, with the header Authorization: Bearer krokul_….Each of the eleven Krokul events can start one. They cover new and merged contacts, new client companies, new deals, stage changes, won and lost deals, new tasks, new documents, paid invoices and received payments.
With a Krokul API key saved in the Albato connection. The key scope limits what the automation can read and write, and an admin can revoke it in Krokul.
Yes. The search Find Contact looks up a person by email or phone, so the next step updates the contact instead of adding a duplicate.
The failed delivery stays in the Krokul delivery log with the response code, and it can be sent again once Albato is back.
An Albato automation moves data from one trigger to its actions, so each direction is a separate automation. Albato keeps the Webhooks and HTTP Request apps for services and routes that have no ready app or action.
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.
Albato is a trademark of its owner. Krokul is not affiliated with Albato.
