Resources · Make integration

Neaktor Make integrationAutomate Neaktor with Make.

Can Make keep your Neaktor tasks in step with the rest of your tools? The Neaktor Make integration gives you 7 modules: one trigger, five actions and one search, all about tasks. This page shows you how to link your account, build a first scenario and pick the right module.

Try the Neaktor integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Neaktor Make integration do for you?

The Neaktor Make integration links your Neaktor account to Make, a no-code tool where you chain apps together. You build a scenario, the automation itself, out of modules, the bricks that each read or change something in one app. For Neaktor, those bricks all work on tasks.

Tasks that open themselves. A form, a CRM or a shared inbox receives a request, and Create a Task opens the matching task in Neaktor with the details already filled in. Nobody has to retype the request.

A task list that tells other apps what changed. Watch Tasks starts the scenario from Neaktor, so a task can post a message in team chat, add a row to a sheet or start a follow-up in another tool.

Cleanup and lookups on demand. Search Tasks finds the tasks that match what you need, Get a Task pulls one full record, and Update a Task or Delete a Task acts on it. When the listed modules stop short, Make an API Call reaches any other endpoint of the Neaktor API with the same connection.

Keep in mind that Make only does what these modules allow, and the official app documentation warns that its own content may contain mistakes, so check the details against Neaktor when something matters. If you also weigh n8n, which often has a node for the same app, read our n8n vs Make comparison. For costs, see Make pricing, and for a guided start, Make training.

Connect

How do you connect Neaktor to Make?

  1. 01

    Generate an OAuth2 key in Neaktor

    In Neaktor, open the three-line menu, then Integrations and API keys. Click Generate new key, choose OAuth2 keychain, enter the callback URI https://www.integromat.com/oauth/cb/neaktor if asked, then click Create API key.

  2. 02

    Set the key to read and write

    Switch the status of the new key to Read and write, otherwise Make could read tasks without being able to change them. Then copy the Client ID and the Client secret that Neaktor shows on screen and keep them at hand.

  3. 03

    Create the connection in Make

    In your scenario, add any Neaktor module and click Create a connection. Naming it in Connection name is optional, though handy once you run several accounts, so fill it if you like; then paste the credentials you copied, or follow the prompts, and save.

First scenario

Your first scenario with Neaktor

GoalWhen Watch Tasks returns a task from Neaktor, Make runs Update a Task on it.

  1. 01

    Create a new scenario

    Open the Scenarios page in Make, create a new scenario and click the big + in the middle of the editor to add your first module.

  2. 02

    Add the Watch Tasks trigger

    Search for Neaktor, pick Watch Tasks and click Create a connection to link your account with the Client ID and Client secret. Once connected, Make lists what it can read in Neaktor so you can fill the module fields.

  3. 03

    Add Update a Task

    Click the + on the right of Watch Tasks, choose Neaktor again and pick Update a Task. Map the task coming from the trigger into it, so the update lands on that exact task.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles, the items each module received. Open them to check that the right task went through before you go further.

  5. 05

    Schedule and switch it on

    Click the clock on Watch Tasks to set the schedule. A new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Triggers

What can start a Neaktor scenario?

1 module starts a scenario when something happens in Neaktor. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Neaktor as soon as it happens.

Neaktor1Watch Tasks

Watch Tasks

triggerIn the docs only

Watch Tasks gives your scenario a starting point inside Neaktor: it hands tasks to the next modules as bundles, one per task, so each can be sent to another app or processed on its own. Its scheduled type is deduced from its name, so review its options once connected.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
when work tracked in Neaktor should set off something elsewhere, such as a message to the team or a line in a report.
Watch out
each check uses operations, the unit Make counts on your plan, so pick a schedule that matches how fast you really need to react.
Modules

What can Make do in Neaktor?

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

Neaktor1

Create a Task

ActionIn the docs only

Create a Task turns data coming from another app into a fresh Neaktor task, so requests land in your task list without anyone copying them over. It fits at the end of a scenario.

When to use it
a web form, a support email or a deal in your CRM should become a piece of work someone picks up in Neaktor.
Watch out
run the scenario once with Run once and check the new task before switching it on, so duplicates do not pile up.
Neaktor2

Delete a Task

ActionIn the docs only

Delete a Task removes one task from Neaktor for you, which keeps the list clean when the work behind it no longer exists elsewhere. It targets a single task at a time.

When to use it
an order is cancelled or a request is withdrawn in another tool, and the related task should go too.
Watch out
place a filter before it so only the right tasks reach it, and test on a throwaway task first.
Neaktor3

Get a Task

ActionIn the docs only

Get a Task fetches the full record of one task you already know, so later modules can use its details. Choose it over Search Tasks when you hold the exact task rather than a description of what you want.

When to use it
a trigger or a previous module gives you a task reference and you need everything about that task before writing to another app.
Watch out
it reads a single task; to look through several, start with Search Tasks instead.
Neaktor4

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Neaktor API from your scenario, reusing the connection you already created. It covers whatever the other six modules leave out.

When to use it
you need something from Neaktor that Create, Get, Update, Delete and Search Tasks do not offer.
Watch out
you build the request yourself, so keep the Neaktor API documentation open and check the result of each run with Run once before you rely on it.
Neaktor5

Search Tasks

SearchIn the docs only

Search Tasks looks through your Neaktor tasks and returns every match, which lets a scenario act on a whole batch instead of one known task. The answer can hold zero, one or many bundles.

When to use it
you want to find the tasks tied to a client or a project before updating or reporting on them.
Watch out
the modules after it run once per task found, so a broad search can use many operations in a single run.
Neaktor6

Update a Task

ActionIn the docs only

Update a Task changes an existing Neaktor task so it reflects what just happened in another tool, without anyone opening Neaktor to edit it. It needs to know which task to change.

When to use it
a payment clears, a ticket closes or a file arrives, and the matching task should move forward on its own.
Watch out
map the task from Watch Tasks, Get a Task or Search Tasks, otherwise the change may land on the wrong task.
Need help

Need help automating Neaktor with Make?

A person reads every message.

FAQ

Neaktor and Make: common questions

01Is the Neaktor Make integration free?
Yes, on the Make side. Neaktor is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per run and files up to 5 MB. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios. Your Neaktor subscription is separate and depends on Neaktor's own pricing.
02What does it take to connect Neaktor to Make?
You need an active Neaktor account and an OAuth2 API key. In Neaktor, go to Integrations, then API keys, generate a new key with the OAuth2 keychain option, set its status to Read and write, and copy the Client ID and Client secret. In Make, click Create a connection on any Neaktor module and paste those two values. The connection is then reused by every Neaktor module in your scenarios.
03Does Watch Tasks react in real time?
No. Watch Tasks is a scheduled trigger: Make checks Neaktor on the scenario's schedule rather than being alerted the moment something changes. A new scenario checks every 15 minutes by default. On a paid plan you can bring that down to 1 minute, while the Free plan keeps at least 15 minutes between runs. Each check counts operations, so a shorter schedule uses more of your plan. Set the schedule by clicking the clock on the first module.
04What if a Neaktor module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Neaktor API with the connection you already set up, so you are not limited to the seven listed modules and never need a second account link. Build the request from the Neaktor API documentation and test it with Run once. The official app documentation also warns that it may contain mistakes, so confirm important details with Neaktor directly before you build on them.
05Is Make or n8n better for Neaktor?
It depends on the tool your team already works in. Make offers Neaktor as a standard app with six modules built around tasks, plus Make an API Call for the rest. n8n often has a node for the same app, so check what it offers for Neaktor before deciding. Compare the actions each one exposes against the tasks you actually want to automate, and pick the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations