Resources · Make integration

Maybe* Your AI Make integrationAutomate Maybe* Your AI with Make.

Can Make keep your Maybe* Your AI workspace in sync with the rest of your tools? Yes: the Maybe* Your AI Make integration offers 30 action modules for tasks, users, chats and memories. This page shows how to link your account and build a first scenario, step by step.

Try the Maybe* Your AI integration on MakeSee the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Maybe* Your AI Make integration automate?

The Maybe* Your AI Make integration links your Maybe* Your AI account to Make, a no-code tool where you chain apps into automations. You get 30 action modules to create, read, update and delete tasks, users, chats and memories, plus image generation. There is no trigger, so a schedule or another app starts each run.

Tasks that come from outside. A form reply, a new deal or a support ticket arrives in another app, and Create Task files it in Maybe* Your AI. Add Create Task Category first when a new client needs its own category.

A team list that stays current. When someone joins or leaves in your HR tool, Create User, Update User and Delete User mirror the change, while Get Users lets you check nobody is added twice.

Knowledge the AI can reuse. A PDF saved in cloud storage goes in with Upload File to Memory, and a customer detail from your CRM becomes an entry with Add a Memory. Get Memory reads it back when another tool needs it.

What Make cannot do here: react on its own to something happening in Maybe* Your AI, because the app has no trigger. Make's page for the app also warns that its documentation was generated by AI, so check labels against the vendor's screens. For a wider view of the platform, read our Make review, see Make pricing before you pick a plan, and compare both tools in n8n vs Make if you also run n8n.

Connect

How do you connect Maybe* Your AI to Make?

  1. 01

    Create an API key in Maybe* Your AI

    In your Maybe* Your AI account, open Settings, then Integrations. In the Create API Key section, click Create and copy the key displayed on screen. Your account has to be active at the workspace level.

  2. 02

    Open a connection from a module

    In a Make scenario, add any Maybe* Your AI module and click Create a connection. A connection is your account linked to Make once and reused by every module of the app. Filling Connection name is optional but helps if you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied into the window Make opens, or follow the on-screen instructions if they differ. Save, and the connection shows up in the module. From then on, you just select it in every other Maybe* Your AI module.

First scenario

Build your first scenario with Maybe* Your AI

GoalWhen a new request comes in through another app, Make creates a task in Maybe* Your AI.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario, the automation you build in Make. Click the + and add the first module from the app where requests arrive, such as your form tool.

  2. 02

    Add Create Task

    Click the + on the right of that first module, search for Maybe* Your AI and pick Create Task. Select your connection, or click Create a connection if this is your first module of the app.

  3. 03

    Map the request into the task

    Fill the fields the module shows by picking data from the first module. Each request travels as a bundle, one item passed from module to module, and each bundle becomes one task.

  4. 04

    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, then check in Maybe* Your AI that the task is there.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Keep it or pick another schedule, then switch the scenario on.

Modules

What the 30 Maybe* Your AI modules do

Maybe* Your AI gives you 30 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Maybe* Your AI1

Add a Memory

ActionIn the docs only

Add a Memory saves a new piece of information in your Maybe* Your AI memory straight from a scenario, so nobody has to type it in.

When to use it
a customer detail lands in your CRM and the AI side should keep it for later exchanges.
Watch out
one bundle gives one memory, so a module that sends several rows creates several entries and uses one operation each.
Maybe* Your AI2

Add to Favourites

ActionIn the docs only

This module marks an item as a favourite in Maybe* Your AI, which helps the right content stand out when your team opens the app.

When to use it
a chat or an answer gets approved somewhere else and should be easy to find again.
Watch out
the documentation does not say which items accept a favourite, so try it on one test item with Run once first.
Maybe* Your AI3

Create Conversation

ActionIn the docs only

Create Conversation opens a fresh conversation in Maybe* Your AI from data your scenario already holds, such as a customer's question.

When to use it
a support request arrives in your helpdesk and deserves its own thread on the AI side.
Watch out
if the previous module passes several items, you get one conversation per item, not one conversation for the batch.
Maybe* Your AI4

Create Post

ActionIn the docs only

With Create Post, your scenario publishes a post inside Maybe* Your AI instead of someone pasting the text by hand.

When to use it
a text gets approved in a spreadsheet or a project tool and should land in Maybe* Your AI without copy and paste.
Watch out
the module acts the moment it runs, so test it on harmless text before mapping real content.
Maybe* Your AI5

Create Task

ActionIn the docs only

Create Task turns an incoming request into a task in Maybe* Your AI, so it stops waiting in an inbox. It's the module of the first scenario on this page.

When to use it
a form reply, a new deal or a ticket from another app should become a to-do for the team.
Watch out
every bundle the previous module sends becomes a task, duplicates included.
Maybe* Your AI6

Create Task Category

ActionIn the docs only

This one adds a task category to your Maybe* Your AI account, a way to sort tasks by client, project or team.

When to use it
a new client or project appears in your CRM and should get its own category before any task arrives.
Watch out
place it before Create Task in the scenario; otherwise the task comes in before its category exists.
Maybe* Your AI7

Create User

ActionIn the docs only

Create User adds a person to your Maybe* Your AI workspace from a scenario, without a trip to the settings screen.

When to use it
someone joins the team in your HR tool or directory and needs access to Maybe* Your AI too.
Watch out
check with Get Users that the person isn't already there, or a second run may add them twice.
Maybe* Your AI8

Create a Chat

ActionIn the docs only

Create a Chat starts a chat in Maybe* Your AI that you can later read back with Get All Chats.

When to use it
each new lead or ticket should get its own AI chat.
Watch out
its name sits close to Create Conversation and the documentation doesn't separate the two. Run both once on the same test bundle and keep the one whose result matches what you expect in the app.
Maybe* Your AI9

Delete Chat

ActionIn the docs only

Delete Chat removes a chat from Maybe* Your AI, which keeps old or test exchanges from piling up.

When to use it
a customer asks you to erase their exchanges, or test chats accumulate while you build.
Watch out
treat the deletion as final. Find the right chat with Get All Chats first and try the module on a single test chat.
Maybe* Your AI10

Delete Memory

ActionIn the docs only

When information stored in Maybe* Your AI turns wrong or has to disappear, Delete Memory takes it out from within the scenario.

When to use it
a contact closes their account in your CRM and what the AI remembers about them should go as well.
Watch out
pair it with Get Memory so you know exactly which entry you target, and treat the deletion as final: try it on a test entry first.
Maybe* Your AI11

Delete Task

ActionIn the docs only

Delete Task clears a task out of Maybe* Your AI once it has no reason to exist, which keeps the list readable.

When to use it
a deal is lost or an order cancelled in another app, and the matching task would only clutter things.
Watch out
you need the right task first, so put Get Tasks or Get Task by ID before it and test on a dummy task.
Maybe* Your AI12

Delete Task Category

ActionIn the docs only

This module removes a whole task category from your Maybe* Your AI account, not just one task.

When to use it
a project ends and its category has nothing left to hold.
Watch out
the documentation says nothing about tasks still filed under the category. Look at them with Get Tasks before you run it, and move what you want to keep.
Maybe* Your AI13

Delete User

ActionIn the docs only

Delete User takes a person out of your Maybe* Your AI workspace directly from Make, so offboarding doesn't depend on someone remembering it.

When to use it
a colleague leaves in your HR tool and their access should close too.
Watch out
this is the module to handle with most care. Put Get User by ID in front of it to confirm who you're about to remove.
Maybe* Your AI14

Generate Image

ActionIn the docs only

Generate Image asks Maybe* Your AI for a picture and hands the result to the next module of your scenario.

When to use it
a product or an article is added in another tool and needs a first visual to review.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of what comes back before you send it to storage.
Maybe* Your AI15

Get Account

ActionIn the docs only

Get Account reads the details of your Maybe* Your AI account and passes them on as a bundle the next modules can use.

When to use it
you want to confirm the connection works before a longer build, or a later step needs account information.
Watch out
it only reads. To change anything, Update Account is the module you need.
Maybe* Your AI16

Get All Chats

ActionIn the docs only

This module fetches the chats stored in your Maybe* Your AI account so the rest of the scenario can work on them.

When to use it
an export of chats to a spreadsheet, or spotting the chat you plan to remove with Delete Chat.
Watch out
if Run once shows several bundles, every module placed after it runs once per chat, and each run counts as an operation.
Maybe* Your AI17

Get Assistants

ActionIn the docs only

Get Assistants lists the assistants set up in Maybe* Your AI, so your scenario knows what exists before acting.

When to use it
your account has several assistants and a later step of the scenario should work with the right one.
Watch out
the documentation doesn't describe what each returned item contains; read the bundle in Run once before you map anything from it.
Maybe* Your AI18

Get Memory

ActionIn the docs only

Get Memory reads back what Maybe* Your AI has stored, so another tool can put it to use.

When to use it
copying stored information into a CRM or a document, or checking an entry before Update Memory or Delete Memory touches it.
Watch out
look at the result in Run once first; what the module returns decides what you can map in the following steps.
Maybe* Your AI19

Get Task Categories

ActionIn the docs only

Get Task Categories returns the categories already set up in your Maybe* Your AI account.

When to use it
right before Create Task, to file new tasks in an existing category instead of inventing a new one on every run.
Watch out
if the category you expect isn't in the result, add Create Task Category to the scenario rather than guessing a value.
Maybe* Your AI20

Get Task by ID

ActionIn the docs only

When you already hold a task's identifier, Get Task by ID fetches that single task and nothing else.

When to use it
an earlier module or another app stored the ID, and you need the current state of the task before acting on it.
Watch out
with an empty or wrong ID the module has nothing to return, so map the ID from a bundle instead of typing it.
Maybe* Your AI21

Get Tasks

ActionIn the docs only

Get Tasks pulls your Maybe* Your AI tasks into the scenario, ready to be copied elsewhere or acted on.

When to use it
a task report in a spreadsheet, or a cleanup pass with Update Task or Delete Task.
Watch out
many tasks mean many bundles, and the modules after it multiply operations accordingly; test on a small account before you switch the scenario on.
Maybe* Your AI22

Get User by ID

ActionIn the docs only

Get User by ID looks up one person in Maybe* Your AI from the identifier you give it.

When to use it
before Update User or Delete User, to be sure you're about to change the right person.
Watch out
the ID can come from Get Users or from Create User earlier in the scenario; map it rather than pasting a fixed value that will go stale.
Maybe* Your AI23

Get Users

ActionIn the docs only

Get Users brings the people of your Maybe* Your AI workspace into Make, one bundle per person in the Run once view.

When to use it
comparing the list with your HR tool, or checking before Create User that nobody gets added twice.
Watch out
reading the list is harmless, but whatever you place after it acts on every user it returns.
Maybe* Your AI24

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Maybe* Your AI API with the connection you already set up, no second login needed.

When to use it
none of the other modules covers the action you need.
Watch out
here you work with the API directly, so keep the vendor's API reference at hand. Make's page for this app says its content was generated by AI, so verify endpoints with Maybe* Your AI.
Maybe* Your AI25

Update Account

ActionIn the docs only

Update Account changes the settings of your Maybe* Your AI account from a scenario instead of the settings screen.

When to use it
company information changes in your main tool and the account should follow.
Watch out
an update replaces the values you map. Read them with Get Account first so you know what you are about to overwrite.
Maybe* Your AI26

Update Memory

ActionIn the docs only

Rather than deleting and adding again, Update Memory corrects an entry Maybe* Your AI already keeps.

When to use it
a customer changes role or company in your CRM, and the AI should stop relying on the old detail.
Watch out
it needs the right entry. Find it with Get Memory in the same scenario and map it from there.
Maybe* Your AI27

Update Task

ActionIn the docs only

Update Task edits a task that already exists in Maybe* Your AI, so it reflects what changed elsewhere.

When to use it
a ticket closes in your helpdesk or a deal moves forward, and the matching task should keep up.
Watch out
keep the task ID from Create Task somewhere; without it, you need an extra Get Tasks step to find the task again.
Maybe* Your AI28

Update Task Category

ActionIn the docs only

Renaming or adjusting an existing category is the job of Update Task Category, with no need to rebuild it.

When to use it
a project or client gets renamed in your project tool and the category should carry the new name.
Watch out
confirm the category with Get Task Categories before running it, since the update lands on whatever category you map.
Maybe* Your AI29

Update User

ActionIn the docs only

Update User keeps a person's profile in Maybe* Your AI in line with the rest of your tools.

When to use it
someone changes team or name in your directory and Maybe* Your AI should show the same thing.
Watch out
map the user's ID from Get Users or Get User by ID; a typed ID breaks the day that person is replaced.
Maybe* Your AI30

Upload File to Memory

ActionIn the docs only

Upload File to Memory sends a file into the memory of Maybe* Your AI, so documents from other tools join what it keeps.

When to use it
a PDF lands in your cloud storage and should become reference material on the AI side.
Watch out
on the Free plan Make caps files at 5 MB and data transfer at 512 MB, so check sizes before you build around large documents.
Need help

Need help automating Maybe* Your AI with Make?

A person reads every message.

FAQ

Maybe* Your AI and Make: common questions

01Is the Maybe* Your AI Make integration free?
Yes, on Make's side. Maybe* Your AI is a standard app, available from the Free plan, so you can build with its 30 modules without paying Make. The Free plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Your Maybe* Your AI subscription is a separate matter: see the vendor's pricing page.
02What does connecting Maybe* Your AI to Make require?
Two things: an active Maybe* Your AI account at the workspace level, and an API key. You create the key in Maybe* Your AI under Settings, then Integrations, with the Create button of the Create API Key section, and you copy it. In Make, add any module of the app, click Create a connection, name it if you like and paste the key. That single connection then serves all 30 modules, including Make an API Call.
03Does Maybe* Your AI start a Make scenario instantly?
No. The app has no trigger in Make, neither scheduled nor instant, so nothing in Maybe* Your AI can start a scenario by itself. Two options remain. You can start the scenario on a schedule: a new one runs every 15 minutes by default, 15 minutes is also the shortest interval on the Free plan, and paid plans go down to 1 minute. Or you can open the scenario with a trigger from another app, a form or a CRM for instance, and place the Maybe* Your AI modules after it.
04What if a Maybe* Your AI module is missing in Make?
Use Make an API Call. It calls any endpoint of the Maybe* Your AI API with the connection you already have, so it covers what the 30 listed modules don't. You'll need the vendor's API reference to fill it in. Keep in mind that Make's page for this app was generated by AI and warns it may contain mistakes, so double-check endpoints and labels with Maybe* Your AI directly before relying on them.
05Make or n8n for Maybe* Your AI?
It depends on the tool your team already runs. In Make, Maybe* Your AI comes with 30 ready modules plus Make an API Call, one connection shared by all of them, and it works from the Free plan. The same app often has an n8n node, but that isn't confirmed for Maybe* Your AI here, so look for it in n8n before deciding. If both exist, compare what each side covers for your actual need (tasks, users, memories) and pick the tool you'll maintain. On the Make side, remember that a schedule or another app has to start each scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations