Agendor

Connect AI agents to Agendor, a sales CRM built for Brazilian small and medium businesses. Agents create organizations and people, move deals through funnels, assign tasks, and read the categories, sectors, and lead origins those records depend on.

30 actions API key available

Platform Documentation ↗

A qualified lead arrives from a landing page or a spreadsheet row

Upsert Organization matches the empresa instead of creating a second one

Upsert Person attaches the contact to that organization

List Users resolves the owner so the deal is assigned to a real person

Create Deal opens the deal on the correct funnel and stage sequence

Create Task schedules the first follow-up as a call or WhatsApp touch

The owner is told the deal exists and what the lead actually asked for

Sales manager confirms the funnel and stage before a bulk batch is written

What This Integration Enables

Agendor is a sales CRM for Brazilian small and medium businesses, and it is opinionated in a way that matters for automation. Duplicate prevention is built into the API rather than bolted on afterwards: Upsert Organization and Upsert Person exist precisely because an SMB sales team gets the same company from three sources in a week. A deal cannot float free either, it has to attach to an organization or a person. And the wire values are Portuguese, so a task type is VISITA, REUNIAO, LIGACAO, EMAIL, PROPOSTA, or WHATSAPP, and a deal status is ongoing, won, or lost. Automation that respects those constraints keeps the funnel honest. Automation that ignores them fills the CRM with orphans.

FlowRunner agents work the whole object model through this connector: organizations, people, deals, tasks, products, and the users those records are assigned to. Agendor does not publish a webhook subscription API with a documented payload shape, so this connector ships no triggers. Agents run on a schedule instead, polling List Deals, List Tasks, or List Deal Movements History to catch what changed since the last pass. That is a normal pattern and it is honest about what the vendor offers. What FlowRunner adds on top is the digital andon cord: the point where the agent stops writing and asks, because a pipeline is a record other people make decisions from.

Without FlowRunner

Duplicate empresas The same company arrives twice from two campaigns and both records survive

Leads that sit unassigned A form fill lands in an inbox and waits for someone to notice it

Funnel reports built by hand Stage moves get recorded when someone remembers, so the pipeline is a guess

With FlowRunner

One record per company Upserts resolve the match at write time rather than during a cleanup project

Owned on arrival Every qualified lead reaches Agendor with an owner, a funnel, and a first task

Movement history that is true Stage changes are written when the event happens, so reports read the record

Use Case Scenarios

Inbound leads that arrive already filed

Leads from ad platforms and web forms collect in Google Sheets. On a schedule, the agent reads new rows and calls Upsert Organization for the empresa and Upsert Person for the contact, so a company already in Agendor gains a new contact rather than a twin record. List Users resolves the territory owner, then Create Deal opens the deal attached to that organization with the right funnel and stage sequence number, and Create Task schedules the first touch as a LIGACAO or WHATSAPP depending on what the lead supplied. The rep opens Agendor to a deal that already knows who owns it and what to do next.

Stalled deals surfaced instead of buried

Because Agendor ships no triggers, the agent polls. On a nightly run it calls List Deals filtered to ongoing status and cross-references List Deal Movements History to find deals that have not changed stage inside their usual dwell time. Those get named in a Slack digest with owner, value, and days since the last movement. Deals with no open task at all are called out separately, because that is the failure that costs money quietly. The sales manager reads a short list of exceptions rather than exporting the pipeline into a spreadsheet every Friday.

Won deals that update the rest of the business

When a contract is signed, the agent calls Update Deal Status to mark the deal won, Update Deal to record the final value, and Create Task to open the handover activity for the delivery owner. Get Organization pulls the company detail, and Google Sheets receives a revenue row with the deal value, owner, and product mix read from List Products. If the deal is lost instead, the agent records the loss reason on the same call, because a funnel report is only useful when the lost column has reasons in it.

Human-in-Loop Highlight

Agendor makes deletion permanent, and it makes organizations load-bearing. A deal has to attach to an organization or a person, so an empresa record is not just a name in a list, it is the anchor the pipeline hangs from. When a dedup agent finds two organizations for the same company, one carrying two open deals and the other carrying eight months of tasks and the CNPJ, it does not pick a winner. It gathers the evidence with Get Organization, List Organization People, List Deals, and List Tasks, then messages the sales manager on WhatsApp, which is a first-class activity type in this CRM and where a Brazilian SMB sales lead actually is: "Two organizations match Construtora Vale. ID 88214 carries the open deals worth R$ 96.000. ID 91077 carries the CNPJ and the task history. Which record survives?" Only after the answer does the agent move the people and deals onto the survivor and call Delete Organization on the duplicate. The same rule covers Delete Person and Delete Product. The agent is faster than a person at finding the duplicate. It is not entitled to decide which version of a customer relationship the company keeps.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via WhatsApp

Human decides

Agent resumes with decision

Agent Capabilities

30 actions

Organizations

List Organizations Returns a paginated list of organizations with filters. Used for account sweeps, territory reports, and duplicate detection passes.
Get Organization Retrieves a single organization with its full field set. Used to load context before an update, a merge decision, or a deal write.
Create Organization Creates a new empresa record with name, contact details, category, sector, and lead origin. Used when a company enters the pipeline for the first time.
Update Organization Updates the supplied fields on an existing organization, including the zero to five star ranking. Used to enrich or correct records without clobbering what is already there.
Delete Organization Permanently deletes an organization. Cannot be undone, so agents assemble the case and a person makes the call.
Upsert Organization Creates the organization if it does not exist and updates it if it does. Used as the default write path for imports, because it is Agendor's own answer to duplicate prevention.
List Organization People Returns the contacts attached to a given organization. Used to see who is already known at an account before adding another name.

People

List People Returns a paginated list of contacts with filters. Used for outreach lists and data quality sweeps.
Get Person Retrieves a single contact with their full field set. Used before enrichment, routing, or a merge decision.
Create Person Creates a contact, optionally attached to an organization. Used when a new individual appears on an existing account.
Update Person Updates the supplied fields on an existing contact. Used for enrichment and ownership corrections.
Delete Person Permanently deletes a contact. Cannot be undone, so it stays behind a human decision.
Upsert Person Creates the contact if it does not exist and updates it if it does. Used for imports where the same person may arrive from several sources.

Deals

List Deals Returns deals with filters including status, where the wire filter uses status IDs one for ongoing, two for won, and three for lost. Used for pipeline reports and stalled deal sweeps.
Get Deal Retrieves a single deal with its current funnel, stage, and value. Used to confirm state before a stage or status move.
Create Deal Creates a deal attached to an organization or a person, with funnel, stage sequence number, value, and owner. Used the moment a lead qualifies.
Update Deal Updates the supplied fields on a deal, including value, ranking, and description. Used to keep the number on the record matching the number in the quote.
Update Deal Status Moves a deal to ongoing, won, or lost, recording a loss reason where the outcome is lost. Used at the close so win rate reporting has something real to read.
Update Deal Stage Moves a deal to a stage by its sequence number, with the funnel ID supplied when the target stage is outside the default funnel. Used to advance the pipeline as events happen elsewhere.
List Deal Movements History Returns the recorded stage and status movements for deals. Used to measure dwell time, build funnel conversion reports, and find deals that have quietly stopped moving.

Tasks

List Tasks Returns tasks with filters. Used to audit open follow-ups by owner or by account.
Create Task Creates a task attached to an organization, person, or deal, typed as VISITA, REUNIAO, LIGACAO, EMAIL, PROPOSTA, or WHATSAPP. Used so every qualified lead leaves the automation with a scheduled next step.
Update Task Updates an existing task, including completion and rescheduling. Used as work finishes or priorities move.

Products

List Products Returns the product catalog with filters. Used to resolve product IDs before writing deal line detail or building a mix report.
Get Product Retrieves a single product record. Used to confirm pricing and naming before a write.
Create Product Adds a product to the Agendor catalog. Used to keep the CRM catalog in step with an external system of record.
Update Product Updates an existing product. Used when pricing or naming changes upstream.
Delete Product Permanently deletes a product. Cannot be undone, so it is treated as a human-approved change.

Users

List Users Returns the account's users with their IDs. Used to assign owners and responsible parties to real people rather than to a guess.
Get Current User Returns the account the API token belongs to. Used to confirm credentials and scope before a run writes anything.

Frequently Asked Questions

What can FlowRunner do with Agendor?

FlowRunner agents can run List Organizations, Get Organization, and Create Organization in Agendor, plus 27 more actions.

Does connecting Agendor to FlowRunner require OAuth?

No. Agendor connects to FlowRunner with an API key, no OAuth flow required.

Can Agendor trigger a FlowRunner workflow automatically?

Agendor doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Agendor

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us