Agendor Zapier integrationAutomate Agendor with Zapier.
The Agendor Zapier integration gives you 10 triggers, 9 actions and 3 searches. All 10 triggers are instant, even on the free plan, so this page focuses on what each run costs, how to target the right deal and which CRM moves to automate first.
Verified Trustpilot reviews · AI, automation & growth agency
What the Agendor Zapier integration is for
Agendor is a sales CRM built for Brazilian companies with long sales cycles, on the web and on mobile. Hooking it up to Zapier lets a change in your pipeline start an automation, or lets another tool create and update deals, companies and people in Agendor without anyone retyping them.
Start with the good news, because it is rare: every one of the 10 Agendor triggers is instant. Agendor tells Zapier the moment a deal is won, lost, moved or edited, so a Zap reacts right away, even on the free plan. In the editor that shows as a lightning bolt.
Three results follow from that. A pipeline that hands work over by itself: Deal Won or Deal Stage Changed starts the Zap, and Create Task puts the next step on someone's list. A clean contact base fed from outside: a form or a store feeds Create or Update Person and Create or Update Organization, which create the record or update it when it is already there. Deals kept in line with the rest of your tools: Update Deal Stage and Update Deal Status move a deal when something happens elsewhere.
What Zapier does not do here: the update actions need the internal ID of the record, so a Zap has to get it from a trigger or a search first. There is no action to delete anything, and the advanced API Request (Beta) is the only way past the listed operations. To compare platforms, see the Agendor Make integration page and the n8n vs Zapier comparison.
Zapier vocabulary in one minute
Eight words carry the rest of the page. Each is defined once here, then used as is.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a deal marked as won in Agendor. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that creates, updates or sends something for you, like adding a task to a deal.
- Task (Zapier)
- The unit Zapier bills: one action your Zap completed successfully. Not to be confused with an Agendor task, the to-do item.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer. Agendor's are all instant.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and quietly stops it otherwise.
- Search step
- A step that looks up a record that already exists, such as a deal or a person, so later steps can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
What an Agendor Zap really costs
Zapier bills tasks, and only successful actions become tasks. A trigger firing costs nothing.
- Free plan100 tasks a month, unlimited Zaps
- Free plan stepsOne trigger and one action
- Agendor on the free planYes, it is not a premium app
- Agendor triggersAll instant, no waiting
Each action that succeeds counts on its own, so a Zap that finds a person and then creates a task can spend two tasks per run. A failed action is not billed. Agendor is not a premium app, so it runs on the free plan, which stops at two steps: one trigger, one action. A filter or a search makes the Zap multi-step, and that needs a paid plan. The interval grid below only applies to polling triggers, so it never slows Agendor's.
Connect your Agendor account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Agendor account linked once to Zapier, then reused by every step that needs it.
- 02
Pick Agendor
Search for Agendor in the dialog, select it and click Add connection. A new tab opens on the Agendor side: sign in with the account the Zaps should act for.
- 03
Grant access
Allow Zapier to access the account. You need an Agendor account, plus read or write rights on any deal, company or person you do not own yourself but want a Zap to touch.
Your first Agendor Zap: a kickoff task for won deals
GoalWhen a deal is won and meets your condition, create the onboarding task for it in Agendor.
- 01
Set the trigger
In the editor, the Build stage is where you choose apps and events. Pick Agendor, the
Deal Wonevent and your connection. A lightning bolt confirms the trigger is instant. - 02
Test with a real deal
Run the trigger test. Zapier brings back the three most recent won deals from your account; pick one, and map the next steps on that real record.
- 03
Add the filter
From the plus icon, add Filter. In Configure & test, choose the field, the rule and the value. Use a number rule for numbers and a text rule for text, or it never passes.
- 04
Create the task
Add Agendor with
Create Task. Fill what it relates to, the text and the author, mapping the deal from the test item. The filter makes this a multi-step Zap, so it needs a paid plan. - 05
Test, then publish
Use Test on the action and check the new task in Agendor. Then click Publish. Only deals won after that moment will start the Zap.
Agendor triggers on Zapier
10 events start a Zap when something happens in Agendor, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.
New Task
Instant triggerIn Zapier“Triggers when a new Task (Tarefa/Comentário) is created.”
Fires when someone adds a task or comment (Tarefa/Comentário) in Agendor. It lets the to-dos your sales team writes in the CRM show up wherever people actually plan their day.
New Deal
Instant triggerIn Zapier“Triggers when a new Deal (Negócio) is created.”
Starts the Zap as soon as a new deal (Negócio) is created in Agendor, by hand or by another tool.
Deal Lost
Instant triggerIn Zapier“Triggers when a Deal (Negócio) is set as lost.”
Reacts when a deal is marked as lost. A lost deal is still information, and this trigger makes sure it reaches someone instead of disappearing from the pipeline view.
Deal Stage Changed
Instant triggerIn Zapier“Triggers when a Deal (Negócio) moves to another stage (Etapa) in the pipeline.”
Goes off each time a deal moves to another stage (Etapa) of the pipeline. Of all the deal triggers, this is the one that follows progress step by step.
Updated Deal
Instant triggerIn Zapier“Triggers when a Deal (Negócio) is edited.”
Picks up any edit to a deal in Agendor, whatever field changed. Broader than the stage or status triggers, it catches everything.
Update Deal Basic Data on the same deals makes the Zap set itself off again and again.Deal Won
Instant triggerIn Zapier“Triggers when a Deal (Negócio) is set as won.”
Sends the Zap off the moment a deal is marked as won, which is usually where sales ends and delivery begins.
Update Deal Status in another Zap can mark deals as won and set this trigger off as well.New Organization
Instant triggerIn Zapier“Triggers when a new Organization (Empresa) is created.”
Triggers when a company (Empresa) is added to Agendor. It is the right entry point for anything account-based rather than deal-based.
Updated Organization
Instant triggerIn Zapier“Triggers when an Organization (Empresa) is edited.”
Catches every edit made to a company record in Agendor, so the account data spread across your tools can follow it.
Update Organization or Create or Update Organization can loop on itself.New Person
Instant triggerIn Zapier“Triggers when a new Person (Pessoa) is created.”
Runs when a new contact person (Pessoa) is created in Agendor, so the people side of the CRM can feed your other tools.
Create or Update Person also come through here, which is easy to forget.Updated Person
Instant triggerIn Zapier“Triggers when a Person (Pessoa) is edited.”
Fires whenever someone edits a person's record in Agendor. It is the contact-side twin of Updated Organization.
Update Person from this Zap, or it retriggers and burns tasks.Agendor actions on Zapier
Agendor gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Task
ActionIn Zapier“Creates a Task (Tarefa/Comentário).”
Adds a task or comment in Agendor, attached to the record it relates to, so the follow-up sits where the salesperson looks.
Update Deal Stage
ActionIn Zapier“Updates a Deal Stage (Mover Negócio de Etapa).”
Moves a deal to another stage of the pipeline from outside Agendor.
Deal Stage Changed can loop if it moves the same deal.Update Deal Status
ActionIn Zapier“Updates a Deal Status (Atualizar Status de um Negócio).”
Sets a deal's status, for instance won or lost, without anyone opening the CRM.
Deal Won or Deal Lost Zaps.Update Deal Basic Data
ActionIn Zapier“Updates a Deal (Negócio).”
Rewrites the basic data of a deal that already exists in Agendor, from outside the CRM.
Updated Deal Zap on the same deals will see this change.Update Organization
ActionIn Zapier“Updates a Organization (Empresa).”
Edits a company record that already exists in Agendor.
Find Organization, has to supply it.Create or Update Organization
ActionIn Zapier“Creates or updates an Organization (Empresa).”
Adds a company to Agendor, or refreshes it if it is already there, so account records stay single.
Update Person
ActionIn Zapier“Updates a Person (Pessoa).”
Changes the details of a person who already exists in Agendor.
Find Person first.Create or Update Person
ActionIn Zapier“Creates or updates a Person (Pessoa).”
Creates a person in Agendor, or updates them when they already exist, so one action covers both cases.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced action for what the list above does not cover: it sends a raw request to Agendor using your existing connection, so you skip the sign-in work.
Agendor searches on Zapier
3 search steps look for data that already exists in Agendor, so a later step can use it.
A search step finds a record that already exists in Agendor and hands it to the steps that follow. In the editor, Agendor's searches sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts one just before and wires the result in for you. Each app decides whether a search wants an exact match or a close one. Three settings decide what happens when the search does not go as planned.
Find Deal
SearchFind or createIn Zapier“Finds a deal.”
Looks up a deal that already exists in Agendor so a later step can update it or attach a task to it.
Update Deal Status.Find Organization
SearchFind or createIn Zapier“Finds an organization.”
Finds a company record in Agendor and passes its ID on, which is exactly what Update Organization needs.
Find Person
SearchFind or createIn Zapier“Finds a person.”
Retrieves a person already in Agendor, so the Zap can update them or link a task to them instead of creating a duplicate.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on with nothing.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create: it hides the setting above and asks for the fields needed to create the missing record.
- If multiple search results are found?Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When an Agendor Zap breaks
Zapier attaches no Agendor-specific help article and no documented rate limit to this app. What goes wrong comes from how Zapier itself works.
Four situations cover the surprises. None of them looks like an obvious error, which is why they are worth knowing before you publish. For anything else, the Zapier troubleshooting guide is the next stop.
Nothing from before the Zap
A Zap only reacts to what happens after you publish it. Deals, companies and people already in Agendor are never picked up; moving that backlog is a separate job.A Zap that triggers itself
Updated Deal plus Update Deal Basic Data, or Updated Person plus Update Person, on the same records: the Zap writes where it watches, starts again and burns tasks.A big import held back
When a trigger suddenly sends a huge batch, after importing a contact list for instance, Zapier's flood protection can hold it back instead of running it.A search that finds nothing
With the default setting, a Find step that comes back empty stops the Zap there and skips what depended on it. Switch the setting on, or use find-or-create.
Need help automating Agendor with Zapier?
A person reads every message.
