--- title: "Rejstriky.info Integration" description: "Rejstriky.info is a Czech business register lookup covering the insolvency register (ISIR) and the register of enforcement proceedings. Agents check a subject for insolvency and enforcement records, pull case details and events, and manage a watch list of monitored subjects." url: https://flowrunner.ai/integrations/rejstriky-info date_modified: 2026-09-04T19:38:13-07:00 --- # Rejstriky.info [Analytics & Data](https://flowrunner.ai/integrations/category/analytics-data) Rejstriky.info is a Czech business register lookup covering the insolvency register (ISIR) and the register of enforcement proceedings. Agents check a subject for insolvency and enforcement records, pull case details and events, and manage a watch list of monitored subjects. 8 actions · Custom auth · available [Rejstriky.info website](https://rejstriky.info/) · [Platform Documentation](https://www.rejstriky.info/api) · Capability data verified 2026-08-27 1. The nightly credit exposure job runs over active Czech customers and their open balances 2. Check Insolvency Record screens the whole list and returns one boolean per subject 3. Get Insolvency Cases pulls the case reference, the court, and the current stage for every subject that came back true 4. Check Enforcement Proceedings adds any entries in the enforcement register, and Get Enforcement Detail brings back the amounts and dates 5. Agent confirms the match was made on an IC rather than on a name alone before treating the hit as this customer 6. Agent posts the case file, the stage of proceedings, and the open receivable to the credit channel 7. The credit manager decides whether the account goes on stop ## What This Integration Enables Most register connectors answer the question of who a counterparty is. Rejstriky.info answers a different and more urgent one: who is already coming after their money. It reads the Czech insolvency register (ISIR) and the register of enforcement proceedings, which is where distress becomes public before it becomes visible in your accounts receivable. An enforcement order against a customer is a credit signal in its own right, and it usually predates the missed payment that would otherwise be your first warning. The connector is deliberately built as a ladder. Check Insolvency Record returns one boolean and is cheap enough to run across an entire customer list. Get Insolvency Cases adds the case reference, the court, and the current stage. Get Insolvency Events adds every filing, hearing, ruling, and document link, which is what a due diligence trail actually requires. Screen wide, then read deep only where the screen fired. A separate watch list keeps monitored subjects synchronized from your CRM, so the same discipline applies to counterparties you acquired last week as to the ones you have billed for years. ### Without FlowRunner **Distress found in arrears**: The first sign a customer is in trouble is an invoice that stops being paid **Screening priced out of routine use**: Checking every customer every night is not something a person schedules **Hits without a file**: A register match arrives as a yes, with no case, court, or stage attached to it ### With FlowRunner **Distress found on the register**: The insolvency and enforcement registers are read on a schedule against the whole customer book **Cheap screen, targeted detail**: A boolean sweep runs across everyone, and the expensive reads run only where it came back true **Hits arrive as evidence**: Every escalation carries the case reference, the stage, the amounts, and links to the official documents ## Use Case Scenarios ### The receivables book, screened nightly The agent pulls active Czech customers with open balances from [HubSpot](https://flowrunner.ai/integrations/hubspot) or the ledger, then calls Check Insolvency Record for each. Most come back false and cost almost nothing. For the handful that come back true, the agent escalates to Get Insolvency Cases for the reference and the stage, and calls Check Enforcement Proceedings to see whether an enforcement officer is already involved. The result posts to the credit channel in [Slack](https://flowrunner.ai/integrations/slack) as a short list ordered by exposure, with the largest open balance against a live proceeding at the top. Nobody had to remember to run anything. ### Onboarding a counterparty with the file already assembled A sales team wants terms for a new Czech customer. Before credit is extended, the agent runs the full ladder: the insolvency check, then Get Insolvency Events for the complete timeline including the filings, the rulings, and the links to the documents on the official register, then Check Enforcement Proceedings and Get Enforcement Detail for any claim amounts. Identity and ownership come from a companion register through [Merk](https://flowrunner.ai/integrations/merk), and the registered address is confirmed through [RUIAN API](https://flowrunner.ai/integrations/ruian-api). The credit committee gets one file rather than four browser tabs, and the file names its own sources. ### Keeping the watch list in step with the CRM New customers arrive continuously, and monitoring only helps if it covers them. On a schedule, the agent compares the CRM against the watch list using Check Subject Is Watched, then adds the newcomers with Import Subjects. That call fails partially by design: rows that validate are imported and rows that do not are rejected, and the whole call then reports a non-zero status carrying the rejected rows. The agent treats that as partial rather than total, writes the imported subjects back to the CRM as monitored, and raises the rejected identifiers as a small, specific work item. Customers who left are removed with Delete Watched Subject, which is the only way monitoring stops being paid for on accounts nobody has any more. ## Human-in-Loop Highlight Putting a customer's account on stop is the single most damaging thing this workflow could do on its own. It halts shipments, it reaches the customer's own operations within a day, and a relationship that survives it rarely does so unchanged. Two properties of this register make an unsupervised stop a genuinely bad idea. First, the search criteria are joined with AND rather than OR, so a lookup that supplied only a surname and first name matched on a name, and Czech namesakes are ordinary. Second, Check Insolvency Record answers whether a subject appears in the register at all, which includes proceedings that concluded years ago. So the agent gathers rather than decides. It runs Get Insolvency Events for the full timeline, calls Get Enforcement Detail for the claim amounts, and then posts: "Customer Stavby Morava s.r.o., IC 27641902, matched on IC. INS 4412/2026 at the Regional Court in Brno, stage: moratorium declared 18 August. One enforcement proceeding, 1.2m CZK. Open receivable 340,000 CZK, 22 days out. Place the account on stop, shorten terms, or leave it alone?" The credit manager answers. That pause is the [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord): the agent has done every piece of work a person would have done, and stopped exactly where the judgment starts. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 8 actions ### Insolvency 3 - **Check Insolvency Record** Reports whether a company or individual appears in the Czech insolvency register at all, as a single true or false. This is the screening call, cheap enough to run across a whole customer list on a schedule. Criteria are combined with AND, so each additional identifier narrows the search rather than widening it. - **Get Insolvency Cases** Returns the insolvency case files held for a subject, each with its reference number, the court, the current stage of proceedings, and a link to the file. Use it as the second rung, once the boolean screen has told you which subjects are worth the call. - **Get Insolvency Events** Returns the case files together with every recorded event: the filings, the hearings, the rulings, and the documents, each with its date, type, and a link to the official document. This is the read that produces a due diligence trail rather than a status. ### Enforcement 2 - **Check Enforcement Proceedings** Reports whether a subject has an entry in the Czech register of enforcement proceedings and returns the identifier of each one. An enforcement order against a counterparty is a credit signal on its own, and this is what surfaces it before the missed payment does. - **Get Enforcement Detail** Returns the detail of a single enforcement proceeding: the reference number, the enforcement officer, the issuing court, the amounts claimed, and the key dates. Address it by the identifier the enforcement check returned. ### Watched Subjects 3 - **Check Subject Is Watched** Reports whether a subject is already on the Rejstriky.info watch list. Call it before an import to avoid adding a duplicate, which is the usual step when synchronizing a CRM. - **Import Subjects** Adds subjects to the watch list in bulk, which is how a customer list is brought under monitoring. Each subject needs a valid IC or RC. Rows that validate are imported and rows that do not are rejected, so treat a failure here as partial and read the rejected rows attached to it. - **Delete Watched Subject** Removes a subject from the watch list so Rejstriky.info stops monitoring it. Supplying both an IC and an RC matches only a subject carrying both, so send only the identifier you actually hold. ## Frequently Asked Questions ### What can FlowRunner do with Rejstriky.info? FlowRunner agents can run Check Insolvency Record, Get Insolvency Cases, and Get Insolvency Events in Rejstriky.info, plus 5 more actions. ### Does connecting Rejstriky.info to FlowRunner require OAuth? Rejstriky.info uses a custom authentication method to connect to FlowRunner. ### Can Rejstriky.info trigger a FlowRunner workflow automatically? Rejstriky.info doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Rejstriky.info?** This integration exposes Rejstriky.info to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/rejstriky-info. Site index: https://flowrunner.ai/llms.txt