Exact Spotter

Connect AI agents to Exact Spotter, a lead qualification and pre-sales engagement platform from Exact Sales. Agents create and route leads, manage the pre-sales funnel, and read the meetings booked between pre-sales and sales.

33 actions API key available

Platform Documentation ↗

A web form submission arrives from another system, because Exact Spotter has no FlowRunner trigger of its own

List Leads with an OData filter on the company or contact confirms whether this prospect already exists in the funnel

Create Lead registers the prospect with its source, sub source, and industry matched against the account's configured names

Create Person attaches the contact as the lead's main contact, and Transfer Lead moves it to the SDR who owns that segment

Add Lead Timeline Note records where the lead came from and what it asked for, on behalf of a named user

Create Task schedules the first follow up so the lead does not sit in a stage with nobody responsible for it

When the SDR proposes discarding the lead, the reason and the evidence go to the pre sales manager before the loss is written

What This Integration Enables

Exact Spotter is a pre sales platform, which is a narrower and more useful thing than a CRM. It exists for the stage between a lead arriving and a meeting being worth a closer's time: the SDR's funnel, the qualification questions, the discard reasons, the transfer to a rep. The API reflects that. It is an OData v4 service where reads come back in the standard envelope and writes post to dedicated action collections such as LeadsAdd, LeadsUpdate, and LeadsLost, which is a design that makes lifecycle transitions explicit rather than implied by a field update.

For an agent, the payoff is that OData query options are exposed directly. List Leads, List Persons, List Organizations, List Products, List Tasks, List Activities Done, and List Meetings all accept filter, top, skip, and orderby, so a flow can ask for the leads in funnel 5 registered since Monday sorted newest first without pulling the account and filtering in memory. Reference values are matched by their configured names rather than by numeric ids for source, sub source, industry, and discard reason, which means a flow writes what a human would recognise in the interface. Funnels and task activity types use numeric ids instead.

Two things this connector does not do, stated plainly because the alternative is a page that promises them. It reads meetings but does not book them: List Meetings retrieves meetings already scheduled between pre sales and sales reps, and there is no create or update meeting action. And its custom field surface is schema management, not data entry. List Custom Fields returns the fields configured for leads with their keys, types, options, and required flags, and Add Custom Field creates a new one, but neither writes a value onto a particular lead. Qualification answers are captured in the platform; the API side of this connector defines the questions and reads the funnel.

There are also no triggers, and the Webhooks group is not a substitute for one. List Webhooks, Create Webhook, and Delete Webhook manage subscriptions inside Exact Spotter that post to a notification URL you choose. Nothing in that group creates a FlowRunner trigger or causes FlowRunner to receive an event. A native trigger is deferred because the delivered payload shape is not documented from a primary source. Until then, the honest patterns are a scheduled List Leads with an OData filter on registerDate, or your own HTTP endpoint registered through Create Webhook and parsed downstream.

Without FlowRunner

Intake is retyped A form lands in an inbox and someone rekeys the company, source, and industry into Spotter

Duplicates surface late The same company enters twice from two campaigns and two SDRs work it in parallel

Loss reasons are guesses Discard reasons get picked to clear the queue, and later reporting treats them as findings

With FlowRunner

Intake is a write, not a retype Create Lead carries the source and industry the campaign already knew

Duplicates are caught at the door Duplicity validation rejects a lead whose company or contact already exists

A loss is attributable Discard Lead runs under a named active user, with the evidence reviewed before it is recorded

Use Case Scenarios

Inbound capture that arrives already routed

A form submission lands from a campaign page. Before writing anything, the agent calls List Leads with an OData filter on the company name to check whether this account is already in someone's funnel, because the expensive failure here is not a missing lead, it is two SDRs calling the same company in the same week. If the account is new, Create Lead registers it with duplicity validation enabled and email validation on, so Spotter itself rejects a collision the filter missed and refuses a malformed address. Create Person attaches the contact with main contact set true. Transfer Lead then moves it to the SDR who owns that industry, by email, and Add Lead Timeline Note records the campaign, the form answers, and the landing page, attributed to a real user id. The SDR opens a lead that already knows where it came from.

Keeping a second system honest without a trigger

Spotter does not wake a flow up, so a scheduled read does the work. Every twenty minutes an agent calls List Leads filtered on registerDate greater than the last watermark, ordered by registerDate desc, and reconciles the page against RD Station so marketing sees which of its leads survived qualification and which did not. Leads that reached a later funnel stage get their status written back; leads that were discarded get their reason written back. The value is not the sync itself, it is that the marketing team stops arguing about lead quality from two different datasets. A flow can also call List Sellers and List SDRs to keep the owner mapping current, because rep turnover is the quiet reason routing rules rot.

The follow up that actually gets scheduled

Change Lead Funnel Stage moves a lead forward, and the moment it moves is the moment work should be created. An agent watching stage changes calls Create Task with the activity type id for a call, links the contact person, and sets a reminder, then posts to Slack telling the assigned SDR what changed and when the task is due. When the outcome is a win, Mark Lead as Won records the sales date and the closing rep's email, and a second flow appends the deal to a Google Sheets revenue tab for finance. The stage change and the task stop being two separate acts of discipline that depend on someone remembering.

Human-in-Loop Highlight

Discard Lead is the action worth stopping on, and not because it is destructive in the ordinary sense. It requires two things the platform takes seriously: a reason that must match a discard reason configured in the account, and a user email belonging to an active user. Spotter is asking who decided this and why, and then it keeps the answer. Every report on where the funnel leaks, every review of which sources are worth the spend, every argument between marketing and pre sales about lead quality is later settled with that field. An agent discarding at volume does not just remove leads, it manufactures qualification history under a named colleague's account, and once a few hundred rows say "no budget" the account believes it. That is the failure to design against, and it is different from the ordinary risk of a delete. Delete Person, Delete Product, and Delete Task remove records permanently and cannot be undone, but they destroy data everyone knows is gone; a wrong discard reason quietly becomes evidence. So the agent prepares the case and stops. It calls Get Lead for the full record, List Tasks filtered by leadId to show what was actually attempted, and List Activities Done for what was completed, then asks the pre sales manager: "Lead 8823, Metalurgica Sul, in Contato Inicial for 21 days. Three calls logged, no answer, one email opened twice. SDR proposes discard reason 'Sem interesse'. The opens suggest not uninterested, just unreachable by phone. Discard under that reason, or transfer to the inside team for an email sequence?" Framing this as human-in-the-loop is what lets the agent handle the hundreds of routine creates, notes, and stage moves without anyone reviewing them.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

33 actions

Leads

List Leads Retrieves a page of leads with OData system query options for filtering, sorting, field selection, and pagination. Use filter with an expression such as funnelId eq 5, orderby to sort by registerDate desc, and top or skip to page. This is the read that replaces a trigger on a scheduled reconciliation.
Get Lead Retrieves a single lead by its numeric identifier, returning the full record including source, funnel, stage, contact phones, and address fields. The confirmation read before any status-changing write.
Create Lead Creates a new lead. Only the name is required. Source, sub source, and industry reference the account's configured values by name rather than by id. Set duplicity validation to reject a lead whose company or contact already exists, and validate email to reject invalid addresses, which pushes both checks into the platform instead of into your flow.
Update Lead Updates an existing lead by its numeric identifier, changing only the fields provided. Source, sub source, and industry are again matched against configured values by name.
Discard Lead Discards, meaning loses, a lead with a discard reason. The reason must match a reason configured in the account and the user email must belong to an active user, so the platform attributes the loss to a person. This is the action whose accumulated output becomes the account's view of why deals do not happen.
Mark Lead as Won Marks a lead as won, optionally recording the sales date and the email of the sales rep who closed it. Set ignore sales rep to true to close without assigning one.
Transfer Lead Transfers one or more leads to a pre sales rep (SDR) by email, optionally within a specific group. Takes the identifiers of the leads to move, so it doubles as the bulk reassignment path when territory or headcount changes.
Change Lead Funnel Stage Moves a lead to a different stage within its funnel. The stage identifier must belong to that lead's funnel, so a flow that hardcodes stage ids across funnels will fail loudly rather than silently misfile the lead.
Add Lead Timeline Note Adds a free text note to a lead's timeline on behalf of a user, whose identifier must belong to an active user. The place to record why an automated decision was made, so the SDR who picks the lead up is not reading an unexplained stage change.

Contacts

List Persons Retrieves a page of contact persons with the full OData query options. Filter by leadId to list the contacts belonging to one lead.
Create Person Creates a contact person linked to a lead. Provide the lead identifier and the contact details, and set main contact to true to make this the lead's primary contact.
Update Person Updates an existing contact person by numeric identifier, changing only the fields supplied.
Delete Person Permanently removes a contact person by numeric identifier. This cannot be undone, and it takes the contact out from under any lead that referenced them.

Organizations

List Organizations Retrieves a page of organizations with OData filtering, sorting, field selection, and pagination.
Create Organization Creates an organization. Only the name is required. Set duplicity validation to reject one whose name or document already exists, and supply the user email to link the record to a registering user.
Update Organization Updates an existing organization by numeric identifier, changing only the fields provided.

Products

List Products Retrieves a page of products from the account catalog with the standard OData query options.
Create Product Creates a product in the account catalog with a name and a monetary value.
Update Product Updates an existing product by numeric identifier, changing only the fields provided.
Delete Product Permanently removes a product from the account catalog by numeric identifier. This cannot be undone.

Tasks and Activities

List Tasks Retrieves a page of tasks, meaning activities, with OData query options. Filter by leadId to list the tasks belonging to one lead, which is how a flow shows what has actually been attempted before proposing a discard.
Create Task Creates a task for a lead. The activity type identifier determines the kind of task, optionally linking a contact person and scheduling a reminder notification. The natural companion to a funnel stage change.
Update Task Updates an existing task by numeric identifier, changing only the fields supplied.
Delete Task Permanently removes a task by numeric identifier. This cannot be undone.
List Activities Done Retrieves a page of completed activities with the standard OData query options. The record of what was done rather than what was scheduled.

Meetings

List Meetings Retrieves a page of meetings already scheduled between pre sales and sales reps, with OData filtering, sorting, field selection, and pagination. This is a read. The connector has no action that books a meeting, so a flow reports on the handoff calendar rather than filling it.

Custom Fields

List Custom Fields Retrieves the custom fields configured for leads, including each field's key, type, options, and whether it is required or API only. Use it to discover the qualification schema a flow must respect.
Add Custom Field Creates a new custom field for leads. The field type controls the input, and Single Choice and Multiple Choice fields take a list of allowed option values. This defines a field; it does not set that field's value on a particular lead.

Webhooks

List Webhooks Retrieves the webhooks currently registered for the account, including each notification URL. Useful for auditing which external endpoints are already receiving Spotter events.
Create Webhook Registers a webhook that posts to a URL you supply when the selected event occurs. The endpoint is yours, and registering it does not create a FlowRunner trigger or cause FlowRunner to receive the event.
Delete Webhook Removes a registered webhook by its notification URL. This cannot be undone, and the flow behind that endpoint goes quiet without further warning.

Users

List Sellers Retrieves the sales reps configured in the account with name, email, and active status. Read it before assigning, because Mark Lead as Won and Transfer Lead both require an active user.
List SDRs Retrieves the pre sales reps configured in the account with name, email, and active status. The mapping a routing flow needs to keep current as the team changes.

Frequently Asked Questions

What can FlowRunner do with Exact Spotter?

FlowRunner agents can run List Leads, Get Lead, and Create Lead in Exact Spotter, plus 30 more actions.

Does connecting Exact Spotter to FlowRunner require OAuth?

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

Can Exact Spotter trigger a FlowRunner workflow automatically?

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

Start building with Exact Spotter

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

Start Building Free Talk to us