Yes. Krokul CRM has an app in Make with instant trigger modules for eleven Krokul events, action modules that create and update records, and search modules that find them. A scenario places Krokul between the other apps Make supports, with routers, filters and iterators in between.
The instant trigger Watch Deal Events listens to created, stage changed, won and lost deals in one module. A router sends won deals to an invoicing branch and lost deals to a short client survey. The pipeline filter on the module keeps a sales funnel and a service funnel apart.
A scheduled scenario reads new rows from a spreadsheet app. The Krokul search module Search Contacts looks up each person by email or phone, and Create a Deal runs only when no open deal exists. The action Save an External Key stores the row ID, so the next run updates the same deal.
Watch Deal Events with a filter on the won stage starts the scenario. Create a Document from a Deal issues the invoice in Krokul, and the next module of a delivery or mail app sends it to the client. The deal feed in Krokul gets a comment with the result.
A payment app reports a transfer. Search Documents finds the invoice by number, and Record a Payment adds the payment fact to its deal. Krokul then fires Invoice Paid, which another Krokul trigger can pick up for the next step.
| Make | Direction | Krokul | When |
|---|---|---|---|
| Instant trigger Watch Deal Events | Krokul → Make | card.created, card.statusChanged, card.won, card.lost with pipeline and stage filter | At the moment of the event |
| Instant trigger Watch Contacts and Companies | Krokul → Make | contact.created, contact.merged, clientCompany.created | When a record is created or merged |
| Instant trigger Watch Money and Documents | Krokul → Make | document.created, invoice.paid, payment.received, task.created | When the event happens |
| Action modules Create / Update a Company, Contact, Deal, Task, Ticket | Make → Krokul | The matching Krokul record | A module in the scenario |
| Action modules Change a Deal Stage, Create a Document from a Deal, Record a Payment, Log Hours | Make → Krokul | Deal stage, invoice, payment, project hours | A module in the scenario |
| Search modules Search Contacts, Companies, Deals, Documents | Krokul → Make | Existing records, with paging inside the module | Before a write module |
| Universal module Make an API Call | Make ↔ Krokul | Any public Krokul route with your connection | For routes without a dedicated module |
webhook/api-upsert.Instant triggers for all eleven Krokul events, action modules for client companies, contacts, deals, tasks, tickets, documents, payments and project hours, search modules, and the universal module Make an API Call.
Each watch module has its own webhook in Make. A webhook left without a scenario is deactivated by Make after 5 days and answers 410 Gone, and Krokul switches the subscription off after that answer.
Make queues incoming webhook data up to a limit tied to your plan credits, at most 10,000 items per webhook. Events above the limit are rejected, and the Krokul delivery log lets you send them again.
No. A Krokul API key belongs to one company, so an agency creates one Make connection per client company and reuses the same scenario blueprint.
A Make scenario runs on the operations of your Make plan, and Make caps incoming webhooks at 300 requests per 10 seconds. The HTTP and Webhooks apps of Make remain the tools for anything outside the Krokul modules.
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.
Make is a trademark of its owner. Krokul is not affiliated with Make.