FlowRunner
PricingContact
Theme
Start Free

Salesflare

CRM

Connect AI agents to Salesflare CRM. Agents manage contacts, accounts, opportunities, tasks, and tags, log interactions, and read pipelines and stages to keep deal data moving without manual entry.

34 actions API key available
Salesflare website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
Weekly pipeline review kicks off on a Monday morning schedule
List Opportunities pulls every open deal with its stage and owner
Agent flags deals idle well past their stage's normal dwell time
List Stages confirms each proposed move maps to a real stage ID
Proposed moves post to the sales channel with deal context attached
The sales lead approves before Update Opportunity marks anything lost

What This Integration Enables

Teams pick Salesflare because it fills itself in. The whole pitch of the product is that reps should sell, not type. An automation layer around that CRM has one job: extend the same bargain to the rest of the stack. When an order lands in the store, a payment clears, or a meeting gets booked, the record should already exist in Salesflare by the time a rep thinks to look for it. FlowRunner agents work the full surface: contacts, accounts, opportunities, tasks, tags, and the interaction timeline, with pipelines, stages, users, and custom fields readable so every write carries valid IDs. Free-text search and duplicate-safe creation keep the database clean while agents feed it. The judgment calls, which deals to declare dead and which tags to retire, stay with a person through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop/) steps.

Without FlowRunner

Pipeline fiction Dead deals inflate the forecast because nobody closes them out
Manual CRM entry Reps retype orders, payments, and meetings into the CRM after the fact
Silent duplicates The same company enters the CRM three different ways from three channels

With FlowRunner

A forecast you can defend Stale deals surface on a schedule with a decision attached
Records write themselves Orders, payments, and meetings become CRM records on arrival
One record per company Existing accounts get matched before anything new is created

Use Case Scenarios

The Monday pipeline that tells the truth

Every Monday morning, an agent runs List Opportunities across the open pipeline, checks each deal's stage against its last activity, and builds a short list of deals that have gone quiet. It validates every proposed stage move against List Stages, then posts the list to the sales channel in [Slack](/integrations/slack) with owner, value, and idle time per deal. The sales lead approves or overrides each one in the thread. Only then does Update Opportunity move deals or mark them lost. The forecast meeting starts from a pipeline someone has already defended.

Storefront to CRM without a keyboard

A new customer appears in [Shopify](/integrations/shopify). The agent creates the company with Create Account and the person with Create Contact, using the duplicate-safe update option so a returning buyer updates the existing record instead of spawning a twin. An order becomes a deal through Create Opportunity on the buyer's account, and Create Interaction logs the order details on the company timeline where the rep already reads. When a payment settles in [Stripe](/integrations/stripe), Update Opportunity moves the deal to closed-won. A welcome call lands on the rep's list through Create Task.

Meetings that arrive prepared

A prospect books through [Calendly](/integrations/calendly). The agent creates the contact, links them to their company with Link Contact To Account, and opens a preparation task for the assigned rep with the meeting context written into it. The rep gets fifteen minutes of preparation they did not have to assemble, and the CRM shows the meeting happened whether or not anyone remembered to log it.

Human-in-Loop Highlight

Salesflare's Delete Tag does not just remove a label. The API removes the tag from every record it was applied to, permanently, and it cannot be undone. Tags are how this CRM segments accounts, contacts, and opportunities, which means a deleted tag can silently break every workflow and report that filtered on it. So when a tag-hygiene agent finds sprawl, it audits with List Tags, counts usage across records, and stops. It asks the sales lead in Slack: "Tag enterprise-2024 sits on 143 accounts and one active segment filters on it. Merge it into enterprise and delete the old tag, or keep both?" A rename via Update Tag applies everywhere and is safe. The deletion waits for a person, because the segmentation it destroys does not come back.

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

34 actions

Contacts

5
  • List Contacts Lists contacts with pagination and free-text search across names, emails, and companies. Used as the match check before creating anyone.
  • Get Contact Retrieves a contact's full record including positions, tags, and linked account. Used to load context before updates or outreach decisions.
  • Create Contact Creates a contact from a name or email, with duplicate-safe update behavior available. Used when orders, bookings, or forms introduce a new person.
  • Update Contact Changes only the supplied fields. Used to enrich records without overwriting what the CRM already captured.
  • Delete Contact Permanently deletes a contact. Cannot be undone, so agents route it through approval.

Accounts

7
  • List Accounts Lists companies with search by name and domain. Used to resolve the account before any contact or deal write.
  • Get Account Retrieves a company's full record with tags and custom fields. Used before enrichment or merge proposals.
  • Create Account Creates a company with domain, size, and tags. Used when new business introduces a new company.
  • Update Account Updates supplied fields on a company. Used for enrichment and ownership changes.
  • Delete Account Permanently deletes a company. Cannot be undone; kept behind human sign-off.
  • List Account Contacts Lists everyone linked to a company. Used to see the full buying group before outreach.
  • Link Contact To Account Associates a person with a company. Used so new contacts land connected instead of floating.

Opportunities

5
  • List Opportunities Lists deals with filters by account, pipeline, stage, owner, and status. The backbone of pipeline sweeps and forecasts.
  • Get Opportunity Retrieves a deal with value, stage, and close date. Used to confirm state before a move.
  • Create Opportunity Opens a deal with a name, account, and pipeline stage. Used when orders or qualified interest become real business.
  • Update Opportunity Moves a deal between stages, adjusts value, or closes it out. Used wherever the pipeline needs to match reality.
  • Delete Opportunity Permanently deletes a deal. Cannot be undone; agents propose, people approve.

Tasks

5
  • List Tasks Lists to-dos with filters by assignee and account. Used to audit open follow-ups.
  • Get Task Retrieves a task with due date and completion status. Used before reassignment.
  • Create Task Creates a to-do with a due date, linked account, and assignee. Used to turn events into follow-ups reps actually see.
  • Update Task Marks tasks complete or shifts dates and assignees. Used as work gets done.
  • Delete Task Permanently deletes a task. Cannot be undone.

Tags and Interactions

6
  • List Tags Lists every tag with its ID. Used to audit segmentation before writes.
  • Create Tag Creates a tag for segmenting contacts, accounts, and opportunities. Used to establish new segments programmatically.
  • Update Tag Renames a tag everywhere it is used. The safe path for tag cleanup.
  • Delete Tag Permanently removes a tag from every record carrying it. Cannot be undone; gated behind a human decision.
  • List Account Interactions Lists the emails, meetings, and calls logged on a company. Used to review the relationship before a decision.
  • Create Interaction Logs a message or note onto the relevant timelines. Used so agent activity shows up where reps read.

Reference Data

6
  • List Users Lists team members with IDs. Used to assign owners and task recipients correctly.
  • List Pipelines Lists the sales pipelines and their stages. Used to target deal writes at the right pipeline.
  • List Stages Lists pipeline stages with IDs. Used so every stage move is valid before it executes.
  • List Workflows Lists the email workflows configured in the account. Used to check active campaigns before touching their audience.
  • List Custom Fields Lists custom fields per record type. Used to discover writable field names before enrichment.
  • Get Current User Retrieves the profile behind the API key. Used as a connection check.

Frequently Asked Questions

What can FlowRunner do with Salesflare?

FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Salesflare, plus 31 more actions.

Does connecting Salesflare to FlowRunner require OAuth?

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

Can Salesflare trigger a FlowRunner workflow automatically?

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

Start building with Salesflare

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