B2Cor CRM

Connect AI agents to B2Cor, a Brazilian CRM built for insurance brokers. Agents capture leads, move them through sales funnels, and read the lead origins, task types, and users those records depend on.

19 actions API key available

Platform Documentation ↗

A quote request lands on an insurance landing page or partner form

List Origins resolves the origin code this brokerage actually uses

List Users resolves the broker who should own the lead

Create Lead writes the prospect with the right form type and origin

Add Leads To Funnel places the lead in the correct funnel and stage

The owning broker is told a quote request is waiting and what it is for

Broker manager approves the funnel change before a bulk pipeline move runs

What This Integration Enables

B2Cor is a CRM and sales funnel platform for Brazilian insurance brokers, and the thing it moves through its funnels is not an abstract opportunity. It is a named person's insurance shopping, with their contact details and the product they are trying to buy attached. The vendor's own documentation flags this: lead records contain the personal data of insurance prospects. That shapes what good automation looks like here. Speed matters, because an insurance quote request goes cold in hours, but so does keeping the record accurate and keeping the outbound contact under a broker's control.

FlowRunner agents work leads end to end through this connector: creating and editing them, updating status, contact detail, and ownership, appending history, sending contact messages, adding and removing them from funnels, and pulling unexported leads into a warehouse or spreadsheet. The connector ships no triggers, so change detection runs on a schedule against List New Leads and Search Leads. Two API behaviors shape how agents are built on it. Most write actions return no body at all, so success is read from the HTTP status rather than from returned data, and List New Leads returns only leads not yet marked as exported, which makes Mark Lead As Exported the cursor that keeps a sync from repeating itself. Neither is a problem. Both are reasons to be deliberate about which writes an agent performs alone, and which ones stop for a person. That boundary is what human-in-the-loop orchestration is for.

Without FlowRunner

Leads copied out of email Quote requests arrive as notifications and get retyped into the CRM

Wrong form type on the record A health lead is filed as an auto lead, so the wrong quote workflow starts

Exports that repeat themselves The same leads get pulled into the warehouse twice because nothing marks them done

With FlowRunner

Leads created at capture Every form submission becomes a lead with its origin, form type, and owner set

Correct product path from the start The form type is resolved before the write, so the right quoting process begins

An export cursor that holds Processed leads are marked exported, so the next run picks up only what is new

Use Case Scenarios

Quote requests that reach a broker while they are still warm

A visitor fills in a health insurance quote form. The agent calls List Origins and List Task Types to resolve the brokerage's own codes, List Users to pick the broker on rotation, then Create Lead with the correct form type so the right quoting path begins. Add Leads To Funnel places it at the top of the new business funnel and Add Lead History records where it came from. Slack tells the broker a quote request is waiting with the prospect's product and the value estimate. The broker makes the first contact themselves, because a first call to an insurance prospect is theirs to make.

A one-way sync into the warehouse that does not repeat

On a schedule, the agent calls List New Leads, which returns only leads not yet marked as exported. It writes each one into Google Sheets for the analytics team, then calls Mark Lead As Exported with the batch of lead codes so the next run starts where this one finished. If the sheet write fails, the export mark is never sent, so the leads reappear on the next pass rather than vanishing. The cursor lives in B2Cor rather than in a state file, which means a rerun after an outage is safe by construction.

Pipeline hygiene that names the deals instead of clearing them

Ahead of the monthly review, the agent runs Search Leads across the active funnels, groups by status, and builds the picture the broker manager actually wants: which leads are sitting in Negociacao with no history entry in three weeks, which ones changed owner but never got a follow-up task, and which ones have a sale value recorded but no closing status. Update Lead Status and Change Lead Owner handle the corrections the manager approves. Remove Leads From Funnel handles the specific leads that should come out. Clear Funnel is the one action the agent never reaches for on its own.

Human-in-Loop Highlight

Clear Funnel removes every lead from a funnel in a single call, and like most B2Cor write actions it returns no body, so the agent cannot even report afterwards which leads it took. There is no undo action in this connector. That combination is exactly the shape of decision that belongs to a person. So when the quarterly hygiene agent finds a funnel clogged with stale leads, it does the work up to the edge and stops. It enumerates the funnel with Search Leads, separates the genuinely dead records from the ones still carrying a Negociacao status or a recent history entry, and posts the split to the broker manager in Slack: "Funnel Auto Novos holds 214 leads. 187 have had no history entry in 90 days. 27 are still in Negociacao, 9 of those carry a sale value, and 3 changed owner last week. Clear Funnel takes all 214 and reports nothing back. Clear the whole funnel, or remove the 187 by code?" The manager picks, and the agent executes with Remove Leads From Funnel or Clear Funnel accordingly. The agent is better at counting. The person is the one who knows that lead 41 is a broker's brother-in-law who is about to sign.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

19 actions

Leads

List New Leads Returns only the leads that have not yet been marked as exported. Used as the incremental cursor for syncing leads into a warehouse, spreadsheet, or ERP without pulling the same records twice.
Get Lead Retrieves a single lead by its code. Used to load the full record before a status change, ownership change, or downstream write.
Search Leads Searches leads with filters. Used for pipeline reporting, stale lead detection, and building the evidence behind a funnel cleanup.
Create Lead Creates a lead with its insurance form type and origin, taking a lead data object whose keys follow the B2Cor lead model. Used to push a captured quote request into the CRM the moment it arrives.
Edit Lead Updates an existing lead with a lead data object. Used when better information about the prospect or the product arrives after capture.
Update Lead Status Moves a lead to one of B2Cor's standard statuses, with the friendly labels mapped to the wire values the API expects. Used to keep funnel reporting in step with what the broker actually did.
Update Lead Info Updates the lead's commercial detail, including sale values as the deal progresses. Used so closed business carries a real number.
Update Lead Contact Updates the prospect's contact details on the lead. Used when a correction or an enrichment step produces a better phone number or email.
Change Lead Owner Reassigns a lead to a different broker by user code. Used for rotation, territory changes, and coverage when a broker is unavailable.
Add Lead History Appends a history note to the lead. Used to record what an automation did and why, so the broker opening the record sees the whole story.
Mark Lead As Exported Marks one lead code or a list of codes as exported so they stop appearing in List New Leads, and can be set back to false to make them reappear. Used to close the loop on an incremental sync.
Send Contact Message Sends a message to the lead's contact. Used for confirmations and follow-ups, and treated as a customer-facing write rather than a routine one.

Funnels

Add Leads To Funnel Places one or more leads into a funnel and stage. Used to file new business into the right pipeline at capture time.
Remove Leads From Funnel Removes specific leads from a funnel by their codes. The targeted alternative to clearing a funnel, and the action an approved cleanup normally uses.
Clear Funnel Removes every lead from a funnel in a single call, returning no body describing what was removed. There is no undo, so agents assemble the evidence and a person authorizes it.

Reference Data

List Origins Returns the account-specific origin codes. Used so a lead is created with an origin this brokerage actually recognizes rather than a free-text guess.
List Task Types Returns the account-specific task type codes. Used when scheduling broker follow-ups and agenda reminders.
List Users Returns the account's user codes for owners and responsible parties. Used to assign leads to real brokers.
Check Health Returns the current server timestamp and is the one route that does not require the API key. Used as a connectivity probe before a batch run commits to anything.

Frequently Asked Questions

What can FlowRunner do with B2Cor CRM?

FlowRunner agents can run Check Health, List Origins, and List Task Types in B2Cor CRM, plus 16 more actions.

Does connecting B2Cor CRM to FlowRunner require OAuth?

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

Can B2Cor CRM trigger a FlowRunner workflow automatically?

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

Start building with B2Cor CRM

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

Start Building Free Talk to us