Resources · Make integration

EET Make integrationAutomate EET with Make.

Can Make send your sales to EET without a line of code? The EET Make integration gives you 2 action modules: one creates the taxpayer's signature code, the other sends the registered sale message. This guide shows how to connect the account, what each module is for and how to build a first scenario.

Try the EET integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the EET Make integration do for you?

The EET Make integration links your EET account to Make, a visual tool where you chain modules into a scenario, the automation you build. A module is one brick of that chain. EET brings two of them, both actions: one creates a taxpayer's signature code (PKP), the other sends a registered sale data message. There is no trigger, so another app or a schedule starts the flow.

Register a sale straight from your checkout data. A sale recorded in another tool starts the scenario, then Send a registered sale data message passes it to EET. Each item that moves between modules is called a bundle, here one sale.

Prepare the signature code first. Place Create a Taxpayer's Signature Code (PKP) before the sending module when your message needs that code. The module names suggest this order; the documentation does not spell it out, so check it with a test run.

Keep one flow per sales channel. A web shop and a physical till can each feed their own scenario and reuse the same connection, your EET account linked to Make once.

Know the limits before you start. Make states that its documentation for EET is limited, because little public information about the app exists. No field list, no quota and no error guide are given, so the editor itself is your reference. The Make troubleshooting page helps when a run fails, and Make review covers the tool as a whole. If you also look at n8n, read n8n vs Make before choosing.

Connect

How do you connect EET to Make?

  1. 01

    Add an EET module

    In your scenario, click the +, search for EET and pick one of its two modules. Make then asks for a connection: click Create a connection to open the setup window.

  2. 02

    Name the connection

    Giving the connection a name is optional, yet it pays off once you manage several accounts. A label such as the shop or company it belongs to tells you at a glance which account a module is using.

  3. 03

    Authorize and save

    Approve access on the EET page if Make opens one, or paste the key EET provides. Then click Save. Every EET module in your scenarios can reuse this connection afterwards.

First scenario

Your first scenario with EET

GoalWhen a sale lands in another app, Make creates the PKP code and sends the registered sale message to EET.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Choose the app where your sales are recorded as the first module, since EET has no trigger of its own.

  2. 02

    Add the PKP module

    Click the + on the right, search for EET and pick Create a Taxpayer's Signature Code (PKP). Click Create a connection if this is your first EET module.

  3. 03

    Send the sale

    Add Send a registered sale data message next. Fill its fields by mapping data from the earlier modules: the sale from the first app, the code from the PKP module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received and spot any empty value.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock icon, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the EET modules do

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

EET1

Create a Taxpayer's Signature Code (PKP)

ActionIn the docs only

This action produces a taxpayer's signature code, the PKP, and hands it to the next module as a value you can map. You get the code inside the scenario instead of computing it elsewhere.

When to use it
place it before the sale message whenever that message needs the PKP of the sale.
Watch out
the documentation gives no field list, so read what the module asks for in the editor and test with Run once.
EET2

Send a registered sale data message

ActionIn the docs only

Sending the sale itself happens here: the module takes one sale per bundle and delivers its data message to EET. It is the step that actually registers the sale.

When to use it
at the end of the flow, once the sale data and any PKP code are ready to map.
Watch out
it acts on one sale per run, so a list of sales from the first app creates one operation per sale.
Need help

Need help automating EET with Make?

A person reads every message.

FAQ

EET and Make: common questions

01Is the EET Make integration free?
Yes, EET is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, per month. This page gives no price for EET or for Make, only the plan limits Make publishes.
02What do you need to connect EET to Make?
An EET account and a Make account. The documentation lists no prerequisite and no dedicated setup steps, so the generic Make flow applies: add an EET module, click Create a connection, optionally name it, authorize Make on the EET page or paste the key EET gives you, then click Save. The connection is then reused by both EET modules. Because the documentation is limited, confirm with EET which credentials belong to your account if the first attempt fails.
03Does the EET Make integration have a trigger?
No, EET has no trigger module, so nothing in EET starts a scenario by itself. Two options remain. Start the flow on a trigger from another app, such as the tool where your sales are recorded, then add the EET actions after it. Or start it on the schedule of the first module, which Make sets to every 15 minutes by default; on the Free plan the shortest interval is 15 minutes, on paid plans 1 minute. The scenario then runs on that clock rather than at the moment a sale happens.
04What if an EET module is missing in Make?
It depends on what you need. EET offers only 2 actions in Make and no Make an API Call module, so you cannot reach other parts of EET through a custom request inside this app. Make also says its EET documentation is limited, with no quotas or error guide published. If a step is missing, look for another app in Make that covers it, or ask the Hack'celeration agency team to study the case with you before you build around a gap.
05Should you use Make or n8n for EET?
It depends on the modules you need. On Make, EET brings two actions, one for the PKP code and one for the registered sale message, and no trigger. Many apps also have an n8n node, but this page does not confirm one for EET, so check the n8n side before you compare. Choose the tool where the steps of your flow exist as ready modules, and test one real sale in it. The comparison page linked above sets out the general differences between the two tools, without a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations