Resources · Make integration

aiKonnector Human Approvals Make integrationAutomate aiKonnector Human Approvals with Make.

Need a human to say yes before an automation goes further? The aiKonnector Human Approvals Make integration gives you 4 action modules, no trigger. This guide shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the aiKonnector Human Approvals Make integration do?

The aiKonnector Human Approvals Make integration lets a Make scenario (the automation you build, a chain of modules) hand an item to a person for review through your aiKonnector account. You get 4 modules, all actions, which create approval requests, look up items, update them or call the API directly.

Send a request for review. A lead arrives from a form, an invoice lands in a shared inbox, a generated text is ready: the module Create a human approval request passes it to aiKonnector, where your queue holds it for a person to look at. Each module is one brick of the scenario, and this one is usually the brick that sits right after the event you want someone to check.

Keep items up to date. Once a request exists, Item search and Update human approval item let a later scenario find it again and change it. The exact fields each module shows are not described in the Make documentation, so open the module and read what Make lists once your connection is set.

Reach what the modules do not cover. Make an API Call sends any request of the aiKonnector API with the same connection, which is the way out when none of the listed modules fits.

What this app does not offer: a trigger. Nothing in the app starts a scenario on its own, so the flow opens on another app or on a schedule. Keep in mind too that the Make documentation for this app says its content is AI-generated and may hold mistakes. If something behaves differently from what you expect, the Make troubleshooting page is a good first stop. The same app may also exist as an n8n node; the n8n vs Make comparison helps you pick a tool, and Make training covers the editor from scratch.

Connect

How do you connect aiKonnector Human Approvals to Make?

  1. 01

    Copy your API key

    Log in to aiKonnector, open your account dashboard, then the API section or API keys panel, and copy the key shown on screen. You also need an active account and a queue already created on the aiKonnector side.

  2. 02

    Add a module and create the connection

    In your scenario, add any aiKonnector Human Approvals module and click Create a connection. A connection is your aiKonnector account linked to Make once, then reused by every module of this app.

  3. 03

    Name it and paste the key

    The Connection name field is optional. Still, a clear name saves you from mixing things up the day you run several aiKonnector accounts in the same Make organization. Paste the credentials you copied, or follow the on-screen instructions, then save.

First scenario

Your first scenario with aiKonnector Human Approvals

GoalWhen a new entry arrives in another app, Make sends it to aiKonnector Human Approvals as a request that waits for a person.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. That first module comes from the app where your items start, a form tool or a CRM for instance.

  2. 02

    Set the starting module

    Search that app by name, pick the module that watches new entries, click Create a connection and fill its fields. It hands each new entry to the next module as a bundle, one item at a time.

  3. 03

    Add the approval request

    Click the + on the right, search aiKonnector Human Approvals and choose Create a human approval request. Connect your account, then map the data coming from the first module into the fields Make lists.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, then check your aiKonnector queue for the new request.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What the aiKonnector Human Approvals modules do

aiKonnector Human Approvals gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

aiKonnector Human Approvals1

Create a human approval request

ActionIn the docs only

This is how an item leaves your automation and reaches a person: the module sends a new approval request to aiKonnector, where your queue holds it for review. It is the entry point of most scenarios built on this app.

When to use it
right after the event that needs a human check, such as a quote drafted by AI or a refund asked through a form.
Watch out
the request lands in a queue, so create that queue in aiKonnector before your first test.
aiKonnector Human Approvals3

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the aiKonnector API from your scenario, using the connection you already set up. No new login, no separate key to paste.

When to use it
the three other modules do not cover what you need, and the aiKonnector API has an endpoint for it.
Watch out
you write the request yourself here, so test it with Run once and read what comes back before you map anything.
aiKonnector Human Approvals4

Update human approval item

ActionIn the docs only

Changing a request that already sits in aiKonnector is the job of this module, so the item keeps up with what happens elsewhere in your tools. It acts on one existing item per bundle.

When to use it
the source record changed after the request went out, and the reviewer should see the new version.
Watch out
it needs to know which item to change, so place Item search or another source of the item reference before it.
Need help

Need help automating aiKonnector Human Approvals with Make?

A person reads every message.

FAQ

Questions about the aiKonnector Human Approvals Make integration

01Is the aiKonnector Human Approvals Make integration free?
Yes on the Make side: it is a standard app, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 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, Enterprise) drop the interval to 1 minute and count usage in credits per month. On the aiKonnector side you need an active account; its own subscription terms are on the aiKonnector pricing page, which this guide does not cover.
02What do you need to connect aiKonnector Human Approvals to Make?
Three things, all on the aiKonnector side: an active account, a queue already created, and an API key. You find the key in your account dashboard, under the API section or API keys panel, and copy it from the screen. In Make, you add any module of the app, click Create a connection, optionally give it a name, then paste the credentials. The connection is saved once and every module of the app reuses it afterwards.
03Can aiKonnector Human Approvals start a Make scenario on its own?
No, the app has no trigger module in Make, only 4 actions. A scenario that uses it has to start somewhere else: on a trigger from another app, such as a new form entry or a new CRM record, or on the schedule of the first module, which runs every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. The aiKonnector modules then sit after that starting point.
04What if a module is missing in the aiKonnector Human Approvals Make integration?
Use Make an API Call. It is part of this app and calls any endpoint of the aiKonnector API with the connection you already created, so you can cover an operation the three other modules leave out. You write the request yourself, so test it with Run once before you rely on it. Also note that the Make documentation for this app is flagged as AI-generated and may contain mistakes; when a detail matters, confirm it with aiKonnector directly.
05Should you use Make or n8n with aiKonnector Human Approvals?
It depends on the tool your team already runs. On Make, the app gives you 4 action modules plus a connection saved once, and the scenario editor lets you test each step with Run once before you switch anything on. The same app often exists as an n8n node too, so check the n8n side if that is where your automations live. Pick the tool your team already knows and maintains, and compare how each one fits the rest of your stack.