# Zapier + Krokul CRM

Yes. Krokul CRM has its own app in Zapier. Eleven Krokul events, such as Deal Won or Payment Received, start a Zap as instant triggers, and Zap steps create or update client companies, contacts, deals, payments and tasks in Krokul. You connect the app once with a Krokul API key.

**Status:** Via API and webhooks.

## What your team gets

### A won deal opens the next piece of work

The Krokul trigger Deal Won fires the moment a manager moves a deal to a won stage. The next step opens a project in a task tracker, posts the deal amount to a team channel or adds a row to a sheet.

### Inquiries from forms and ad platforms arrive as deals

A Zap starts with the trigger of a form or an ad platform. The Krokul search Find Contact by email or phone runs first, and the action Create Deal with the option to create the contact when the search finds nothing prevents a second card for the same person. The deal gets the source you choose, so reports show where the inquiry came from.

### Payments in another app close the invoice in Krokul

When a payment app or an accounting app reports a payment, the Krokul action Record Payment adds it to the deal, linked to the invoice found with the search Find Document. Krokul reduces the debt of the client company and fires Invoice Paid once the invoice is covered.

### One record, one ID on both sides

The action Save External Key stores the ID that the other app gave to a company, deal or document. A later Zap uses the search Find by External Key and updates the same Krokul record without creating a copy.

## What moves between Zapier and Krokul

| Zapier | Krokul | Direction | When |
|---|---|---|---|
| Instant trigger (Deal Created, Deal Stage Changed, Deal Won, Deal Lost) | Deal events `card.created`, `card.statusChanged`, `card.won`, `card.lost` | Krokul → Zapier | At the moment of the event |
| Instant trigger (Contact Created, Contacts Merged, Company Created) | Contact and client company events | Krokul → Zapier | When a record is created or merged |
| Instant trigger (Document Created, Invoice Paid, Payment Received, Task Created) | Document, payment and task events | Krokul → Zapier | When the event happens in Krokul |
| Action (Create or Update Company, Contact, Deal, Task, Ticket) | The matching Krokul record | Zapier → Krokul | A step of the Zap |
| Action (Change Deal Stage, Create Document from Deal, Record Payment, Log Hours, Add Comment) | Deal stage, invoice, payment, project hours, deal feed | Zapier → Krokul | A step of the Zap |
| Search (Find Contact, Find Company by EDRPOU, Find Deal, Find Document) | Existing Krokul records | Krokul → Zapier | Before a write step |
| Action and search on external keys | `externalRef` of a company, contact, deal, product or document | Zapier ↔ Krokul | When the other app has its own ID |

## How to connect today

### Connect the Krokul app

1. In Krokul, create an API key with the scope the Zaps need, for example deals and contacts.
2. In Zapier, add the Krokul app from its invite link and pick a trigger or an action.
3. Paste the key when Zapier asks you to connect a Krokul account. Zapier checks it at once.
4. Pick a trigger such as Deal Won, test it, and Zapier pulls a recent sample with real fields.
5. Add the steps of the other app and map the fields. When you turn the Zap on, Krokul subscribes it to the event, and when you turn it off the subscription is removed.

### Raw webhooks for edge cases

1. For a signed payload or a route the app does not list, use Catch Raw Hook with `webhook/api-upsert`, or the Krokul action API Request.

**Triggers:** Catch Hook; Catch Raw Hook; Retrieve Poll.

**Actions:** POST; GET; PUT; Custom Request.

### For integrators

Every Zap call runs through the public Krokul API, so the key scope, the role and the call log apply to Zapier the same way they apply to your own code. Each instant trigger is a Krokul webhook subscription with a signed delivery, an `x-crm-delivery` ID for dropping repeats, and an entry in the delivery log.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Which Krokul events can start a Zap?

Deal Created, Deal Stage Changed, Deal Won, Deal Lost, Contact Created, Contacts Merged, Task Created, Company Created, Document Created, Invoice Paid and Payment Received. All eleven are instant triggers.

### How does the Krokul app sign in?

With a Krokul API key. The key has a scope and a role, so a Zap can read and write only what that key allows, and an admin can revoke it in Krokul at any time.

### Can a Zap filter deal events by pipeline or stage?

Yes. The deal triggers accept a pipeline and a stage, so a Zap reacts only to the funnel it is meant for.

### Do I still need Webhooks by Zapier?

Only for raw payloads or for checking the Krokul signature in a code step. Zapier accepts webhook payloads up to 10 MB for triggers and 2 MB for Catch Raw Hook.

## Limits

Each Zap runs one way, from its trigger to its steps, so a round trip needs two Zaps. Webhooks by Zapier stays the tool for raw signed payloads, and Zapier lists its webhook steps on the Professional, Team and Enterprise plans.

## Related services

- [Make](https://krokul.com/en/integrations/make/index.md)
- [n8n](https://krokul.com/en/integrations/n8n/index.md)
- [Albato](https://krokul.com/en/integrations/albato/index.md)
- [Google Sheets](https://krokul.com/en/integrations/google-sheets/index.md)
- [Slack](https://krokul.com/en/integrations/slack/index.md)

[Automation platforms](https://krokul.com/en/integrations/category/automation/index.md)

Zapier is a trademark of Zapier, Inc. Krokul is not affiliated with Zapier.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs