Resources · Make integration

NeoGate Make integrationAutomate NeoGate with Make.

Can Make work with NeoGate for you? Yes. The NeoGate Make integration gives you 2 action modules with Czech names, Poslat zprávu and Vypsat kredit. The official doc says little about them, so this guide sticks to what is known: linking your account, building a first scenario and testing it safely.

Try the NeoGate integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NeoGate Make integration do for you?

The NeoGate Make integration lets a Make scenario, the automation you build as a chain of modules, act on your NeoGate account without code. It offers 2 modules, both actions: one whose Czech name means "send a message" and one whose name means "list credit". It has no trigger, so another app or a schedule starts the flow.

A word of caution first. Make lists NeoGate in its Communication category but publishes no description for either module, and its doc states that information about the app is limited. The ideas below rest on the module names, so open each module and check its fields before you rely on it.

Messages that follow an event. A form reply, a new order or a row added in another app becomes a NeoGate message through Poslat zprávu. Every module in the chain passes a bundle, one item such as one reply, to the next.

A credit check right after sending. Chain Vypsat kredit behind Poslat zprávu and the scenario ends by reading what your account reports, which you can route to a sheet or a chat.

A plain credit report. Use Vypsat kredit alone as the first module and let the schedule run it; each run costs one operation, the unit Make counts on your plan.

New to the editor? The Make training covers the basics, and the n8n vs Make comparison helps if you are still choosing a platform.

Connect

How do you connect NeoGate to Make?

  1. 01

    Add a NeoGate module

    In your scenario, click the +, search for NeoGate and pick one of its two modules. A connection, your NeoGate account linked to Make once, is needed before the module can do anything, so click Create a connection.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the account or team it belongs to. This step is optional, but it helps as soon as you link a second NeoGate account.

  3. 03

    Authorize and save

    Either approve access on the NeoGate page that opens, or paste the key NeoGate gives you, depending on what the window asks for. Then click Save. Both NeoGate modules reuse this connection from then on.

First scenario

Your first scenario with NeoGate and Make

GoalWhen a new entry lands in another app, Make passes it to the Poslat zprávu module, then runs Vypsat kredit to read what your NeoGate account reports.

  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

    Pick the starting app

    NeoGate has no trigger, so the flow opens on another app: search it by name, choose the module that watches for new entries and link its account with Create a connection.

  3. 03

    Add Poslat zprávu

    Click the + on the right of the first module, search NeoGate and pick Poslat zprávu. Then fill its fields by mapping values from the first module instead of typing them.

  4. 04

    Chain Vypsat kredit

    Add one more module with the + on the right and choose Vypsat kredit. It reuses the same NeoGate connection, so there is nothing new to authorize.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check what NeoGate sent back.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Modules

What each NeoGate module does

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

NeoGate1

Poslat zprávu

ActionIn the docs only

Going by its Czech name, "send a message", this is the module that sends content from your scenario out through NeoGate. Place it after the module that produces the text and map the values into its fields.

When to use it
a new entry in another app, such as a form reply or an order, should go out through NeoGate.
Watch out
Make publishes no description for this module, so test it with Run once on harmless data before the scenario goes live.
NeoGate2

Vypsat kredit

ActionIn the docs only

Gives your scenario a reading of the credit on your NeoGate account, if the module does what its Czech name, "list credit", suggests. It is the one to pick when you want to know where you stand rather than send anything.

When to use it
right after Poslat zprávu, or alone as the first module of a scheduled scenario.
Watch out
check the bundle it returns during Run once before mapping it into another app.
Need help

Need help automating NeoGate with Make?

A person reads every message.

FAQ

NeoGate and Make: common questions

01Is the NeoGate Make integration free?
Yes, NeoGate is a standard app, so its modules work on the Make Free plan. That plan has limits worth knowing before you build: 2 active scenarios, at least 15 minutes between two 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. Every plan counts usage in operations per month, one per module run on a bundle.
02What do you need to connect NeoGate to Make?
A NeoGate account and a Make account. The Make doc lists no other prerequisite and gives no NeoGate-specific steps, so the standard flow applies: add a NeoGate module, click Create a connection, optionally name it, then either authorize Make on the NeoGate page or paste the key NeoGate provides, and click Save. The doc does not say which of the two methods NeoGate uses, so check the connection window before gathering anything. Once saved, the connection serves both NeoGate modules.
03Can the NeoGate Make integration start a scenario on its own?
No. NeoGate has no trigger in Make, only two actions, so something else has to start the scenario. You have two options. Put a trigger from another app first, so NeoGate acts whenever that app records something new. Or place a NeoGate module first and let the schedule start it: a new scenario runs every 15 minutes by default, the Free plan allows no shorter interval, and paid plans go down to 1 minute. Either way, test with Run once before switching the scenario on.
04What if the NeoGate Make integration lacks a module you need?
It depends on what is missing. NeoGate has no Make an API Call module in Make, so there is no way to reach other NeoGate features from its own app in the editor. The doc also warns that information about NeoGate is limited, which explains the two bare modules. If the job goes beyond sending a message or reading credit, look at whether another communication app on Make covers it, or ask the team through the help form further down this page.
05Make or n8n for NeoGate?
It depends on what each tool offers for NeoGate on the day you build. On Make, the app is available from the Free plan with 2 action modules and no trigger, and the doc on it is thin. The same app often has an n8n node too, so check the n8n catalog for NeoGate before deciding. Compare the actions each side exposes, how the connection works and which editor your team already uses. Neither choice is better by default; the right one covers the steps your process needs.
Same platform

Other docs you might need on this stack.

Browse all integrations