Resources · Make integration

Aidbase Make integrationAutomate Aidbase with Make.

Your support tickets can feed your chatbot's knowledge on their own. The Aidbase Make integration gives you 14 modules: 8 triggers on tickets and emails, 6 actions on FAQs, sources and replies. This guide connects your account and walks you through a first scenario.

Try the Aidbase integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Aidbase Make integration automate?

The Aidbase Make integration links your Aidbase account to Make, a no-code tool where you build a scenario, meaning the automation itself: a chain of modules, each one a brick that watches, adds or reads something in one app. Here, Make watches your tickets and support emails and can add content to what your chatbot knows.

A help center that grows from solved tickets. Watch Ticket Status notices a ticket moving to a new status, and Add FAQ Item turns the answer your agent wrote into a new entry. The next customer with the same question gets it from the bot.

An escalation lane for urgent mail. Watch Email Priority reacts when an email is flagged as more important, and the next module can alert whoever is on duty in your chat tool or your task board.

Fresh sources for the bot. When your marketing team publishes a page or a tutorial, Add Website and Add Video hand it to Aidbase so the chatbot can draw on it.

Know the limits before you start. Judging by their names, all 8 triggers are scheduled, so none fires the moment something happens, and there is no Make an API Call module for this app. Make's own directory gave no description for these modules; the notes below lean on their names and on the Aidbase doc, which itself warns that it is AI-generated. To weigh the two tools, read our n8n vs Make comparison, and the Make pricing page explains how plans count usage.

Connect

How do you connect Aidbase to Make?

  1. 01

    Create an API key in Aidbase

    In Aidbase, open Settings from your account menu, then API Keys, and click Create new API Key. Give it a name you will recognize later, pick the permissions it needs, and click Copy.

  2. 02

    Add an Aidbase module in Make

    Open your scenario in Make, add any Aidbase module and click Create a connection. A connection is your Aidbase account linked to Make once, then reused by every Aidbase module you add afterwards.

  3. 03

    Paste the key and save

    The Connection name field is optional, but a clear label helps when you manage several accounts. Paste the key you copied into the credentials field, confirm, and Make can now read and write in your Aidbase workspace.

First scenario

Your first scenario: turn solved tickets into FAQ entries

GoalWhen a ticket changes status in Aidbase, Make adds an FAQ item so the chatbot can reuse the answer.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the big + in the middle of the canvas to place your first module.

  2. 02

    Pick the ticket trigger

    Search for Aidbase, choose Watch Ticket Status and click Create a connection with the API key you prepared. Then fill the fields Make shows for the module.

  3. 03

    Add the FAQ action

    Click the + on the right of the trigger and pick Add FAQ Item. Map the data the trigger returns into the fields Make shows. Run the trigger alone first to see what a ticket carries.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time, then open the bubbles to read each bundle, one item passed from a module to the next. The test adds a real FAQ item, so check it in Aidbase.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep that or change it within your plan, then switch the scenario on.

Triggers

Which Aidbase triggers can start a scenario?

8 modules start a scenario when something happens in Aidbase. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Aidbase as soon as it happens.

Aidbase1Watch Email Priority

Watch Email Priority

triggerIn the docs only

This trigger picks up support emails whose priority has changed in Aidbase, which gives you a way to act on the messages your team flagged as important instead of reading the whole inbox again.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule and starts the run on the next check.
When to use it
send an alert to the person on call when an email gets bumped up.
Watch out
Make lists this module without a description, so run it once on a test email to see what it returns.
Aidbase2Watch Email Received

Watch Email Received

triggerIn the docs only

Every incoming support email becomes a starting point with this module: once Aidbase has the message, your scenario can copy it, log it or pass it to another tool your team already uses.

How it fires
scheduled; Make asks Aidbase for new emails each time the scenario's clock comes round, not the second the email lands.
When to use it
keep a shared spreadsheet of inbound requests that your support lead can sort and review.
Watch out
on the Free plan the shortest gap between checks is 15 minutes, so plan your reply promises accordingly.
Aidbase3Watch Email Sent

Watch Email Sent

triggerIn the docs only

Going by its name, this one looks at the other side of the conversation: the emails that left Aidbase. It helps you track what your team or your bot actually answered, not only what customers asked.

How it fires
Make checks the app on the scenario's schedule, which makes it a scheduled trigger; look for the clock badge on the module.
When to use it
copy each outgoing reply into your CRM so sales sees the full history of an account.
Watch out
the official directory gives no detail about this module, so confirm with Run once which emails it catches.
Aidbase4Watch Email Status

Watch Email Status

triggerIn the docs only

Status moves on an email are the signal here. Pick this trigger when you care about where a message stands in your process rather than about new arrivals or priority changes.

How it fires
it runs on the scenario's schedule; Make polls Aidbase and only sees a change on its next pass.
When to use it
close the matching task in your project tool when an email is marked as handled.
Watch out
the Free plan keeps 2 scenarios active at once, so splitting every email trigger into its own scenario fills that quota quickly.
Aidbase5Watch New Ticket

Watch New Ticket

triggerIn the docs only

A fresh ticket in Aidbase is what this module waits for. It is the natural entry point when you want the rest of your stack to know that a customer opened a request.

How it fires
scheduled. Make looks for new tickets at each interval you set on the first module.
When to use it
post new tickets into the support channel of your team chat so nobody has to keep Aidbase open.
Watch out
each bundle, meaning each ticket the trigger returns, goes through the following modules, and every module run counts as an operation on your Make plan.
Aidbase6Watch New Ticket Comment

Watch New Ticket Comment

triggerIn the docs only

Conversations inside a ticket keep moving, and this trigger follows them: when someone adds a comment, the scenario can pick it up and carry it wherever the follow-up happens.

How it fires
Make checks the app on the scenario's schedule, so a comment waits for the next check before anything runs.
When to use it
notify the account manager when a customer replies on a ticket about their contract.
Watch out
Make has no description for this module, so test on a ticket with a known comment and read the bundle before building on it.
Aidbase7Watch Ticket Priority

Watch Ticket Priority

triggerIn the docs only

This is the ticket twin of the email priority trigger. It lets you react when a ticket climbs or drops in importance, so urgent cases get a different path from routine ones.

How it fires
scheduled; Make polls Aidbase at the interval of the scenario, 15 minutes by default on a new one.
When to use it
open an incident card on your team board when a ticket is raised to the top priority.
Watch out
paid plans let you check as often as every minute; on Free, a raised ticket can wait up to the full interval.
Aidbase8Watch Ticket Status

Watch Ticket Status

triggerIn the docs only

Ticket status changes, such as a case being solved or reopened, start your scenario with this module. That makes it the best hook for anything that should happen after a ticket is closed.

How it fires
Make checks the app on the scenario's schedule and picks up the status changes since its last visit.
When to use it
feed solved tickets into Add FAQ Item, as in the first scenario above.
Watch out
nothing in the doc lists the statuses it reports, so check the first bundles before adding a filter on a specific status.
Modules

What can Make do in Aidbase?

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

Aidbase1

Add FAQ Item

ActionIn the docs only

Add FAQ Item writes a new question and answer into Aidbase, so your chatbot has one more entry to draw from without anyone opening the FAQ editor.

When to use it
right after a ticket trigger, to turn a good agent answer into knowledge the bot can reuse.
Watch out
Run once creates a real item, so tidy up the test entry afterwards.
Aidbase2

Add Video

ActionIn the docs only

With Add Video, a video you publish elsewhere can become part of what Aidbase knows, which saves copying links by hand every time your team records a tutorial.

When to use it
when a new product walkthrough goes live on your video channel and the bot should point customers to it.
Watch out
the directory gives no detail on accepted sources, so test with one video first.
Aidbase3

Add Website

ActionIn the docs only

Pages from your site reach the chatbot through this action: it hands a website to Aidbase as a source, so answers can reflect what you actually published.

When to use it
after a new help article or pricing page goes live, triggered by your CMS or a form.
Watch out
the module has no official description; read the result of Run once before relying on it in production.
Aidbase4

Create Chatbot Reply

ActionIn the docs only

Create Chatbot Reply asks your Aidbase bot for an answer from inside a scenario, which lets another tool, such as a form or a chat app, benefit from the knowledge you built.

When to use it
a question arrives through a web form and you want a first draft answer before a human looks at it.
Watch out
review what the bot returns before sending it to a customer automatically.
Aidbase5

Get Chatbots

ActionIn the docs only

Get Chatbots reads the bots set up in your Aidbase account, handy when the next module needs to know which chatbot to address and you run more than one.

When to use it
ahead of Create Chatbot Reply, when your scenario chooses the bot by brand or by language.
Watch out
Make classes it as an action, not a search, so check with Run once how many bundles it returns.
Aidbase6

Get FAQs

ActionIn the docs only

Get FAQs pulls the FAQ content stored in Aidbase back into Make, so you can review it, export it or compare it with what support is answering today.

When to use it
to copy your FAQ into a spreadsheet the content team can audit, or to avoid adding a duplicate entry.
Watch out
each item that passes to the next module costs an operation, so a large FAQ adds up.
Need help

Need help automating Aidbase with Make?

A person reads every message.

FAQ

Questions about the Aidbase Make integration

01Is the Aidbase Make integration free?
Yes, on Make's side. Aidbase is a standard app, available from the Free plan, like the 3000+ standard apps on every plan. The Free plan keeps 2 scenarios active, waits at least 15 minutes between scheduled runs, caps a run at 5 minutes and allows 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift those limits and count usage in credits each month. You still need an active Aidbase subscription; see the Aidbase pricing page for that part, since Make does not cover it.
02What do you need to connect Aidbase to Make?
An active Aidbase account and a valid bearer token, which Aidbase calls an API key. You create it in Settings, then API Keys, then Create new API Key: name it, choose its permissions and copy it. In Make, add any Aidbase module, click Create a connection, optionally fill the Connection name field and paste the key. That single connection then serves all 14 Aidbase modules in every scenario you build, so there is nothing to redo per module.
03Do Aidbase triggers fire instantly in Make?
Most likely not. Make's directory does not describe them, but their names mark all 8 Aidbase triggers as scheduled: Make checks Aidbase on the scenario's schedule instead of being called the moment a ticket or email changes. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. If speed matters, run the scenario on a paid plan with a short interval, and keep in mind that each module run on each bundle counts as an operation.
04What if the Aidbase Make integration lacks a module you need?
It depends on the gap. Aidbase has no Make an API Call module in Make, so you cannot fall back on a generic request from the Aidbase app itself. The 14 modules cover ticket and email triggers plus actions on FAQs, websites, videos and chatbot replies. For anything else, handle that step in another app of your scenario, or ask the team behind this page to look at your case. The Aidbase doc also warns it is AI-generated, so check behaviour with Run once.
05Should you use Make or n8n with Aidbase?
It depends on your criteria rather than on the app. On Make, Aidbase comes with 14 ready modules, 8 of them scheduled triggers, a connection based on one API key and a visual editor with Run once for testing. Many apps also have an n8n node, so check whether one exists for Aidbase and what it covers before choosing. Compare the modules each tool offers for your exact scenario, how each counts usage, and which editor your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations