Resources · Make integration

FAPI Make integrationAutomate FAPI with Make.

Can Make create, update and settle your FAPI invoices without you touching them? The FAPI Make integration gives you 58 action modules for invoices, clients, orders, vouchers and payments. This guide connects your account, builds a first scenario and explains each module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FAPI Make integration do for you?

The FAPI Make integration links your FAPI account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. FAPI brings 58 modules, all actions, so FAPI never starts a scenario by itself. Something else does, and FAPI does the invoicing work.

Paid invoices that close themselves. When your bank export or payment tool shows money in, Označit fakturu jako zaplacenou marks the matching FAPI invoice as paid, and Spárovat platbu a fakturu pairs a recorded payment with its invoice.

A client and an invoice from one form. A sales form in another app feeds Vytvořit klienta, then Vytvořit fakturu, then Odeslat e-mail/SMS k faktuře sends it out. Nobody retypes an address.

Promo codes handled outside FAPI. A marketing tool decides who gets a discount; Vytvořit slevový kód or Vytvořit voucher creates it in FAPI, and Označit voucher jako invalidní kills it once the campaign ends.

Two things to know first. The module names appear in Czech, and the Make documentation for FAPI gives no description per module and warns that its content is AI-generated and may contain mistakes, so test every module with Run once before trusting it. And FAPI has no trigger and no generic Make an API Call module. New to the editor? The Make training walks through the basics, Make troubleshooting helps when a run fails, and if you are weighing tools, read n8n vs Make.

Connect

How do you connect FAPI to Make?

  1. 01

    Create an API key in FAPI

    In FAPI, open Můj účet, then API klíče, and click Nový API klíč. Give the key a name you will recognize later, create it, then click Zobrazit to reveal the credentials.

  2. 02

    Copy the username and the key

    Two values show on screen: the Username and the API key. Copy both. You need an active FAPI account for this; FAPI's own pricing page covers the subscription side.

  3. 03

    Add a FAPI module and create the connection

    In your Make scenario, add any FAPI module and click Create a connection. A connection is your FAPI account linked to Make once and reused by every FAPI module. Name it if you like in Connection name, paste the two values and save.

First scenario

Build your first scenario with FAPI

GoalWhen a customer fills in an order form in another app, Make creates the invoice in FAPI and sends it by email or SMS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since FAPI has no trigger, this first module comes from the app that holds your orders, such as your form tool.

  2. 02

    Add Vytvořit fakturu

    Click the + on the right of the first module, search for FAPI and pick Vytvořit fakturu. Connect your account, then map the customer data coming from the form into the invoice fields Make shows you.

  3. 03

    Send the invoice out

    Add Odeslat e-mail/SMS k faktuře after it and point it at the invoice the previous module just created. Each item passing between modules is a bundle, here one invoice.

  4. 04

    Test with Run once

    Submit a test order, then click Run once. Read the bundles each module received and check in FAPI that the invoice exists and was sent.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on one bundle is an operation, which is what Make counts on your plan.

Modules

What each FAPI module does

FAPI gives you 58 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

FAPI1

Aktivace Pravidelné fakturace

ActionIn the docs only

This module switches on recurring invoicing in FAPI, so a billing cycle you prepared starts producing invoices on its own.

When to use it
a customer confirms a subscription in your CRM, and you want their recurring billing to start without opening FAPI.
Watch out
run it on a test customer first, since a wrongly activated cycle keeps issuing invoices until you stop it with Zastavení pravidlené fakturace.
FAPI2

Aktualizovat data faktury

ActionIn the docs only

Keep an existing invoice accurate: this action rewrites the data of a FAPI invoice that is already there, instead of creating a second one.

When to use it
a customer sends a corrected billing detail after the invoice went out, and the fix lives in another tool.
Watch out
the module has to know which invoice to change, so map it from an earlier FAPI module rather than typing it by hand.
FAPI3

Aktualizovat data klienta

ActionIn the docs only

Your FAPI client records stay in sync with the rest of your stack: this module edits the details of a client that already exists in FAPI.

When to use it
a customer changes their company address in your CRM, and future invoices should carry the new one.
Watch out
pick Vytvořit klienta instead when the person is new, otherwise there is nothing to update.
FAPI4

Aktualizovat data objednávky

ActionIn the docs only

Changes to an order no longer need a manual edit: this action updates an order already recorded in FAPI with fresh data from your scenario.

When to use it
fulfillment happens in another tool, and the order in FAPI should reflect what that tool now says about it.
Watch out
map the order from Vytvořit objednávku or another FAPI module so the right one gets changed.
FAPI5

Aktualizovat slevový kód

ActionIn the docs only

Adjust a live promotion without recreating it: this module edits a discount code that already exists in FAPI.

When to use it
your marketing team extends or changes an offer in a planning sheet, and FAPI should follow the change.
Watch out
a discount code and a voucher are separate objects in FAPI, each with its own modules, so check which one your offer actually uses.
FAPI6

Aktualizovat voucher

ActionIn the docs only

A voucher you already issued can be corrected here: the module changes the data of an existing FAPI voucher instead of issuing a new one.

When to use it
a gift voucher was sold with a typo or the wrong holder, and support fixes it from a ticketing tool.
Watch out
to cancel a voucher rather than edit it, Označit voucher jako invalidní is the clearer choice.
FAPI7

Aktualizovat šablonu pravidelné fakturace

ActionIn the docs only

Future recurring invoices change in one place: this action edits the template that FAPI uses to generate a recurring invoice, so every invoice built from it carries the new data.

When to use it
a subscriber upgrades their plan in your sales tool and their next invoices should reflect it.
Watch out
invoices already issued from the template keep their old content.
FAPI8

Aktualizovat šablonu produktu

ActionIn the docs only

Product changes flow into FAPI without a manual edit: this module updates a product template stored in FAPI.

When to use it
your catalog lives in a spreadsheet or an online store, and a product you edited there should be edited in FAPI too.
Watch out
use Získat data šablon produktů in an earlier step if you need to find the right template before changing it.
FAPI9

Aplikovat (použít) voucher

ActionIn the docs only

Redeem a voucher from outside FAPI: this module marks a FAPI voucher as applied, the Czech label meaning apply or use.

When to use it
a customer spends a gift voucher at a point of sale or in a booking tool that is not FAPI, and FAPI should know it is used.
Watch out
if the redemption gets reversed, Označit voucher jako neaplikovaný (nepoužitý) puts it back to unused.
FAPI10

Odebrat štítky z faktury

ActionIn the docs only

Clean labels off an invoice automatically: this action removes tags (štítky) from a FAPI invoice.

When to use it
you tag invoices as waiting for review, and once the check is done in another tool, the tag should disappear from FAPI.
Watch out
it only takes tags off; to put some on, pair it with Přidat štítky k faktuře.
FAPI11

Odeslat e-mail/SMS k faktuře

ActionIn the docs only

Your customer gets their invoice without anyone pressing send: this module has FAPI send an email or SMS about a given invoice.

When to use it
right after Vytvořit fakturu in the same scenario, so a new invoice leaves the moment it exists.
Watch out
test it on your own address first with Run once, because a real customer receives whatever the test sends.
FAPI12

Označit fakturu jako stornovanou

ActionIn the docs only

Cancelled deals stop showing as money owed: this action marks a FAPI invoice as cancelled (stornovaná) while keeping it on record.

When to use it
an order is refunded or voided in your store, and the matching invoice should be cancelled instead of deleted.
Watch out
Smazat fakturu removes the invoice entirely, which is a different result, so choose on purpose.
FAPI13

Označit fakturu jako zaplacenou

ActionIn the docs only

Stop ticking paid invoices by hand: this module flags a FAPI invoice as paid (zaplacená).

When to use it
your payment provider or bank feed confirms money for an invoice, and FAPI should show it as settled.
Watch out
if you also record the payment itself with Vytvořit platbu, check with Run once that the two steps do not settle the same invoice twice.
FAPI14

Označit voucher jako invalidní

ActionIn the docs only

Shut down a voucher that should no longer work: this action marks a FAPI voucher as invalid.

When to use it
a campaign ends, a voucher gets reported as leaked, or an order paid with it is refunded.
Watch out
invalid is not the same as unused; to hand a voucher back to its holder, the module for marking it unapplied is the right one.
FAPI15

Označit voucher jako neaplikovaný (nepoužitý)

ActionIn the docs only

Give a voucher a second life: this module sets a FAPI voucher back to not applied, meaning unused.

When to use it
an order that consumed a voucher gets cancelled, and the customer should be able to spend it again.
Watch out
it undoes Aplikovat (použít) voucher, so run it only when the original use really fell through.
FAPI16

Přidat položku do faktury

ActionIn the docs only

Build an invoice line by line: this action adds an item (položka) to an existing FAPI invoice.

When to use it
an order holds several products, and each one arriving as its own bundle should become one line of the same invoice.
Watch out
every item added costs one operation, so a long order uses several; to fix a line rather than add one, go with Upravit položku faktury.
FAPI17

Přidat štítky k faktuře

ActionIn the docs only

Sort invoices without opening FAPI: this module attaches tags (štítky) to a FAPI invoice, so filtering them later takes one click.

When to use it
invoices coming from a given sales channel or campaign should carry a label your accountant can filter on.
Watch out
removing tags is a separate module, Odebrat štítky z faktury.
FAPI18

Sledovat notifikace faktury

ActionIn the docs only

The Czech name means watch invoice notifications, yet Make lists this module as an action, not a trigger, so it cannot start a scenario.

When to use it
place it inside a scenario that another app or a schedule already launches, then check with Run once what it returns.
Watch out
the doc gives no description for it, so read the bundles before building anything on top.
FAPI19

Sledovat notifikace voucheru

ActionIn the docs only

Its sibling for vouchers: the name reads as watch voucher notifications, and like the invoice version, Make types it as an action rather than a trigger.

When to use it
inside a scenario already started elsewhere, when you want to see what FAPI reports about vouchers.
Watch out
no official description exists, so run it once on a test voucher and study the output before relying on it.
FAPI20

Smazat Klienta

ActionIn the docs only

Remove a client from FAPI entirely: the module deletes a client record, the Czech smazat meaning delete.

When to use it
a person asks for their data to be erased in your CRM, and FAPI should follow that request.
Watch out
treat a deletion as final; a filter placed before this module, checked with Run once, keeps a wrong bundle from wiping the wrong client.
FAPI21

Smazat export

ActionIn the docs only

Tidy up exports you no longer need: this action deletes an export from FAPI.

When to use it
at the end of a scenario that created an export with Vytvořit nový export faktur and downloaded it with Stáhnout export, so nothing piles up.
Watch out
place it after the download step, never before, or the file is gone before you fetch it.
FAPI22

Smazat fakturu

ActionIn the docs only

Erase an invoice from FAPI: this module deletes it outright instead of cancelling it.

When to use it
a draft or test invoice was created by mistake, for example while you were building the scenario.
Watch out
for a real sale that fell through, Označit fakturu jako stornovanou keeps a trace, which is usually what your accounting needs.
FAPI23

Smazat platbu

ActionIn the docs only

Undo a payment record: this action deletes a payment stored in FAPI.

When to use it
a payment was recorded twice, or a scenario test with Vytvořit platbu left a fake one behind.
Watch out
if the payment was paired with an invoice, check afterward in FAPI that the invoice status still matches reality.
FAPI24

Smazat položku faktury

ActionIn the docs only

Drop a single line from an invoice while the rest stays intact: this module deletes one item from a FAPI invoice.

When to use it
a customer removes one product from their order in your store, and only that line should leave the invoice.
Watch out
to change a quantity or price instead, Upravit položku faktury is the gentler option.
FAPI25

Smazat slevový kód

ActionIn the docs only

Clear out discount codes you are done with: this action deletes one from FAPI.

When to use it
codes generated for a one-off test or a mistaken batch should vanish from your list.
Watch out
a code customers already hold stops working at once, so for a campaign that simply ends, updating it with Aktualizovat slevový kód may be kinder.
FAPI26

Smazat voucher

ActionIn the docs only

Remove a voucher from FAPI for good: this module deletes it rather than flagging it.

When to use it
a voucher was issued by error, for example by a scenario you were still testing.
Watch out
for a voucher that was sold and must stop working, Označit voucher jako invalidní keeps the history, which support will thank you for.
FAPI27

Smazat šablonu produktu

ActionIn the docs only

Retire a product from FAPI: this action deletes a product template (šablona produktu).

When to use it
a product disappears from your online store or catalog sheet, and FAPI should stop offering it as well.
Watch out
fetch the template first with Získat data šablon produktů and filter on it, so a missing value never points the deletion at the wrong product.
FAPI28

Spárovat platbu a fakturu

ActionIn the docs only

Link money to the invoice it pays: this module pairs (spárovat) a payment and an invoice in FAPI.

When to use it
payments land in FAPI through Vytvořit platbu or another channel, and each one should be matched to its invoice without manual reconciliation.
Watch out
both the payment and the invoice must already exist, so map them from earlier modules in the scenario.
FAPI29

Stáhnout export

ActionIn the docs only

Get the export file itself into your scenario: this action downloads (stáhnout) an export from FAPI.

When to use it
after Vytvořit nový export faktur, to send the file to your accountant's storage or attach it to an email in the next module.
Watch out
on the Free plan Make handles files up to 5 MB, so a large export may need a paid plan.
FAPI30

Univerzální REST dotaz

ActionIn the docs only

The name translates as universal REST request, which suggests a way to reach FAPI endpoints the other modules do not cover.

When to use it
only when none of the named modules does what you need and you know the FAPI API well enough to write the request.
Watch out
this is not Make's own Make an API Call module, and the doc describes neither its fields nor its behavior, so test carefully.
FAPI31

Upravit položku faktury

ActionIn the docs only

Correct one line of an invoice in place: this module edits an item that already sits on a FAPI invoice.

When to use it
a customer changes the quantity of one product after ordering, and the invoice line should follow.
Watch out
it edits a line, it does not add one; for a new product on the same invoice, Přidat položku do faktury is the tool.
FAPI32

Vyhledat exporty

ActionIn the docs only

Find exports already sitting in FAPI: the name means search exports, handy when you did not create them in the same run.

When to use it
before Stáhnout export or Smazat export, to locate the file a colleague generated in FAPI.
Watch out
a search can hand back several exports, each as its own bundle, and every following module then runs once per bundle.
FAPI33

Vytvořit fakturu

ActionIn the docs only

Issue an invoice straight from another app: this action creates a new invoice (faktura) in FAPI from the data your scenario carries.

When to use it
a deal closes in your CRM or an order form comes in, and the customer should get an invoice without anyone typing it.
Watch out
each run creates a new invoice, so a test with Run once leaves a real one to clean up.
FAPI34

Vytvořit klienta

ActionIn the docs only

Add a customer to FAPI automatically: the module creates a new client record ready for invoicing.

When to use it
a lead signs up through a form or becomes a customer in your CRM, and you want them in FAPI before the first invoice.
Watch out
running it for a person who already exists may create a duplicate; Aktualizovat data klienta handles returning customers.
FAPI35

Vytvořit nový export faktur

ActionIn the docs only

Have FAPI prepare an invoice export for you: this action starts a new export of invoices.

When to use it
your accountant asks for the invoices of a period, and you want the export produced and sent without logging into FAPI.
Watch out
creating the export is only half the job; chain Stáhnout export to actually get the file into the scenario.
FAPI36

Vytvořit objednávku

ActionIn the docs only

Record an order in FAPI coming from another channel: the module creates a new order (objednávka).

When to use it
sales happen in a store or booking tool that is not FAPI, and you still want every order tracked there.
Watch out
an order is not an invoice; if you need both, add Vytvořit fakturu as a separate step and test the pair with Run once.
FAPI37

Vytvořit platbu

ActionIn the docs only

Log incoming money in FAPI: this action creates a payment (platba) record.

When to use it
your payment gateway or bank tool reports a transfer, and FAPI should hold a matching payment.
Watch out
a payment on its own does not settle anything; follow it with Spárovat platbu a fakturu so it lands on the right invoice.
FAPI38

Vytvořit slevový kód

ActionIn the docs only

Generate a discount code in FAPI from outside it: this module creates a new slevový kód, the Czech term for discount code.

When to use it
a customer joins your newsletter or finishes a survey, and a personal code should wait for them in FAPI.
Watch out
each run creates one code, so a list of recipients turns into as many codes and as many operations.
FAPI39

Vytvořit voucher

ActionIn the docs only

Issue a voucher automatically: this action creates a new voucher in FAPI.

When to use it
someone buys a gift card in your store, or earns a reward in a loyalty tool, and the voucher should exist in FAPI right after.
Watch out
vouchers and discount codes follow separate modules in FAPI; pick the object your checkout actually accepts.
FAPI40

Vytvořit šablonu pravidlené fakturace

ActionIn the docs only

Set up recurring billing from another tool: this module creates a template for recurring invoicing in FAPI.

When to use it
a new subscriber signs up in your sales tool, and their recurring invoice should be prepared without anyone opening FAPI.
Watch out
a template alone issues nothing; Aktivace Pravidelné fakturace is the step that switches the cycle on.
FAPI41

Vytvořit šablonu předmětu

ActionIn the docs only

Add a new item template (předmět) to FAPI without opening its admin, which is what the Czech name says. You stop typing the same item twice.

When to use it
a product you just launched should exist in FAPI as a reusable line before the first invoice goes out.
Watch out
the doc lists no fields for it. Check what Make asks for once the connection exists, then test with Run once.
FAPI42

Zastavení pravidlené fakturace

ActionIn the docs only

End a recurring invoice schedule from your scenario; the name reads “stop recurring invoicing”. It is the opposite of Aktivace Pravidelné fakturace.

When to use it
a customer cancels in your helpdesk or CRM, and billing in FAPI should end with it.
Watch out
test on a dummy client with Run once first, since a stopped schedule means no invoice goes out.
FAPI43

Získat data exportu

ActionIn the docs only

Read the details of one FAPI export without leaving your scenario. The label translates as “get export data”.

When to use it
after Vytvořit nový export faktur, to check the export before Stáhnout export fetches the file.
Watch out
Free plan files stop at 5 MB, so a large export may need a paid plan.
FAPI44

Získat data faktur

ActionIn the docs only

Your invoice data leaves FAPI and can feed a spreadsheet, a report or a message to finance. The Czech name means “get invoice data”.

When to use it
your accountant wants invoice figures in a tool other than FAPI, and copying them by hand keeps going wrong.
Watch out
click Run once and read the output before mapping it, so you see what Make actually receives.
FAPI45

Získat data klienta

ActionIn the docs only

Look up one FAPI client mid-scenario and reuse the record further down the chain. The label means “get client data”, the singular form next to the create, update and delete client modules.

When to use it
before Aktualizovat data klienta, to see what the client record holds right now.
Watch out
map the client from an earlier module rather than typing it.
FAPI46

Získat data měn

ActionIn the docs only

No more hard-coded currency: this module pulls the currencies FAPI knows (“get currency data”), so later steps stay in line with FAPI.

When to use it
you sell in more than one currency and want the next step to use FAPI's values, not a guess.
Watch out
the doc does not say what comes back, so inspect the bundle after a test run.
FAPI47

Získat data objednávek

ActionIn the docs only

Bring your FAPI orders into Make so they can land in a sheet, a CRM or a team channel without anyone exporting them. The Czech name means “get order data”.

When to use it
sales and delivery work in different tools and both need the same list of FAPI orders.
Watch out
each module run on one bundle counts as an operation, so keep an eye on usage once the scenario is live.
FAPI48

Získat data plateb

ActionIn the docs only

This is the reading side of payments, next to Vytvořit platbu and Smazat platbu: it pulls the payments already recorded in FAPI (“get payment data”).

When to use it
finance wants to reconcile FAPI payments with the bank export before Spárovat platbu a fakturu links them.
Watch out
run it once on its own first and look at the output, so the mapping in later modules matches real data.
FAPI49

Získat data pravidelných faktur

ActionIn the docs only

See what is scheduled without logging into FAPI: this module reads recurring invoices, the ones FAPI sends again and again (“get recurring invoice data”).

When to use it
before stopping or reactivating billing for a client, to check which recurring invoice is concerned.
Watch out
do not mix it up with Získat data šablony pravidelných faktur, which reads the template, not the invoices.
FAPI50

Získat data slevového kódu

ActionIn the docs only

Check one discount code before acting on it. The label reads “get discount code data”, in the singular.

When to use it
a customer asks support whether a code is still valid, and the answer should come from FAPI, not from memory.
Watch out
for several codes at once, the plural module Získat data slevových kódů is the one to pick.
FAPI51

Získat data slevových kódů

ActionIn the docs only

Pull all your FAPI discount codes at once for an overview, rather than one code at a time. The name means “get discount codes data”.

When to use it
marketing wants the current promo codes listed in a shared sheet after a campaign ends.
Watch out
a near twin of this module ends in “špatný”, Czech for “wrong”, and the doc does not explain the difference; compare both outputs with Run once.
FAPI52

Získat data slevových kódů - špatný

ActionIn the docs only

This one also reads discount codes from FAPI, but its label ends in “špatný”, which means “wrong” in Czech. Nothing in the doc explains that suffix, so treat it with care.

When to use it
only if the unmarked Získat data slevových kódů does not return what your scenario needs.
Watch out
compare its bundles with the unmarked module using Run once before building anything on top of it.
FAPI53

Získat data voucheru

ActionIn the docs only

Check a voucher's state before you touch it: this action reads one FAPI voucher (“get voucher data”). It comes before you apply, invalidate or reset it.

When to use it
a gift voucher is presented at checkout and you want to confirm its state in FAPI before Aplikovat (použít) voucher.
Watch out
map the voucher from an earlier module; a typed value breaks as soon as the next voucher arrives.
FAPI54

Získat data šablon produktů

ActionIn the docs only

Your FAPI product templates arrive in Make, so later modules know which products exist before an order or invoice is built. The name means “get product template data”.

When to use it
your catalogue lives in FAPI and a website or sheet should mirror it without manual copying.
Watch out
the doc lists no fields, so open the output after a test run to see what each bundle carries.
FAPI55

Získat data šablony pravidelných faktur

ActionIn the docs only

Here you read the template behind a recurring invoice, not the invoices it produces: the pattern FAPI reuses each time (“get recurring invoice template data”).

When to use it
before Aktualizovat šablonu pravidelné fakturace, to see what the template holds and change only what needs it.
Watch out
reading the template is not the same as reading issued invoices, which Získat data pravidelných faktur handles.
FAPI56

Získat kódy států

ActionIn the docs only

Get country codes the way FAPI writes them (“get country codes”), so addresses go out with FAPI's codes instead of free text.

When to use it
a web form collects country names in plain words and you want FAPI's code before Vytvořit klienta runs.
Watch out
check the output with Run once to learn how codes are written before you map them.
FAPI57

Získá data položky faktury

ActionIn the docs only

One line of an invoice, not the whole document, is what this action reads (“gets invoice item data”). You can check that line or pass it on by itself.

When to use it
before Upravit položku faktury, so the scenario sees the current line and edits only what changed.
Watch out
map the line from an earlier module rather than typing it by hand.
FAPI58

Získá konverzní data objednávky

ActionIn the docs only

Pull the conversion data attached to a FAPI order (“gets order conversion data”). It looks at the order from a different angle than the plain order modules.

When to use it
marketing wants to connect FAPI orders to the campaign reporting it keeps in another tool.
Watch out
the doc does not say what the conversion data contains, so inspect a real bundle before mapping it.
Need help

Need help automating FAPI with Make?

A person reads every message.

FAQ

FAPI and Make: common questions

01Is the FAPI Make integration free?
Yes on the Make side: FAPI is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs a scheduled scenario every 15 minutes at the shortest, stops a run after 5 minutes, handles files up to 5 MB and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to one minute and remove the active scenario limit. You still need an active FAPI account with an API key, and FAPI bills that subscription separately.
02What do you need to connect FAPI to Make?
An active FAPI account and an API key. In FAPI, go to Můj účet, then API klíče, click Nový API klíč, name it, create it and click Zobrazit to reveal the credentials. Copy the Username and the API key. Then, in Make, add any FAPI module, click Create a connection, paste both values and save. From then on, that single connection serves all 58 FAPI modules in every scenario you build.
03Can FAPI start a Make scenario in real time?
No. FAPI has no trigger module in Make, scheduled or instant, so it never starts a scenario by itself. Two modules carry notification in their names, but Make lists them as actions. To run FAPI modules, start the scenario from another app's trigger, for example a form or store event, or set a schedule on the first module. A new scenario checks every 15 minutes by default, and paid plans go down to one minute.
04What if the FAPI module you need is missing in Make?
It depends on the gap. FAPI has no generic Make an API Call module, so that route is closed. The list does include Univerzální REST dotaz, whose name points to a universal REST request, but the doc does not describe it, so test it with Run once before counting on it. Otherwise, handle the missing step in another app of the scenario, or describe your case through the help form on this page.
05Should you use Make or n8n to automate FAPI?
It depends on what your stack already runs. On Make, FAPI offers 58 action modules, no trigger, and a connection built from a username and an API key, all usable from the Free plan within its limits. Before choosing n8n, check whether it offers a FAPI node that covers the objects you need, since this page only documents the Make side. Pick the tool where your other apps already live, and compare the two on concrete criteria.