Yes. Krokul CRM integrates with Opendatabot. Krokul queries Opendatabot as soon as a manager enters the EDRPOU code of a company, and fills in the full name, address, director, business activity and registration state from the Unified State Register. For companies with open deals, Krokul watches the register for changes and writes them to the card feed. The setup runs on the Opendatabot API together with the Krokul API and webhooks.
A manager enters an EDRPOU code in Krokul, Krokul checks the checksum and calls GET /full-company/{code}. The registry block fills the company card with the legal name, address, director name and main business activity. The manager does not copy details from the register by hand.
The status field of the Opendatabot response shows whether the company is registered, being terminated or already terminated. Krokul shows this state on the company card and warns the manager when a contract or invoice is created for a company that is being terminated.
For companies with open deals, Krokul creates a POST /subscriptions subscription with the company type. On a schedule, Krokul reads GET /history, and each new change, such as a new director or address, appears as an entry in the company feed and a notification to the owner.
The «Update from register» button on the company card repeats the /full-company request and shows which fields have changed. The manager decides what to accept, and the previous values stay in the card history.
| Opendatabot | Direction | Krokul | When |
|---|---|---|---|
| EDRPOU code (/full-company/{code}) | Krokul → Opendatabot | Company EDRPOU field | A company is created, or «Update from register» |
| Registration data (registry: name, address, director, business activity) | Opendatabot → Krokul | Company card fields | In the reply to the request |
| Registration state (status) | Opendatabot → Krokul | Mark and warning on the company card | In the reply to the request |
| Monitoring subscription (POST /subscriptions) | Krokul → Opendatabot | Company with an open deal | When the company gets a deal |
| Change history (/history) | Opendatabot → Krokul | Entry in the company feed, notification | Polling on a schedule |
clientCompany.created event and check the x-crm-signature header of every delivery against your secret.clientCompany/api-update.activity/api-create with the comment type.Yes, through Opendatabot. Krokul checks the code checksum, then takes the data from the Unified State Register and fills in the company card.
Among other things, the /full-company method returns the full and short name, address, director, main business activity, registration state and founders. Krokul records the details and the state, and the rest is visible in Opendatabot.
Yes, for companies under monitoring. Krokul reads the Opendatabot change history regularly and writes every change to the company feed.
An Opendatabot API key. You agree the API access terms with Opendatabot itself.
Access to the Opendatabot API is arranged with Opendatabot itself, which also gives test access. Opendatabot sends no webhooks, so Krokul fetches monitoring changes by polling the history on a schedule.
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.
Opendatabot is a trademark of its owner. Krokul is not affiliated with Opendatabot.