Resources · Make integration

Rejstříky.info Make integrationAutomate Rejstříky.info with Make.

Can Make keep an eye on the subjects you follow in Rejstříky.info? The Rejstříky.info Make integration gives you 5 action modules and no trigger. This guide is for ops teams who want to add, check and remove tracked subjects without code, and it walks you to a tested first scenario.

Try the Rejstříky.info integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Rejstříky.info Make integration do for you?

The integration links your Rejstříky.info account to Make, a no-code tool where you build a scenario: an automation made of modules, where each module is one brick that does one job. Here all 5 modules are actions, so another app or a schedule starts the scenario and Rejstříky.info does the work.

Start tracking without copy and paste. When a new partner lands in your CRM or a form, Import sledovaného subjektu can add it to your tracked list in Rejstříky.info. The Czech name reads as “import a tracked subject”; the official documentation gives no description, so a first test with Run once is the safest way to confirm what it expects.

Pull a status or a history into your tools. Stav subjektu (subject status) and Události subjektu (subject events) are named for reading data about one subject. Each result travels as a bundle, one item passed from a module to the next, so you can drop it into a sheet or a message.

Clean up and go further. Smazat sledovaný subjekt (“delete a tracked subject”) should, judging by its name, take a subject off your list once a contract ends, and Vlastní volání API (custom API call) is the name of a module for requests the other four do not cover.

What Make does not give you here: a trigger, and full documentation. Make states it lacks enough public information about Rejstříky.info to document the modules in detail. If a step blocks, the Make troubleshooting guide helps, and the Make pricing page explains how operations are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect Rejstříky.info to Make?

  1. 01

    Add a Rejstříky.info module

    Open a scenario, click the + and search for Rejstříky.info. Pick any of its modules, then click Create a connection. A connection is your account linked to Make once, then reused by every Rejstříky.info module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, for example the team or account it belongs to. Then either approve Make on the Rejstříky.info page that opens, or paste the key Rejstříky.info gives you, depending on what the window asks.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and every other Rejstříky.info module in any scenario can pick it from the list without asking again.

First scenario

Your first scenario with Rejstříky.info

GoalWhen a new record appears in another app, Make imports it into Rejstříky.info and reads back its status.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario, then click the + to place the first module. Rejstříky.info has no trigger, so choose the app where new partners or clients appear.

  2. 02

    Add the import

    Click the + on the right of that first module, search Rejstříky.info and choose Import sledovaného subjektu. Select your connection and map the data from the first module into the fields Make shows.

  3. 03

    Read the status

    Add Stav subjektu after the import. Map the same subject from the earlier modules so Make asks Rejstříky.info for the status of the one you just added.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time; open the bubble above each module to read the bundles it received and check that the subject really arrived.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Modules

What each Rejstříky.info module does

Rejstříky.info gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Rejstříky.info1

Import sledovaného subjektu

ActionIn the docs only

Judging by its name, you get a subject added to your Rejstříky.info tracking list straight from a scenario, with no manual entry. The name translates to “import a tracked subject”, and Make publishes no description for it.

When to use it
right after a new client or supplier is created in your CRM, so tracking starts the moment the relationship does.
Watch out
the fields are not documented, so run it once on a single test subject before mapping real data.
Rejstříky.info2

Smazat sledovaný subjekt

ActionIn the docs only

This one keeps your tracked list tidy by taking a subject out of monitoring. Its Czech name means “delete a tracked subject”.

When to use it
when a deal is marked lost or a contract closes in another app, so you stop following a company that no longer matters to you.
Watch out
treat a delete as final, since nothing documents an undo. Test it on a throwaway subject first, and add a filter so only the right records reach it.
Rejstříky.info3

Stav subjektu

ActionIn the docs only

Stav subjektu, “subject status”, is the module to call when you want the current state of one subject in your scenario, ready to map into a later step.

When to use it
before an invoice or an order goes out, to check the partner first and route the record depending on the answer.
Watch out
nothing documents what the status contains, so read the bundle after Run once before building any rule on it.
Rejstříky.info4

Události subjektu

ActionIn the docs only

With Události subjektu (“subject events”) your scenario can fetch what has happened to a subject, rather than a single snapshot of where it stands today.

When to use it
when a colleague opens a client file and needs its history pasted into a note, a sheet or a team message.
Watch out
if it returns several events, each one may count as a bundle, and every module that processes it uses an operation on your plan.
Rejstříky.info5

Vlastní volání API

ActionIn the docs only

When the four named modules fall short, Vlastní volání API (“custom API call”) lets you send your own request to Rejstříky.info through the connection you already set up.

When to use it
only after checking that none of the other modules does the job, because a custom request asks more of you.
Watch out
Make gives no guide for it, so you need the Rejstříky.info API reference on hand to fill it correctly.
Need help

Need help automating Rejstříky.info with Make?

A person reads every message.

FAQ

Rejstříky.info and Make: common questions

01Is the Rejstříky.info Make integration free?
Yes, on the Make side. Rejstříky.info is a standard app, so it is available on the Free plan. That plan gives you 2 active scenarios, a shortest interval of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module per bundle. Your Rejstříky.info account itself follows its own terms, which this page does not cover.
02What do you need to connect Rejstříky.info to Make?
A Rejstříky.info account and a Make account. The Make documentation lists no other prerequisite and no steps specific to this app, so the generic flow applies: add any Rejstříky.info module, click Create a connection, optionally name it, then authorize Make on the Rejstříky.info page or paste the key the app provides, and click Save. Every Rejstříky.info module then reuses that same connection. Since the documentation is marked as limited, keep your account settings open while you connect in case the window asks for something unexpected.
03Can Rejstříky.info start a Make scenario in real time?
No. Rejstříky.info has no trigger in Make, neither scheduled nor instant, so it cannot start a scenario on its own. You have two ways around it. Start the scenario with a trigger from another app, such as a new row or a new CRM record, and place Rejstříky.info modules after it. Or leave the first module on a schedule: a new scenario runs every 15 minutes by default, and paid plans go down to 1 minute. Either way, Rejstříky.info acts as the step that does the work, not the one that fires.
04What if a Rejstříky.info module you need is missing in Make?
Start with Vlastní volání API, whose name means custom API call. By that name, it sends your own request to Rejstříky.info through the connection you already have, which covers cases the four other modules do not. You will need the Rejstříky.info API reference, since Make documents none of these modules in detail and says so openly. Rejstříky.info has no generic Make an API Call module on top of that. If you still cannot get the result you want, the team can look at your case with you.
05Should you use Make or n8n for Rejstříky.info?
It depends on what each tool offers for this app. In Make, Rejstříky.info has 5 action modules and no trigger, with documentation that Make itself calls limited. This page cannot confirm whether n8n has a dedicated node for Rejstříky.info, so check that first. Compare what each tool covers for your exact case, and how comfortable your team feels building in it, rather than picking by name. The need in front of you should settle it, not habit or reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations