# Ringostat + Krokul CRM

Yes. Krokul CRM integrates with Ringostat. Every call from Ringostat call tracking reaches Krokul with its ad source and UTM tags, so the deal knows at once which campaign brought the client. The recording and duration of the conversation land in the contact feed, and a missed call becomes a task.

**Status:** Via API and webhooks. **Automation platforms:** Albato.

## What your team gets

### The ad source moves into the deal

The Ringostat «Incoming call» event after the call carries the client number and the utm_source, utm_medium and utm_campaign tags. Krokul creates a deal, writes the tags to it and sets the source. The Krokul report by source then shows how many paid deals each campaign brought.

### A repeat call goes to the same deal

When a client with an open deal calls again, Krokul creates no duplicate. The call lands in the feed of the existing deal. Krokul keeps the Ringostat REPEATED status next to it, so the marketer sees first and repeat calls separately.

### A missed call gets an owner

The NO ANSWER or BUSY status in the after-call event creates a «Call back» task in Krokul with the client number. The task goes to the contact manager. A number with no contact goes to the person on duty.

### A callback from the deal card

The manager clicks a number on the card, and Krokul calls the Ringostat method that connects two numbers. In this request, caller carries the client number, callee carries the manager number or SIP account, and direction out makes the call outgoing in the Ringostat log. The conversation comes back to the deal through the «Outgoing call» event.

### The call category becomes a tag

The «Call category set» event arrives when someone sets a category on a Ringostat call card. Krokul adds this category to the deal as a tag, and the pipeline can be filtered by it.

## What moves between Ringostat and Krokul

| Ringostat | Krokul | Direction | When |
|---|---|---|---|
| «Incoming call» event after the call (number, status, duration, recording, UTM) | Deal with source and tags, call in the contact feed | Ringostat → Krokul | After every incoming call |
| «Outgoing call» event after the call | Call in the deal feed | Ringostat → Krokul | After an outgoing call |
| NO ANSWER or BUSY status | «Call back» task | Ringostat → Krokul | A call with no conversation |
| REPEATED status | Repeat call mark on the existing deal | Ringostat → Krokul | A client calls again |
| «Call category set» event | Tag on the deal | Ringostat → Krokul | A category is set on the call card |
| Method that connects two numbers (caller, callee, direction) | Number button on the deal card | Krokul → Ringostat | The manager clicks the number |
| Call log (calls/list) | Check of calls for a period | Ringostat → Krokul | Once a day |

## How to connect today

### Krokul app in Albato

1. Connect Ringostat in Albato, and the Krokul app with a Krokul API key.
2. Link the Ringostat trigger «Incoming call» in its after the call variant to the Krokul action «Create Deal», and pass the number and the UTM tags.
3. Link the «Outgoing call» trigger in its after the call variant to the Krokul action «Add Activity» on the contact found by phone.

### Your own flow through the Krokul API and webhooks

1. Issue a Krokul API key with scopes for deals, contacts, activities and tasks.
2. In the Ringostat account, open «Integration» → «Webhooks», click «Add event», choose «Incoming call» after the call and enter the URL of your handler with the POST method and the json format.
3. The handler finds the person by number through `contact/api-find`, creates a deal through `card/api-create` with the UTM tags and records the call through `activity/api-create`.
4. Use the «Execute and show sample» button in Ringostat to send a test event and check that the deal appeared in Krokul.

**Triggers:** Incoming call — before the call; Incoming call — after the call; Incoming call — after the answer; Outgoing call — before the call; Outgoing call — after the call.

### For integrators

Ringostat webhooks are built in the account with any set of parameters, the GET, POST or PUT method and the json, raw, Json-rpc or Form format. The call log comes from a GET request to https://api.ringostat.net/calls/list with the Auth-key header. On the Krokul side, the Ringostat call ID is stored as an `externalRef`, so a repeated delivery creates no second record, and Krokul webhooks are signed with HMAC and have a delivery log.

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

## Questions and answers

### Does Krokul see which ad made a Ringostat client call?

Yes. The UTM tags and the source from Ringostat call tracking are written to the deal, so Krokul reports by source count calls together with sales.

### Which Ringostat events does Krokul need?

The main event is «Incoming call» after the call. For the full picture, add «Outgoing call» after the call and «Call category set» if the team sets categories on calls.

### What happens to a call if Krokul is unavailable for a while?

Ringostat marks the webhook as «with error» and shows it on the error check page. Ringostat does not retry automatically, and Krokul picks up the missed calls from the calls/list log.

### Can a manager call a client from Krokul through Ringostat?

Yes. Krokul calls the Ringostat method that connects two numbers. The manager phone rings first, then the client, and the conversation comes back to the deal.

## Limits

Tracking numbers, projects, the callback widget and ad channel analytics live in Ringostat. Ringostat does not retry a webhook that the receiver did not answer with 200 OK, so Krokul accepts the event at once and processes it after the reply.

## Related services

- [Binotel](https://krokul.com/en/integrations/binotel/index.md)
- [RingCentral](https://krokul.com/en/integrations/ringcentral/index.md)
- [Aircall](https://krokul.com/en/integrations/aircall/index.md)
- [Google Ads](https://krokul.com/en/integrations/google-ads/index.md)
- [Google Analytics 4](https://krokul.com/en/integrations/google-analytics-4/index.md)

[Phone and calls](https://krokul.com/en/integrations/category/telephony/index.md)

Ringostat is a trademark of its owner. Krokul is not affiliated with Ringostat.

Updated: 2026-10-15

---

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