Automate MyAgentX With Make: 3 Modules, No Code, Quick Start

What you can automate

What can the MyAgentX Make integration do for you?

The MyAgentX Make integration links your MyAgentX account to Make so leads move between MyAgentX and your other tools on their own. In Make you build a scenario, the automation itself, out of modules: each module is one brick, such as a trigger that starts things or an action that does the work.

New leads land in MyAgentX by themselves. A contact form, a spreadsheet row or a signup in another app opens the scenario, and Create a Lead adds that person to MyAgentX. Nobody retypes a name from an inbox.

A stage change tells the rest of the team. Watch Updated Lead Stage picks up leads whose stage changed, and the next module passes the news on: a chat message, a row in a tracking sheet, a task for the account manager.

Anything the two actions miss stays reachable. Make an API Call calls any endpoint of the MyAgentX API with the same connection, so an unusual request does not force you out of Make.

Know the limit before you start: the official Make documentation for MyAgentX is marked as limited, because little public information exists about the app. Expect to test each module with Run once rather than rely on a detailed reference. The Make troubleshooting guide helps when a run fails. If you still hesitate between tools, read n8n vs Make, and check Make pricing before you plan several active scenarios.

Connect

How do you connect MyAgentX to Make?

01
Open the connection window
Add any MyAgentX module to a scenario, then click Create a connection. A connection is your MyAgentX account linked to Make once, and every MyAgentX module in your scenarios reuses it.
02
Name it and authorize Make
Give the connection a name if you like, such as the workspace it belongs to. Then do what MyAgentX asks: approve Make on the MyAgentX page that opens, or paste the key the app gives you.
03
Save and check
Click Save. Back in the module, Make can now read your MyAgentX data, so the fields that expect a choice show what your account holds instead of an empty box.

First scenario

Build your first scenario with MyAgentX

GoalWhen someone fills in a form in another app, Make creates a lead in MyAgentX.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big +. That first module is what starts everything, here the form app your prospects already use.
02
Set up the starting module
Search for your form app, pick its module for new responses and connect your account. Make then lists the forms it can read, so you choose one instead of typing an ID.
03
Add Create a Lead
Click the + on the right of the form module, search MyAgentX and pick Create a Lead. Use Create a connection if this is your first MyAgentX module.
04
Map the answers
Fill the lead fields with the answers the form module passes on. Each response travels as one bundle, the single item that flows from one module to the next.
05
Test with Run once
Submit a test answer, then click Run once. Open the bubble above each module to read the bundles it received and confirm the lead appears in MyAgentX.
06
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

What starts a MyAgentX scenario

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

MyAgentX1Watch Updated Lead Stage

Watch Updated Lead Stage

triggerIn the docs only

This trigger hands your scenario the leads whose stage changed in MyAgentX, so the next steps run on exactly the people who moved.

How it fires

Make checks the app on the scenario's schedule. The docs give no type, so this reading comes from the module's name: look for the clock badge of a scheduled trigger when you add it.

When to use it

a lead reaches a stage where someone else takes over, and that person should hear about it without opening MyAgentX.

Watch out

a scheduled trigger only reports changes at each check, so leave the test lead in its new stage until Run once has read it.

Modules

What MyAgentX can do in a scenario

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

MyAgentX1

Create a Lead

ActionIn the docs only

Create a Lead turns data from any earlier module into a new lead in MyAgentX, so people who reach you elsewhere show up in your pipeline.

When to use it

a prospect fills a form, books a call or lands in a spreadsheet, and that contact should exist in MyAgentX right away.

Watch out

nothing in the docs says the module looks for an existing lead first, so expect one new lead per bundle, duplicates included.

MyAgentX2

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the MyAgentX API through your existing connection, which covers what the two listed modules leave out.

When to use it

you need a MyAgentX request that neither Create a Lead nor the stage trigger offers, and you know which endpoint to call.

Watch out

the Make docs for MyAgentX are limited, so confirm with MyAgentX which request to send and test the call with Run once.

Need help

Need help automating MyAgentX with Make?

A person reads every message.

FAQ

Questions about MyAgentX and Make

01Is the MyAgentX Make integration free?

Yes, MyAgentX is a standard app, so you can use it on the Make Free plan. That plan has real limits: 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 and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle.

02What do you need to connect MyAgentX to Make?

You need a MyAgentX account and a Make account. The Make documentation lists no prerequisite and no MyAgentX-specific steps, so the generic flow applies: add a MyAgentX module, click Create a connection, name it if you want, authorize Make on the MyAgentX page or paste the key MyAgentX provides, then click Save. Every MyAgentX module in your scenarios reuses that one connection afterwards. If a module still shows empty choices, the connection is usually the first thing to recheck.

03Does the MyAgentX trigger fire in real time?

No, as far as the available information goes. Watch Updated Lead Stage is listed as a scheduled trigger, a type inferred from its name because the docs describe nothing more. Make checks MyAgentX on the scenario's schedule, every 15 minutes by default. The Free plan cannot go below 15 minutes, and paid plans can go down to 1 minute. A lead that changes stage waits until the next check. For an urgent handoff, keep that delay in mind when you pick your plan.

04What if the MyAgentX module you need is missing in Make?

It depends on the request, but Make an API Call usually covers it. The module calls any endpoint of the MyAgentX API with the connection you already have, so you are not limited to Create a Lead and the stage trigger. Keep in mind that Make itself flags its MyAgentX documentation as limited, so the endpoint details come from MyAgentX. Test each new call with Run once before you switch the scenario on.

05Should you use Make or n8n for MyAgentX?

It depends on what each tool offers for MyAgentX on the day you build. In Make, you get 3 modules: a scheduled trigger on lead stages, Create a Lead and Make an API Call for the rest. Many apps also have an n8n node, so check whether MyAgentX has one and which operations it lists. Compare on that list and on the tool your team already runs, rather than on reputation.

Open the connection window

Name it and authorize Make

Save and check

Create the scenario

Set up the starting module

Add Create a Lead

Map the answers

Test with Run once

Schedule and switch on

Need help automating MyAgentX with Make?