Resources · Make integration

Agendor Make integrationAutomate Agendor with Make.

Can Make keep your Agendor CRM up to date on its own? Yes. The Agendor Make integration gives you 33 modules, 22 actions and 11 searches, to create deals, contacts and tasks from your other apps. This guide connects your account and builds a first scenario with you.

Try the Agendor integration on Make See the 33 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Agendor Make integration do for your sales team?

The Agendor Make integration links your Agendor CRM to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules where each module is one step handled by one app. Agendor brings 33 modules to that chain. They create, update and search people, organizations, deals, tasks and products whenever another app or a schedule hands them data.

Every inbound lead lands in the CRM. A web form sends a new contact, Upsert a Person updates the record if it exists or creates it if not, and Create a Task for a Person puts a first call on a rep's list.

Closed deals update themselves. When a contract gets signed in your e-signature tool, Search Deals finds the matching opportunity and Update a Deal Status records the outcome, so nobody has to remember to do it.

One product list, several tools. List Products reads your Agendor catalog so a price sheet elsewhere, for instance a base built with the Airtable Make integration, can be rebuilt from it.

What Make does not do here: Agendor has no trigger in Make, so a change inside Agendor never starts a scenario on its own. The scenario starts from another app or from a schedule. If you are weighing Make against another tool, the n8n vs Make comparison lays out the criteria, and Make pricing explains what each plan includes.

Connect

How do you connect Agendor to Make?

01
Copy your Agendor API key
Make talks to Agendor through an API key, a private code tied to your account. In Agendor, open Menu, click Integrations and copy the API key displayed on screen. You need an active Agendor account for this step.
02
Open the connection window
In a Make scenario, add any Agendor module and click Create a connection. A connection is your Agendor account linked to Make once, then reused by every Agendor module you add later.
03
Name it and paste the key
The Connection name field is optional, but a clear label such as “Agendor sales” helps once several accounts exist. Paste the API key you copied and save: Make can now read and write your CRM records.

First scenario

Your first scenario: from a new lead to a follow-up task

GoalWhen a new lead fills your web form, Make adds the person to Agendor and gives a rep a follow-up task.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. Pick the app where your leads arrive, such as your form tool, and its module that picks up new entries.
02
Add Upsert a Person
Click the + to the right of that first module, search for Agendor and choose Upsert a Person. Select your connection, or click Create a connection if this is your first Agendor module.
03
Map the lead's answers
Fill the person fields by mapping the answers from the form module. Because the module updates a known contact and creates a missing one, a lead who writes twice stays a single record.
04
Add the follow-up task
Click the + again and add Create a Task for a Person. Map the person returned by Upsert a Person, so the task sits on the contact Make just saved.
05
Test with Run once
Send a test entry through your form, then click Run once. Open each module to read the bundles it received, and check the new contact and its task in Agendor.
06
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each new lead now reaches a rep's task list without anyone copying it.

Modules

What each Agendor module does

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

Agendor1

Create a Deal for an Organization

Action

In Make“Creates a new deal for an organization.”

Opens a new deal in Agendor directly on a company record, so the opportunity appears in the pipeline under the right account without anyone retyping it.

When to use it

a business customer asks for a quote through another tool and sales should see it as a deal.

Watch out

map the organization from an earlier module such as Upsert an Organization, otherwise Make has no account to attach the deal to.

Agendor2

Create a Deal for a Person

Action

In Make“Creates a new deal for a person.”

Starts an opportunity tied to an individual contact rather than a company, which suits freelancers, consumers or any lead with no organization behind them.

When to use it

a single person books a demo or fills a pricing form and the deal belongs on their own record.

Watch out

run Upsert a Person first and map its result here, so the deal never points to a duplicate contact.

Agendor3

Create an Organization

Action

In Make“Creates a new organization.”

Adds a company to Agendor as a brand-new record, the account that people, deals and tasks can later hang from.

When to use it

a partner signs up through another app and you are certain the company is new to your CRM.

Watch out

this module is built for new companies; if the company might already exist, Upsert an Organization avoids a second copy.

Agendor4

Create a Person

Action

In Make“Creates a new person.”

Records a new contact in Agendor from data another module passes along, ready to receive deals and tasks afterwards.

When to use it

an event registration list gives you attendees you have never met and want in the CRM.

Watch out

Create a Person is meant for new contacts; when a source mixes new and known people, Upsert a Person updates the existing record instead of adding another.

Agendor5

Create a Product

Action

In Make“Creates a new product.”

Adds an item to your Agendor product catalog, so the list your sales team works from matches what you actually sell.

When to use it

your team launches a new service in a billing or e-commerce tool and the CRM catalog should follow.

Watch out

place List Products before it when the same item may already be in Agendor, so you do not create it twice.

Agendor6

Create a Task for a Deal

Action

In Make“Creates a new task for a deal.”

Puts a to-do on a specific deal, so the next step of an opportunity is written where the rep will look for it.

When to use it

your scenario moves a deal forward and someone now has to send the contract or call the client back.

Watch out

map the deal from Search Deals or Get a Deal; a task on the wrong opportunity is easy to miss.

Agendor7

Create a Task for an Organization

Action

In Make“Creates a new task for an organization.”

Attaches a task to a whole company instead of one contact or one deal, which fits account-level work.

When to use it

a customer's contract comes up for renewal in your billing tool and the account owner needs a reminder.

Watch out

pick this one only when the task concerns the company as a whole; if it targets one contact, Create a Task for a Person keeps it on that person's record.

Agendor8

Create a Task for a Person

Action

In Make“Creates a new task for a person.”

Gives a named contact a follow-up in Agendor, which is how a fresh lead turns into a call someone actually makes.

When to use it

right after Upsert a Person, to plan the first call for every inbound lead.

Watch out

map the person returned by the previous module rather than typing a name, so the task lands on the record Make just created or updated.

Agendor9

Delete an Organization

Action

In Make“Deletes an organization.”

Removes a company from Agendor for good, which keeps the CRM free of test accounts and businesses you no longer track.

When to use it

a cleanup scenario receives companies your team has flagged for removal in a shared sheet.

Watch out

treat the deletion as final and try the scenario with Run once on a single test record before switching it on.

Agendor10

Delete a Person

Action

In Make“Deletes a person.”

Erases a contact record, useful when someone asks to be forgotten or when a duplicate has been merged by hand.

When to use it

a request to remove personal data reaches your support tool and has to be applied in the CRM as well.

Watch out

confirm the right person with Search Persons first, because deleting on a name alone can hit a namesake.

Agendor11

Delete a Product

Action

In Make“Deletes a product.”

Takes an item out of the Agendor catalog so reps stop proposing something you no longer sell.

When to use it

a service is retired in your billing tool and the CRM product list should drop it too.

Watch out

treat the deletion as final and test the scenario once with Run once and one sample product before activating it.

Agendor12

Get a Deal

Action

In Make“Retrieves a specific deal.”

Fetches one deal with its details when you already know which one you need, so the next modules can reuse its values.

When to use it

another app stores the Agendor deal reference and you want its latest details before sending an email about it.

Watch out

Get a Deal reads a single record; to find deals by criteria, Search Deals is the module to pick.

Agendor13

Get an Organization

Action

In Make“Retrieves a specific organization.”

Reads a single company record and hands its data to the rest of the scenario, without changing anything in Agendor.

When to use it

an invoicing tool needs the company's details from the CRM before it builds a document.

Watch out

this module expects one known organization; when all you have is a name, start with Search Organizations.

Agendor14

Get a Person

Action

In Make“Retrieves a specific person.”

Pulls up one contact from Agendor so that later modules can personalize a message or fill another tool with it.

When to use it

a task or deal points to a person and you need the full record to write back to them.

Watch out

each run of Get a Person counts as an operation, so skip it when the previous module already carries the data you need.

Agendor15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Agendor API through your existing connection, which covers whatever the listed modules leave out.

When to use it

you need an Agendor feature that has no dedicated module in Make and do not want a second connection.

Watch out

you write the request yourself, path and body included, so keep Agendor's API documentation open while you set it up.

Agendor16

Update a Deal

Action

In Make“Updates a deal.”

Changes the details of an existing deal, so the CRM reflects what happened in another tool without a rep editing it.

When to use it

a quote is revised in your proposal software and the deal should carry the new information.

Watch out

to move a deal along the pipeline or record its outcome, the dedicated Update a Deal Stage and Update a Deal Status modules say more clearly what you mean.

Agendor17

Update a Deal Stage

Action

In Make“Updates a deal stage.”

Moves a deal to another step of your Agendor pipeline, which keeps the sales board in line with real progress.

When to use it

a meeting gets booked in your calendar tool and the matching deal should advance without a manual drag.

Watch out

stage and status are two separate modules: this one moves the deal along the pipeline, Update a Deal Status handles where it stands.

Agendor18

Update a Deal Status

Action

In Make“Updates a deal status.”

Sets the status of a deal, so the CRM records where the opportunity stands after an event in another app.

When to use it

a contract is signed or a payment arrives in another tool, and the deal should show that outcome.

Watch out

run Search Deals first when the app that started the scenario does not know the Agendor deal, then map the one it returns.

Agendor19

Update an Organization

Action

In Make“Updates an organization.”

Edits a company that already sits in Agendor, keeping its record current when the source of truth lives elsewhere.

When to use it

a customer changes their company details in your billing portal and the CRM should follow.

Watch out

it works on an existing organization only; if the company may be missing, Upsert an Organization handles both cases.

Agendor20

Update a Person

Action

In Make“Updates a person.”

Refreshes a contact's record when their information changes in another app, so reps work from current details.

When to use it

a subscriber edits their profile in your newsletter tool and the CRM contact should match.

Watch out

map the person from Search Persons or Get a Person, so the change reaches the right record and not a namesake.

Agendor21

Upsert an Organization

Action

In Make“Updates an organization or creates new if not exist.”

Updates a company if Agendor already has it and creates it if not, all in a single module.

When to use it

leads come from a source where you cannot tell new accounts from known ones, such as a trade show list.

Watch out

place it before any deal or task module, then map its output, so everything attaches to the same company.

Agendor22

Upsert a Person

Action

In Make“Updates a person or creates new if not exist.”

Makes sure a contact exists in Agendor with the latest details, whether it is a first visit or a returning lead.

When to use it

as the first Agendor step of any lead scenario, before creating deals or tasks.

Watch out

map what it returns into the next modules rather than the raw form data, so they point to the Agendor record.

Agendor23

List Deals of an Organization

In Make“Retrieves a list of deals for a selected personal.”

Returns every deal belonging to one company, each as a separate bundle that the next modules process in turn.

When to use it

an account manager wants a summary of all the business with a client before a review meeting.

Watch out

each returned deal runs through the following modules, so a company with many deals multiplies the operations of everything after it.

Agendor24

List Deals of a Person

In Make“Retrieves a list of deals for selected person.”

Collects the deals linked to one contact, handy when a person buys several times or follows more than one project.

When to use it

a support ticket comes in and the agent should see what the customer has bought or discussed.

Watch out

plan for contacts with no deal at all, since the search can come back empty.

Agendor25

List Persons of an Organization

In Make“Retrieves a list of persons for a selected organization.”

Lists the contacts attached to a company, so one scenario can reach every person you know on an account.

When to use it

a contract change or a company-wide announcement must go to everyone on the client side.

Watch out

each person comes out as its own bundle, and every module after this one runs once per person.

Agendor26

List Products

In Make“Retrieves a list of products.”

Pulls your Agendor product catalog into the scenario, item by item, to reuse it in another tool.

When to use it

a price sheet or a website catalog must stay aligned with the products sales can offer.

Watch out

a long catalog produces one bundle per product, and each one counts as an operation in the modules that follow.

Agendor27

Search Deals

In Make“Searches for deals or list them all.”

Finds the deals that match your criteria, or returns all of them when you leave the search open.

When to use it

the app that starts your scenario knows the client but not the Agendor deal, and you need the deal before updating it.

Watch out

a broad search can return several deals; make sure the right one reaches Update a Deal Status.

Agendor28

Search Organizations

In Make“Searches for organizations or list them all.”

Looks up companies in Agendor by your criteria, or lists them all, and passes each match on as a bundle.

When to use it

before creating anything, to check whether a prospect's company is already in the CRM.

Watch out

an empty result is possible and normal, so decide what the scenario should do when no company matches.

Agendor29

Search Persons

In Make“Searches for persons or list them all.”

Searches your contacts, or returns the full list, so a scenario can find a person before acting on them.

When to use it

an email or a chat conversation gives you someone's details and you want the matching Agendor record.

Watch out

two contacts can share a name, so several bundles may come back where you expected one.

Agendor30

Search Tasks

In Make“Searches for tasks or list them all.”

Returns tasks across the whole CRM, matching your criteria or all at once, to review workload or pending follow-ups.

When to use it

a scheduled scenario gathers tasks to post a digest in your team chat.

Watch out

without narrowing the search, every task becomes a bundle and every later module runs once for each of them.

Agendor31

Search Tasks of a Deal

In Make“Searches for tasks for a selected deal or list them all.”

Brings back the tasks of a single deal, so you can see what is left to do on that opportunity.

When to use it

before Update a Deal Status, to review the follow-ups still attached to the deal.

Watch out

map the deal from an earlier search; this module looks inside one deal only and ignores the rest of the pipeline.

Agendor32

Search Tasks of an Organization

In Make“Searches for tasks for a selected organization or list them all.”

Gathers the tasks logged against a company, which gives an account-level view of what your team still has to do for that client.

When to use it

an account moves to a new rep, who needs the list of pending actions.

Watch out

tasks placed on the company's people or deals may not appear here; Search Tasks of a Person and Search Tasks of a Deal cover those.

Agendor33

Search Tasks of a Person

In Make“Searches for tasks for a selected person or list them all.”

Lists the tasks tied to one contact so a scenario knows what is already planned before adding more.

When to use it

before Create a Task for a Person, to avoid giving the same lead two follow-up calls.

Watch out

the search may return nothing for a new contact, which is expected; think about both outcomes when you build the next module.

Need help

Need help automating Agendor with Make?

A person reads every message.

FAQ

Agendor and Make: frequent questions

01Is the Agendor Make integration free?

Yes. Agendor is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, one scheduled run every 15 minutes at the shortest, 5 minutes of execution per run and 512 MB of data transfer. Every module that runs on one bundle counts as one operation against your monthly credits. Paid Make plans shorten the interval to 1 minute and remove the cap on active scenarios. Your Agendor subscription is separate and is not covered by Make.

02What do you need to connect Agendor to Make?

An active Agendor account and its API key. In Agendor, open Menu, then Integrations, and copy the key shown on screen. In Make, add any Agendor module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves all 33 modules, so the setup happens once per Agendor account rather than once per scenario. Your Make account can be on any plan, since Agendor is a standard app.

03Does Agendor trigger Make scenarios in real time?

No. Agendor has no trigger module in Make, neither scheduled nor instant (an instant trigger is one the app fires through a webhook as soon as something happens). A change inside Agendor therefore cannot start a scenario. You start it another way: with a trigger from another app, such as a form or a store, or with a schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans. A schedule paired with Search Deals or Search Tasks reads Agendor on each run.

04What if the Agendor module you need is missing?

Use Make an API Call. It sends a request to any endpoint of the Agendor API with the connection you already have, so you are not limited to the 33 listed modules. You will need Agendor's API documentation to know the path and the content to send. Before going that far, look at the 11 search modules: several needs, such as finding the tasks of one deal or the contacts of one company, already have a dedicated module.

05Should you use Make or n8n for Agendor?

It depends on where your automations already live. On Make, Agendor comes with 33 ready modules covering deals, people, organizations, tasks and products, plus Make an API Call for the rest, and it runs on the Free plan. n8n is a separate automation tool; if your other workflows are there, check whether it offers an Agendor node before moving anything. Compare the modules you need, where your other automations sit and who will maintain them, then keep your CRM flows in one tool.

Copy your Agendor API key

Open the connection window

Name it and paste the key

Create the scenario

Add Upsert a Person

Map the lead's answers

Add the follow-up task

Test with Run once

Schedule and switch on

Need help automating Agendor with Make?