Resources · Make integration

iDoklad Make integrationAutomate iDoklad with Make.

Can Make handle your iDoklad invoicing while you do something else? The iDoklad Make integration gives you 79 modules: 9 scheduled triggers, 56 actions and 14 searches for invoices, contacts, price lists and payments. Below, you connect your account and build a first scenario.

Try the iDoklad integration on MakeSee the 79 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the iDoklad Make integration automate?

The iDoklad Make integration links your iDoklad account to Make, a visual tool that chains apps without code. You build a scenario, the automation itself, out of modules: each module is one brick, such as a trigger, an action or a search. Make then runs it for you, picking up invoices and payments, creating documents and emailing invoices.

Invoices that go out on their own. Pair Watch invoices with Send an invoice by email and each invoice Make picks up lands in the customer's inbox. Add Get an invoice PDF when the file also has to be archived in a shared drive.

One clean record per customer. When a deal closes in your CRM, Search contacts checks whether the client already exists in iDoklad. Create a contact or Update a contact then does the rest, so nobody retypes an address.

Payments closed without a spreadsheet. Once your payment tool confirms the money, Mark an invoice as paid or Create a payment updates iDoklad. In the other direction, Watch payments tells your sales team what came in.

What Make does not do here: none of the 9 triggers is instant, so Make checks iDoklad on the scenario's schedule instead of hearing about changes the moment they happen. The doc also sorts modules into two groups, iDoklad modules and Migrate to the new iDoklad modules, and the directory still shows the Czech-named originals, so check which one sits in your scenario. iDoklad may also have an n8n node; the n8n vs Make comparison helps you pick, and the Make review covers the tool itself.

Connect

How do you connect iDoklad to Make?

  1. 01

    Generate your credentials in iDoklad

    In iDoklad, open Settings, click Aplikace, then the API tab, and press Generate. Copy the Client ID and the Client secret shown on screen: Make asks for both.

  2. 02

    Add an iDoklad module in Make

    Add any iDoklad module to your scenario and click Create a connection. A connection is your iDoklad account linked to Make once, then reused by every iDoklad module. The Connection name field is optional and helps you spot it later.

  3. 03

    Paste the credentials and save

    Paste the Client ID and Client secret you copied, or follow the instructions Make displays. If iDoklad asks for a callback URI while generating the credentials, enter https://www.integromat.com/oauth/cb/idoklad.

First scenario

Build your first iDoklad scenario

GoalWhen Watch invoices picks up an invoice in iDoklad, Make emails it to the customer with Send an invoice by email.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. Type iDoklad in the search box to see its modules.

  2. 02

    Add Watch invoices

    Pick Watch invoices, click Create a connection and paste your Client ID and Client secret. Once connected, Make can read your iDoklad data and fill the lists in the module.

  3. 03

    Add the email step

    Click the + on the right of the trigger and choose Send an invoice by email. Map the invoice returned by Watch invoices into it, so Make knows which document to send.

  4. 04

    Test with Run once

    Click Run once, then open each module's bubble to read the bundles it received; a bundle is one invoice passing from module to module. Test on a dummy customer, since this step sends a real email.

  5. 05

    Schedule it and switch it on

    Click the clock on Watch invoices to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

What starts an iDoklad scenario

9 modules start a scenario when something happens in iDoklad. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by iDoklad as soon as it happens.

iDoklad1Watch invoices

Watch invoices

triggerIn the docs only

Watch invoices hands your scenario the invoices it finds in iDoklad, one bundle per invoice, so every later step works on current billing data without an export. The doc lists it without a description, so a first Run once shows you exactly which invoices it returns.

How it fires
scheduled. Make checks iDoklad on the scenario's schedule, every 15 minutes by default and never more often on the Free plan.
When to use it
any flow that starts from billing, like emailing the invoice or copying it to a finance sheet.
Watch out
do not stack it with its Sledovat faktury twins in one scenario, or each invoice gets processed twice.
iDoklad2Watch price list items

Watch price list items

triggerIn the docs only

Your catalog in iDoklad becomes a starting point: Watch price list items passes each price list entry it finds to the next module, so a shop or a quote template can follow what the accounting side maintains. No official description exists, so read the bundles after a Run once.

How it fires
scheduled. Make queries iDoklad at the interval set on the scenario's clock, 15 minutes by default.
When to use it
keeping an online store or a sales price sheet aligned with the products listed in iDoklad.
Watch out
a busy catalog produces many bundles, and each module that processes one uses an operation.
iDoklad3Watch payments

Watch payments

triggerIn the docs only

Know when money is recorded without opening iDoklad: Watch payments sends the payments it picks up to the rest of your scenario, one bundle each. Since the doc gives no description, a Run once on your account tells you what one payment bundle contains.

How it fires
scheduled. Make polls iDoklad on the scenario's schedule; on paid plans the interval can drop to 1 minute, on Free it stays at 15 minutes minimum.
When to use it
telling an account manager in chat, or moving a CRM deal forward, once a payment is booked.
Watch out
there is a delay of up to one interval between the payment and your alert.
iDoklad4Watch invoices (formerly Sledovat faktury)

Watch invoices (formerly Sledovat faktury)

triggerIn the docs only

This is the invoice watcher as it appears in the doc's Migrate to the new iDoklad modules group, still showing its old Czech name in brackets. It feeds invoices from iDoklad into your scenario so later modules can react to them.

How it fires
scheduled. Make checks the app on the scenario's schedule, with the clock badge on the module.
When to use it
you open an older scenario, find this label on the first module and want to understand what starts the flow before touching it.
Watch out
when you rebuild, keep a single invoice watcher per flow; two of them on the same account duplicate every run and every operation.
iDoklad5Watch price list items (formerly Sledovat položky ceníku)

Watch price list items (formerly Sledovat položky ceníku)

triggerIn the docs only

Listed under Migrate to the new iDoklad modules, this watcher follows your iDoklad price list and carries the former name Sledovat položky ceníku. Each item it returns becomes a bundle that a spreadsheet, a shop or a quote tool can pick up.

How it fires
scheduled. Make asks iDoklad for price list items each time the scenario's clock comes around.
When to use it
auditing a scenario built with the Czech module and deciding what the price list trigger should become.
Watch out
the doc gives no description for it, so compare its Run once output with the Czech original before swapping one for the other.
iDoklad6Watch payments (formerly Sledovat úhrady)

Watch payments (formerly Sledovat úhrady)

triggerIn the docs only

Payments recorded in iDoklad flow from this module into the rest of the scenario. The doc files it in the migration group with its earlier name, Sledovat úhrady, which is the label longtime users of the Czech modules will recognize.

How it fires
scheduled. Make looks for payments on the scenario's schedule, so nothing arrives between two checks.
When to use it
moving a payment alert that used Sledovat úhrady onto the module listed for migration.
Watch out
switch the old scenario off before activating the new one; otherwise both watchers pick up the same payment and your team hears about it twice.
iDoklad7Sledovat faktury

Sledovat faktury

Scheduled trigger

In Make“Spustí se, když je vložen nový doklad (faktura přijatá, vydaná nebo zálohová).”

Sledovat faktury is the original Czech-labeled trigger: it starts when a new document is added in iDoklad, whether an issued invoice, a received invoice or a proforma. That breadth makes it the one to read closely if supplier bills matter to your flow.

How it fires
scheduled. Make checks iDoklad at the scenario's interval rather than being called by the app.
When to use it
routing received supplier invoices to an approval channel while issued ones go to the customer.
Watch out
because three document types come through, map the type into your next module and check it during Run once before you send anything.
iDoklad8Sledovat položky ceníku

Sledovat položky ceníku

Scheduled trigger

In Make“Spustí se, pokud je vložena nová položka ceníku do seznamu.”

Add a product in iDoklad and Sledovat položky ceníku notices it: the directory describes it as starting when a new item joins the price list. It is the Czech-labeled original among the price list triggers.

How it fires
scheduled. Make polls iDoklad on the scenario's clock, every 15 minutes unless you change it.
When to use it
announcing a new service to the sales team, or creating the matching product in your online shop once the next check picks it up.
Watch out
the migration group lists Watch price list items (formerly Sledovat položky ceníku) as its counterpart, so keep only one of the two in a scenario.
iDoklad9Sledovat úhrady

Sledovat úhrady

Scheduled trigger

In Make“Spustí se, pokud je do systému vložena nová úhrada.”

Sledovat úhrady starts your scenario when a new payment is entered in iDoklad, according to its directory description. It is the Czech-labeled original of the payment watchers and still appears in the module list.

How it fires
scheduled. Make checks for new payments each time the scenario runs, with the clock badge on the first module.
When to use it
sending a thank-you email, or unlocking a customer's access in another tool, once a payment is booked in iDoklad.
Watch out
a scenario that both watches payments and creates them in iDoklad keeps reacting to its own entries, so split those jobs.
Modules

What the iDoklad modules do

iDoklad gives you 70 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

iDoklad modules

24 modules
iDoklad1

Send an invoice by email

ActionIn the docs only

Send an invoice by email delivers an iDoklad invoice to your customer, so billing no longer waits for someone to click send in the app.

When to use it
right after Create an invoice, or when Watch invoices returns a document that has to go out.
Watch out
it emails a real person, so run your tests on a dummy contact first.
iDoklad2

Get an invoice

ActionIn the docs only

One invoice, fully loaded: Get an invoice fetches the details of a single iDoklad invoice when you already know which one you want to read.

When to use it
a payment reference shows up in your bank tool and you need the amount and the customer before replying.
Watch out
it needs a precise invoice; with only a customer name, begin with Search invoices.
iDoklad3

Search invoices

SearchIn the docs only

Need every invoice that matches a condition? Search invoices returns zero, one or many invoices, each as its own bundle, so the following modules handle them one at a time.

When to use it
gathering a client's invoices into a sheet before an account review.
Watch out
every bundle it returns runs the next modules once, and each run is an operation on your plan.
iDoklad4

Get a contact

ActionIn the docs only

Get a contact pulls up one customer record from iDoklad, so a later step can reuse the details your accountant already entered instead of asking the client again.

When to use it
preparing a personalized email or a CRM note about a client you can identify precisely.
Watch out
it reads a known contact only; find it with Search contacts when you start from a name or an email.
iDoklad5

Get a price list item

ActionIn the docs only

Read one product or service from your iDoklad price list with Get a price list item, and your scenario works with the entry the accounting team maintains rather than a copy.

When to use it
an order form in another app names a product and you want its iDoklad version before invoicing.
Watch out
it targets a single known item; to browse the catalog, Search price list items fits better.
iDoklad6

Search contacts

SearchIn the docs only

Search contacts tells you whether a customer already exists in iDoklad before you create anything, returning each match as a separate bundle.

When to use it
a new lead arrives from a web form and you want to check for it, then create or update accordingly.
Watch out
zero results is a valid answer, so decide what the scenario does in that case before you add Create a contact.
iDoklad7

Search price list items

SearchIn the docs only

A whole slice of your catalog in one step: Search price list items brings back the iDoklad entries that match your search, one bundle per item.

When to use it
copying the price list into a spreadsheet the sales team reads, or refreshing product pages in an online shop.
Watch out
a large catalog means many bundles, and every later module spends one operation per bundle.
iDoklad8

Get a payment

ActionIn the docs only

Get a payment opens the record of one payment in iDoklad, so you can confirm what was booked before telling a customer anything about it.

When to use it
a support ticket quotes a payment and the agent needs the facts pulled into the reply draft.
Watch out
it works on one payment you can already identify; for a list of them, reach for Search payments.
iDoklad9

Search payments

SearchIn the docs only

Search payments lists the iDoklad payments that match what you ask for, which gives you a reconciliation base without exporting anything by hand.

When to use it
comparing what your bank statement shows with what iDoklad has actually recorded.
Watch out
the search can return nothing, one or dozens of bundles, and each of them triggers the following modules once.
iDoklad10

Delete an invoice

ActionIn the docs only

Delete an invoice removes an invoice from iDoklad for good, which helps when a test scenario has filled your account with documents nobody needs.

When to use it
cleaning up invoices generated for a sandbox customer while you tuned a flow.
Watch out
a delete cannot be undone, so never feed it straight from a search without checking the bundles in Run once.
iDoklad11

Delete a contact

ActionIn the docs only

Delete a contact wipes a customer record from iDoklad, the step to add when a removal decided elsewhere must also reach your invoicing tool.

When to use it
an erasure request handled in your helpdesk has to be applied in iDoklad as well.
Watch out
there is no way back after the run, so test on a contact created only for that purpose.
iDoklad12

Delete a price list item

ActionIn the docs only

Retire a product from your iDoklad price list with Delete a price list item, so nobody picks a discontinued service when drafting the next invoice.

When to use it
a product is archived in your shop or your catalog sheet and iDoklad should follow.
Watch out
the item is gone once the module runs, so write it to a sheet in an earlier step if you may need it again.
iDoklad13

Delete a payment

ActionIn the docs only

A payment booked by mistake disappears with Delete a payment, which keeps your iDoklad records in line with what really reached the bank.

When to use it
a scenario recorded the same payment twice and you need to remove the duplicate.
Watch out
nothing brings the payment back, so log what you delete in a sheet or a chat message first.
iDoklad14

Mark an invoice as paid

ActionIn the docs only

Mark an invoice as paid closes an invoice in iDoklad in a single step, without anyone typing the payment in by hand.

When to use it
your payment platform confirms a transfer and the matching invoice should switch to paid.
Watch out
the Czech module it replaces, Označit fakturu jako uhrazenou, describes a full payment, so keep it for invoices settled in full.
iDoklad15

Update an invoice

ActionIn the docs only

Update an invoice changes an existing iDoklad invoice, so a correction made upstream reaches the document without rebuilding it from scratch.

When to use it
a deal is amended in your CRM before the invoice has gone out.
Watch out
the migration group holds two modules with this name, and one of them formerly updated only the billing address, so check which one your scenario uses.
iDoklad16

Update a contact

ActionIn the docs only

Update a contact rewrites a customer record in iDoklad, so the next invoice carries the details your CRM holds today.

When to use it
a client moves offices or changes company name and the sales team updates the CRM first.
Watch out
it needs to know which contact to change, so put Search contacts in front of it when you start from an email address.
iDoklad17

Update a price list item

ActionIn the docs only

Push a price or label change into iDoklad with Update a price list item, so invoices drafted afterward use the same data as your shop.

When to use it
the product team edits a service in its catalog sheet and accounting should not have to repeat the change.
Watch out
the scenario needs the exact item; fetch it with Search price list items when your source only knows its name.
iDoklad18

Create a price list item

ActionIn the docs only

Create a price list item adds a new product or service to iDoklad, ready to be picked on the next invoice without a manual entry.

When to use it
a product goes live in your online store and should exist in accounting at the same time.
Watch out
run Search price list items first, otherwise a second run of the scenario can create the same item twice.
iDoklad19

Create a payment

ActionIn the docs only

Create a payment records a payment in iDoklad, keeping the books accurate when money arrives through a channel iDoklad does not see.

When to use it
a card payment is confirmed in your checkout tool and the invoice should reflect it.
Watch out
its older Czech version, Vložit úhradu, expects the id of the invoice being paid, so keep that id available from an earlier module.
iDoklad20

Make an API call

ActionIn the docs only

When no listed module does the job, Make an API call reaches any endpoint of the iDoklad API from your scenario, reusing the same connection.

When to use it
you need an iDoklad feature that none of the 79 modules exposes.
Watch out
you write the request yourself, so keep the iDoklad API documentation open and test each call with Run once.
iDoklad21

Create an invoice

ActionIn the docs only

Turn an order into a real invoice: Create an invoice builds the document in iDoklad from the data your scenario collected upstream.

When to use it
a deal is marked won in the CRM, or a shop order is paid, and billing should start without anyone typing.
Watch out
make sure the customer exists first, with Search contacts then Create a contact, so the invoice lands on the right record.
iDoklad22

Create a contact

ActionIn the docs only

Create a contact adds a new customer to iDoklad, so invoices can be issued to them without an accountant keying in their details.

When to use it
a signed quote in your sales tool announces a brand new client.
Watch out
put Search contacts right before it; without that check, a returning client ends up with two records in iDoklad.
iDoklad23

Account a proforma invoice

ActionIn the docs only

Account a proforma invoice settles an advance invoice in iDoklad, the accounting step that follows once the deposit has been paid.

When to use it
a customer paid a deposit on a proforma and the final billing should follow automatically.
Watch out
the Czech original, Vyúčtovat zálohovou fakturu, requires the invoice to be paid, so chain it after Mark an invoice as paid.
iDoklad24

Get an invoice PDF

ActionIn the docs only

Get an invoice PDF hands you the printable file of an iDoklad invoice, ready to be stored, attached or shared by a later module.

When to use it
every invoice should also be archived in a shared drive folder the accountant can browse.
Watch out
on the Free plan Make handles files up to 5 MB, which matters if your invoices embed heavy images.

Migrate to the new iDoklad modules

19 modules
iDoklad25

Send an invoice by email (formerly Doručit fakturu e-mailem)

ActionIn the docs only

This entry of the migration group emails an iDoklad invoice to the customer and keeps its former Czech name, Doručit fakturu e-mailem, in brackets for users of the old module.

When to use it
rebuilding an older billing scenario whose sending step used the Czech module.
Watch out
the original sent issued or proforma invoices to the purchaser; confirm in Run once that yours behaves the same.
iDoklad26

Search invoices (formerly Načíst faktury)

SearchIn the docs only

Here is the invoice search from the Migrate to the new iDoklad modules group, formerly called Načíst faktury, which returned lists of issued, received or proforma invoices.

When to use it
an old reporting scenario relied on Načíst faktury and you are moving it to the module the doc lists for migration.
Watch out
compare the bundles of the old and new modules on the same account before deleting the old step.
iDoklad27

Search contacts (formerly Načíst seznam kontaktů)

SearchIn the docs only

Contacts come back in bulk from this search, the migration-group module that used to be called Načíst seznam kontaktů and returned the contacts stored in iDoklad.

When to use it
a CRM sync built on the Czech module needs to be rebuilt on the current one.
Watch out
the migration group also holds Search contacts (formerly Vyhledat kontakty), so pick the one that matches the step you are replacing.
iDoklad28

Search price list items (formerly Načíst seznam položek ceníku)

SearchIn the docs only

Pulling the iDoklad catalog into another tool goes through this search, once named Načíst seznam položek ceníku and now listed with the modules to migrate to.

When to use it
a price sheet or a shop sync still runs on the Czech module and you want the listed replacement.
Watch out
each item returned is a bundle, so a full catalog multiplies the operations of every step placed after it.
iDoklad29

Search payments (formerly Načíst úhrady)

SearchIn the docs only

Payment lists for reconciliation come from this module, formerly Načíst úhrady, whose Czech original let you leave every filter empty.

When to use it
migrating a bank matching scenario that was built around the older payment search.
Watch out
with no filter set, the original could return every payment, so narrow the search in your new step before running it on a full account.
iDoklad30

Mark an invoice as paid (formerly Označit fakturu jako uhrazenou)

ActionIn the docs only

Closing invoices in full is the job of this migration-group module, known before as Označit fakturu jako uhrazenou, which covered issued, received and proforma invoices.

When to use it
a payment confirmation flow built on the Czech module needs rebuilding.
Watch out
pair it with Mark an invoice as unpaid (formerly Provést oduhrazení faktury) in your tests, so you can reverse a wrong run.
iDoklad31

Mark an invoice as unpaid (formerly Provést oduhrazení faktury)

ActionIn the docs only

Mark an invoice as unpaid reverses a full payment on an iDoklad invoice, the undo button for a settlement recorded too early. It was known as Provést oduhrazení faktury.

When to use it
a card payment is refunded or charged back, and the invoice has to be reopened.
Watch out
the older Czech module FullyUnpayInvoice, shown as Provést oduhrazení faktury, still sits in the list, so rebuild on one of the two only.
iDoklad32

Update an invoice (formerly Upravit fakturu)

ActionIn the docs only

Editing an existing invoice goes through this module, formerly Upravit fakturu, whose Czech version modified issued, received or proforma invoices alike.

When to use it
replacing an Upravit fakturu step in an older scenario that corrects invoices after a CRM change.
Watch out
do not confuse it with Update an invoice (formerly Zaktualizovat fakturační adresu), which descends from the billing address module.
iDoklad33

Update a contact (formerly Upravit kontakt)

ActionIn the docs only

Customer records get corrected with this migration-group module, which carries the former name Upravit kontakt for anyone who built scenarios on the Czech version.

When to use it
moving an address sync from your CRM onto the module the doc lists for migration.
Watch out
the old step and the new one should never run side by side on the same contact, or the last run wins silently.
iDoklad34

Update a price list item (formerly Upravit položku ceníku)

ActionIn the docs only

Catalog corrections reach iDoklad through this module, which the doc lists for migration under the former name Upravit položku ceníku.

When to use it
a price update flow from your shop still uses the Czech step and you are cleaning up the scenario.
Watch out
rebuild the mapping field by field in the new module and check one item with Run once before switching the scenario back on.
iDoklad35

Create a price list item (formerly Vložit položku ceníku do seznamu)

ActionIn the docs only

New catalog entries enter iDoklad through this module, previously named Vložit položku ceníku do seznamu, which inserted a new item into the price list.

When to use it
migrating a product launch flow that created iDoklad items with the Czech module.
Watch out
if both versions stay active in different scenarios, the same product can be created twice, so switch the old scenario off first.
iDoklad36

Create a payment (formerly Vložit úhradu)

ActionIn the docs only

Payment entries are written by this migration-group module, once called Vložit úhradu; the Czech original expected the id of the document being paid.

When to use it
rebuilding a scenario that books payments from a payment platform into iDoklad.
Watch out
map that invoice id from an earlier module, typically a search, rather than typing it, or every payment lands on the same invoice.
iDoklad37

Search contacts (formerly Vyhledat kontakty)

SearchIn the docs only

Filtered contact lookups come from this search, formerly Vyhledat kontakty, whose Czech version found contacts based on the filters you set.

When to use it
a duplicate check before Create a contact ran on the Czech module and needs the migration counterpart.
Watch out
the doc lists it next to Search contacts (formerly Načíst seznam kontaktů); the former filters, the latter returned the whole list.
iDoklad38

Make an API call (formerly Vykonat API požadavek)

ActionIn the docs only

This is the migration-group version of the free-form request module, called Vykonat API požadavek before, which could send any authorized request to iDoklad.

When to use it
an older scenario covers a missing feature with the Czech API module and you are moving it over.
Watch out
rebuild the old request carefully in the new module, then compare both outputs with Run once before deleting anything.
iDoklad39

Create an invoice (formerly Vytvořit fakturu)

ActionIn the docs only

Invoices, received invoices and proformas were all created by the Czech module Vytvořit fakturu, and this is its entry in the Migrate to the new iDoklad modules group.

When to use it
an order-to-invoice scenario built on the Czech step needs to move to the listed replacement.
Watch out
since it creates documents, run the migrated version once on a test customer before switching it on.
iDoklad40

Create a contact (formerly Vytvořit kontakt)

ActionIn the docs only

New customers are added to iDoklad by this module, which the doc files under Migrate to the new iDoklad modules and which was once called Vytvořit kontakt.

When to use it
a lead intake scenario still creates contacts with the Czech step.
Watch out
keep a search before it in the migrated scenario too, since dropping that check during a rebuild is the easiest way to create duplicates.
iDoklad41

Account a proforma invoice (formerly Vyúčtovat zálohovou fakturu)

ActionIn the docs only

This module settles a proforma invoice in iDoklad, so the advance your customer paid turns into proper accounting without anyone opening the app. It is the new name of the Czech module Vyúčtovat zálohovou fakturu.

When to use it
right after a payment lands on a proforma and your scenario has confirmed it.
Watch out
the description of the former module states the invoice has to be paid first, so check that before this step.
iDoklad42

Update an invoice (formerly Zaktualizovat fakturační adresu)

ActionIn the docs only

Here you get a corrected billing address on an issued invoice while the rest of the document stays as it was. Make shows it as the successor of the Czech module Zaktualizovat fakturační adresu.

When to use it
a customer moves offices and the change reaches your CRM before the invoice goes out.
Watch out
another module in the same group carries the name Update an invoice, so read the full title before you pick one.
iDoklad43

Get an invoice PDF (formerly Získat PDF)

ActionIn the docs only

The printable PDF of a chosen iDoklad document comes out of this module as a file your next module can store, attach or forward. It replaces the Czech-named Získat PDF.

When to use it
you archive every issued invoice in a shared drive or attach it to a message from another app.
Watch out
on the Free plan Make handles files up to 5 MB, so large documents may need a paid plan.

Other modules

27 modules
iDoklad44

Doručit fakturu e-mailem

Action

In Make“Odešle vydanou nebo zálohovou fakturu odběrateli.”

With this older Czech-named module, an issued or proforma invoice leaves iDoklad and reaches your customer by email. Its newer equivalent is Send an invoice by email.

When to use it
an existing scenario already relies on it and you want the invoice delivered right after it is created.
Watch out
for a new build, prefer the English-named module that Make lists in the migration group.
iDoklad45

Načíst fakturu

Action

In Make“Načte údaje o dokladu (faktuře vydané, přijaté, nebo zálohové).”

You get every detail of one document, whether it is an issued, received or proforma invoice, ready to map into the following modules. This is the Czech-named version kept for older scenarios.

When to use it
a trigger hands you an invoice ID and you need its amounts or customer before acting.
Watch out
it reads a single document; to go through many, a search module such as Načíst faktury fits better.
iDoklad46

Načíst kontakt

Action

In Make“Vrátí detailní informace o kontaktu.”

This module returns the full record of one iDoklad contact, so later steps can reuse the name, address or email of a customer. It is the Czech-named counterpart of Get a contact.

When to use it
an invoice arrives as a bundle, meaning one item passed along the scenario, and you need its customer details.
Watch out
you must already know which contact you want; without an ID, start with a contact search.
iDoklad47

Načíst položku ceníku

Action

In Make“Načte položku ceníku dle ID.”

Pass an ID and this module brings back one item of your iDoklad price list, with its data ready to map. It belongs to the Czech-named set that predates Get a price list item.

When to use it
an order from your shop points to a product and you want the reference stored in iDoklad.
Watch out
the lookup works by ID only, so keep that ID somewhere upstream in the scenario.
iDoklad48

Načíst úhradu

Action

In Make“Vrátí údaje o úhradě. Vhodné pro zobrazení detailu úhrady.”

Details of a single payment recorded in iDoklad come back from this module, handy when a step needs to show or check what was paid. It is the older Czech-named sibling of Get a payment.

When to use it
Sledovat úhrady flags a new payment and you want its full record before notifying your team.
Watch out
it returns one payment; for a list, use Načíst úhrady instead.
iDoklad49

Odstranit fakturu

Action

In Make“Odstraní doklad (fakturu vydanou, přijatou, nebo zálohovou).”

This module removes a document from iDoklad, whether it is an issued, received or proforma invoice, without a trip into the app. It is the Czech-named ancestor of Delete an invoice.

When to use it
a test invoice or a duplicate created by another scenario has to disappear.
Watch out
a deletion cannot be undone from Make, so run it once on a test document and add a filter before it.
iDoklad50

Odstranit kontakt

Action

In Make“Odstraní kontakt.”

Your iDoklad address book loses one contact each time this module runs, which keeps it aligned with the source you trust. Older scenarios use this Czech-named module; newer ones use Delete a contact.

When to use it
a customer is removed from your CRM and should vanish from invoicing too.
Watch out
nothing brings the contact back, so confirm the right ID with a search first.
iDoklad51

Odstranit položku ze seznamu ceníku

Action

In Make“Odstranit položku ze seznamu ceníku.”

A product or service you no longer sell drops out of the iDoklad price list through this module. It is the Czech-named version that Delete a price list item now covers.

When to use it
an item is archived in your catalog or shop and your invoices must stop offering it.
Watch out
the removal is final, so feed it one confirmed ID rather than a broad search result.
iDoklad52

Odstranit úhradu

Action

In Make“Odstraní úhradu ze seznamu úhrad.”

Use it to take one payment out of the iDoklad payment list, for example after an entry was recorded twice. Its successor in the new set is Delete a payment.

When to use it
a bank refund or a cancelled transfer means a recorded payment should no longer count.
Watch out
the invoice it settled is likely to change status too, so check that invoice afterwards with Načíst fakturu.
iDoklad53

Označit fakturu jako uhrazenou

Action

In Make“Provede plné uhrazení faktury (vystavené, přijaté nebo zálohové).”

The invoice switches to fully paid in iDoklad, issued, received or proforma alike, and your records match the bank without manual clicks. This older Czech-named module now has Mark an invoice as paid as its successor.

When to use it
a payment confirmation reaches Make from your bank or payment tool.
Watch out
it settles the whole amount, so keep it for invoices paid in full; to book a payment line instead, Vložit úhradu is the module.
iDoklad54

Provést oduhrazení faktury

Action

In Make“Provede plné oduhrazení faktury (vystavené, přijaté nebo zálohové).”

This one reverses a full payment, so an invoice marked as paid goes back to unpaid in iDoklad. It covers issued, received and proforma invoices and has Mark an invoice as unpaid as its newer form.

When to use it
a transfer bounces or a card payment is disputed after the invoice was settled.
Watch out
pair it with a filter on the event that caused it, or a correct invoice could be reopened.
iDoklad55

Upravit fakturu

Action

In Make“Upraví doklad (fakturu vydanou, přijatou, nebo zálohovou).”

Edits land directly on an existing document, issued, received or proforma, so a change in another tool shows up on the invoice. This is the Czech-named module that Update an invoice replaces.

When to use it
a deal changes in your CRM after the invoice was drafted.
Watch out
only the address? Zaktualizovat fakturační adresu touches that field and leaves the rest alone.
iDoklad56

Upravit kontakt

Action

In Make“Upraví vybraný kontakt.”

A chosen contact gets updated in iDoklad, which keeps billing details in step with the tool where your team edits them. Newer scenarios use Update a contact for the same job.

When to use it
a customer changes company details in your CRM or signup form.
Watch out
map only the fields that changed, or an empty value from the previous module may overwrite good data.
iDoklad57

Upravit položku ceníku

Action

In Make“Upraví položku ceníku.”

Your price list stays current because this module rewrites one item in iDoklad whenever the source changes. It is the Czech-named version of Update a price list item.

When to use it
a product sheet in your spreadsheet or shop gets a new price or label.
Watch out
the item has to exist already; for a brand new product, Vložit položku ceníku do seznamu is the right module.
iDoklad58

Vložit položku ceníku do seznamu.

Action

In Make“Vloží novou položku ceníku do seznamu.”

A new product or service enters the iDoklad price list, ready to be picked on your next invoices. The newer Create a price list item does the same under an English name.

When to use it
a product is published in your shop and invoicing should offer it straight away.
Watch out
run a search on the price list first, otherwise a rerun of the scenario can create the same item twice.
iDoklad59

Vložit úhradu

Action

In Make“Vloží novou úhradu do seznamu úhrad. Úhrada by měla obsahovat id dokladu který hradí.”

This module records a new payment in iDoklad's payment list, linked to the document it pays. Create a payment is its successor in the migration group.

When to use it
your payment tool reports a transfer and iDoklad should hold the matching payment entry.
Watch out
its description says the payment should carry the ID of the document it settles, so map that ID from an earlier module.
iDoklad60

Vykonat API požadavek

Action

In Make“Vykonná libovolný autorizovaný API požadavek.”

Any authorized request to the iDoklad API can go through this module, reusing the connection you already created. It is the Czech-named ancestor of Make an API call.

When to use it
you need an iDoklad feature that none of the listed modules offers.
Watch out
you describe the request yourself, so keep the iDoklad API documentation open and test with Run once before activating.
iDoklad61

Vytvořit fakturu

Action

In Make“Vloží nový doklad (fakturu vydanou, přijatou, nebo zálohovou) do seznamu.”

A new document appears in iDoklad, issued, received or proforma, built from data another app sent into the scenario. Newer builds use Create an invoice for this.

When to use it
a signed quote or a paid order should become an invoice without anyone retyping it.
Watch out
the customer usually has to exist, so place Vyhledat kontakty and Vytvořit kontakt before this step when needed.
iDoklad62

Vytvořit kontakt

Action

In Make“Vytvoří nový kontakt.”

Each run adds a fresh contact to your iDoklad address book, so a new customer is ready to invoice. The new set lists Create a contact as its replacement.

When to use it
someone fills your order form or becomes a customer in your CRM.
Watch out
look the person up with Vyhledat kontakty first and let a router or filter skip creation when a match exists.
iDoklad63

Vyúčtovat zálohovou fakturu

Action

In Make“Provede vyúčtování zálohové faktury. Faktura musí být uhrazena.”

The accounting of a proforma invoice happens in one step, turning the advance into a settled document. This is the original Czech module behind Account a proforma invoice.

When to use it
a customer paid the advance and the order is ready to close in your books.
Watch out
iDoklad requires the invoice to be paid, so place Označit fakturu jako uhrazenou or a payment step before it.
iDoklad64

Zaktualizovat fakturační adresu

Action

In Make“Zaktualizuje fakturační adresu odběratele na vydané faktuře beze změny ostatních parametrů faktury.”

Only the customer's billing address on an issued invoice changes; amounts, items and dates stay untouched. It is the Czech-named module that the second Update an invoice replaces.

When to use it
your support team fixes a wrong address after the invoice was issued.
Watch out
it works on issued invoices, so a proforma needs Upravit fakturu instead.
iDoklad65

Získat PDF

Action

In Make“Získá PDF tiskovou sestavu zadaného dokladu.”

A printable PDF of any chosen document comes back as a file, ready to drop into storage or attach to an email from another app. The migration group lists Get an invoice PDF as its successor.

When to use it
your accountant wants every issued invoice filed in a shared folder.
Watch out
the Free plan caps files at 5 MB and data transfer at 512 MB, which counts every PDF you move.
iDoklad66

Načíst faktury

Search

In Make“Načte seznam dokladů (faktur přijatých, vydaných nebo zálohových).”

Received, issued and proforma invoices come back as a list, one bundle per document, so the next modules can treat each one. Search invoices is the newer module for this.

When to use it
you reconcile a batch of invoices with your bank export or a spreadsheet.
Watch out
every returned invoice runs the following modules once, and each run costs an operation, the unit Make counts on your plan.
iDoklad67

Načíst seznam kontaktů

Search

In Make“Vrátí seznam kontaktů, které jsou na iDokladu uloženy.”

The whole list of contacts stored in iDoklad flows out of this module, each contact as its own bundle. Search contacts now fills the same role.

When to use it
you copy your customer base into a CRM or a spreadsheet for the first time.
Watch out
a large address book means many operations downstream; to find one person, Vyhledat kontakty with a filter is lighter.
iDoklad68

Načíst seznam položek ceníku

Search

In Make“Načte seznam položek ceníku.”

Your full iDoklad price list comes back, one item per bundle, ready to compare with a catalog elsewhere. Its successor is Search price list items.

When to use it
you check that shop prices and invoicing prices still match.
Watch out
a full catalog means one bundle per item, so every later module runs as many times as you have products.
iDoklad69

Načíst úhrady

Search

In Make“Načte seznam úhrad. Filtry jsou volitelné.”

Payments recorded in iDoklad come back as a list, and the filters stay optional, so you can pull everything or a narrow slice. Search payments takes over this role in new scenarios.

When to use it
you build a cash report in a spreadsheet from the payments iDoklad knows.
Watch out
leave the filters empty and every payment returns, each one costing an operation in the following steps.
iDoklad70

Vyhledat kontakty

Search

In Make“Vyhledá kontakty na základě nastavených filtrů”

Contacts matching the filters you set come back from iDoklad, which answers the question does this customer already exist. The new name is Search contacts (formerly Vyhledat kontakty).

When to use it
before creating a contact or an invoice from an order form.
Watch out
a search can return several matches, so decide in a filter which one the scenario keeps.
Need help

Need help automating iDoklad with Make?

A person reads every message.

FAQ

Questions about the iDoklad Make integration

01Is the iDoklad Make integration free?
Yes, on the Make side. iDoklad is a standard app, so its modules work from the Free plan, which allows 2 active scenarios, a scheduled run every 15 minutes at most, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Every module run on a bundle is an operation, and Make counts those credits each month. Your iDoklad subscription is a separate matter, handled by iDoklad.
02What do you need to connect iDoklad to Make?
An active iDoklad account and API credentials. In iDoklad, go to Settings, then Aplikace, open the API tab and click Generate to get a Client ID and a Client secret. In Make, add any iDoklad module, click Create a connection, give it a name if you like, and paste both values. If iDoklad asks for a callback URI, the doc gives https://www.integromat.com/oauth/cb/idoklad. The connection is then reused by every iDoklad module in your scenarios.
03Do the iDoklad triggers in Make fire in real time?
No. All 9 iDoklad triggers are scheduled and none is instant, so Make checks iDoklad on the scenario's schedule instead of being called by the app. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. For most billing flows this delay is fine. If you need a faster reaction, lower the interval on a paid plan rather than expecting a webhook from iDoklad.
04What if the iDoklad module you need is missing in Make?
Use Make an API call. It exists for iDoklad and lets your scenario call any endpoint of the iDoklad API with the same connection, so features outside the 79 listed modules stay within reach. You write the request yourself, so keep the iDoklad API documentation at hand and test with Run once. The Make doc for this app also warns that its content is generated from the official iDoklad documentation and may contain mistakes, so contact iDoklad directly when a detail looks wrong.
05Should you use Make or n8n for iDoklad?
It depends on where your team already builds. On Make, iDoklad comes with 79 modules, including 9 scheduled triggers and an API call module, and the visual editor with Run once suits someone starting out. n8n is another automation tool, and apps covered by Make often have an n8n node too, so check whether an iDoklad node exists there before deciding. Base the choice on the modules you actually need for your invoices, contacts and payments, and on the tool your team is ready to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations