Resources · Make integration

RUIAN API Make integrationAutomate RUIAN API with Make.

Need Czech addresses checked inside your automations? The RUIAN API Make integration gives you 7 modules, 4 searches and 3 actions, with no trigger. This page shows ops and data teams how to connect the app, build a first scenario and pick the right module.

Try the RUIAN API integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RUIAN API Make integration do for you?

The RUIAN API Make integration plugs the RUIAN API app into Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that searches or acts. Going by their names, since the documentation describes none of them, the seven modules revolve around Czech places, from regions down to streets, plus two modules to select or validate an address.

Catch bad addresses at the door. A form, a shop or a spreadsheet in another app hands over an address, and Validate Address in Czechia checks it before the record lands in your CRM. Your sales team stops calling customers back to fix a postcode.

Build your own reference lists. Chain List Regions in Czechia, then List Municipalities for Region, then List Streets for Municipality, and write the results into a sheet your team can filter. Each search can return zero, one or many items, so plan for a list, not a single answer.

Pin down one exact place. When you already know the street, List Places for Street and Select Address in Czechia narrow things to the address you actually want to store.

Know the limit before you start: the Make documentation for RUIAN API is marked as limited, with no field list and no troubleshooting notes. You learn what each module returns by testing it, which the Make troubleshooting guide walks through. New to the editor? Make training covers the basics, and if you are still choosing a tool, n8n vs Make lays out the criteria.

Connect

How do you connect RUIAN API to Make?

  1. 01

    Add a RUIAN API module

    Inside your scenario, click the + and type RUIAN API in the search box, then pick any of its modules. Click Create a connection. A connection is your RUIAN API access linked to Make once and reused by all seven modules.

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as the project or the team saves you guesswork later, when several connections sit in the same dropdown and you need to know which one a module is using.

  3. 03

    Authorize Make and save

    Depending on what RUIAN API asks for, either approve Make on the app's own page or paste the key the app gives you. Click Save. The connection now appears in the module, ready for the other RUIAN API modules too.

First scenario

Your first scenario with RUIAN API

GoalWhen another app receives a new address, Make checks it with RUIAN API and passes the result along.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle is where your first module goes.

  2. 02

    Start from the app that holds addresses

    RUIAN API has no trigger, so the first module comes from another app, such as your form tool or your sheet. Each new entry reaches Make as a bundle: one item, here one address.

  3. 03

    Add Validate Address in Czechia

    Click the + on the right of the first module, search for RUIAN API and pick Validate Address in Czechia. Connect your account, then map the address coming from the previous module.

  4. 04

    Test with Run once

    Click Run once and open the bundles each module received. With documentation this thin, that output is the best way to see what RUIAN API sends back.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on so it keeps checking new addresses.

Modules

What each RUIAN API module does

RUIAN API gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RUIAN API1

List Municipalities for Region

SearchIn the docs only

Give it a region and it returns the municipalities that belong there, one bundle per municipality, ready to feed the next step of your scenario.

When to use it
you are building a pick list for a delivery zone or a sales territory and need every town inside one region.
Watch out
this is a search, so one run can hand back many items, and every later module runs once per item.
RUIAN API2

List Places for Street

SearchIn the docs only

Starting from a street, this search brings back the places recorded on it, which gets you from a vague street name to specific points you can store.

When to use it
a customer typed only a street, and you want the candidate places before asking them to confirm the right one.
Watch out
the documentation does not describe what a place contains, so run it once and read the bundle before mapping anything.
RUIAN API3

List Regions in Czechia

SearchIn the docs only

Here is the top of the ladder: the module lists the regions of Czechia so you have a clean starting point for everything below them.

When to use it
you are setting up a reference sheet from scratch and want the region names to come from the source rather than from someone's memory.
Watch out
placed after a search that returns several items, it runs once for each, which multiplies operations, the unit Make counts on your plan.
RUIAN API4

List Streets for Municipality

SearchIn the docs only

Pick a municipality and you get back its streets, which turns a town name into a list your forms or your team can choose from.

When to use it
right after List Municipalities for Region, when a sheet or a form field needs streets for one chosen town only.
Watch out
a large town can mean a long list, so add a filter after it if the next module only needs a few streets.
RUIAN API5

Make an API Call

ActionIn the docs only

Your escape hatch: it calls any endpoint of the RUIAN API with the connection you already set up, for whatever the six named modules do not cover.

When to use it
you know the API offers a request that none of the listed modules performs and you do not want a second connection.
Watch out
Make gives no list of endpoints for this app, so you need the RUIAN API reference on hand to build the request.
RUIAN API6

Select Address in Czechia

ActionIn the docs only

As its name says, this action settles on one address in Czechia, so the rest of your scenario works with a single record instead of a list of candidates.

When to use it
after List Places for Street, when you need to keep the one address that will go into your CRM or invoice.
Watch out
the documentation gives no field details, so check with Run once which values the module expects and returns.
RUIAN API7

Validate Address in Czechia

ActionIn the docs only

This action checks an address in Czechia before you rely on it, which keeps typos and half-filled forms out of the tools downstream.

When to use it
a new order, lead or form entry arrives with an address and you want it checked before anything gets shipped or stored.
Watch out
the result format is not documented, so read the bundle after Run once and add a filter on the right value.
Need help

Need help automating RUIAN API with Make?

A person reads every message.

FAQ

RUIAN API and Make: common questions

01Is the RUIAN API Make integration free?
Yes, RUIAN API is a standard app, so you can use it from the Make Free plan. That plan has limits you will feel fast: 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Every module run on one bundle counts as one operation, and operations are what your plan counts. Paid plans lift the interval to 1 minute and allow 40 minutes of execution.
02What do you need to connect RUIAN API to Make?
You need a Make account and access to RUIAN API. The Make documentation lists no specific prerequisite for this app and no dedicated connection steps. You follow the generic flow: add a RUIAN API module, click Create a connection, name it if you like, then either approve Make on the app's page or paste the key the app gives you, and click Save. The same connection then serves all seven modules.
03Does RUIAN API trigger Make scenarios in real time?
No, RUIAN API has no trigger module at all, neither scheduled nor instant. A scenario that uses it has to start somewhere else: on a trigger from another app, such as a form or a spreadsheet that receives addresses, or on a schedule set with the clock on the first module. A new scenario runs every 15 minutes by default, the Free plan cannot go below that, and paid plans can go down to 1 minute.
04What if the RUIAN API module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the RUIAN API with the connection you already have, so you are not limited to the six named modules. Keep in mind that the Make documentation for this app is marked as limited: it gives no field list and no troubleshooting notes. Test every module with Run once and read the bundles to see what comes back before you build the rest of the scenario.
05Should you use Make or n8n for RUIAN API?
It depends on the tool your team already runs. On Make, RUIAN API offers six named modules plus Make an API Call, with no trigger, and works from the Free plan. Many apps also have an n8n node, so check whether one exists for RUIAN API before deciding. Then compare on your own criteria: who maintains the scenarios, which other apps they touch, and how your team prefers to build. Neither answer is right for everyone.
Same platform

Other docs you might need on this stack.

Browse all integrations