SuiteCRM

Connect AI agents to SuiteCRM 7 through its V8 JSON:API. Agents create, update, and delete records in any module, link related records through named relationships, and work with Accounts, Contacts, Leads, Opportunities, Cases, and Tasks via typed operations.

38 actions OAuth available

SuiteCRM website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A paid order lands from the storefront

Agent parses buyer, company, and order total from the payload

List Accounts searches for an existing account by company name

Create Opportunity opens the deal against the matched account

Create Relationship links the buyer contact to the account

Create Task queues a fulfillment follow-up for the deal owner

Ambiguous account matches route to a rep before any record is written

What This Integration Enables

Teams run SuiteCRM because they own it. It is open source, self-hosted, and shaped to their process, usually with custom modules that no stock integration has ever heard of. An automation layer that only reaches Accounts and Contacts misses the point of running SuiteCRM at all. This connector speaks the V8 JSON:API on both levels: typed operations for Accounts, Contacts, Leads, Opportunities, Cases, and Tasks, plus generic Record operations that reach any module by bean name, including the ones your team built. FlowRunner agents create and update records with sparse, field-level writes, link related records through named relationships so nothing lands orphaned, and read filtered lists for reporting. The result is a CRM you own that also maintains itself, with [human-in-the-loop](/concepts/human-in-the-loop/) checkpoints holding the destructive operations, because in a self-hosted system the undo button is your last database backup.

Without FlowRunner

Swivel-chair entry Orders, tickets, and signups get retyped into the CRM by hand

Orphaned records Contacts float unlinked to accounts, so history splits across records

Custom modules left out Automation reaches stock objects and skips the modules your team built

With FlowRunner

Records arrive linked Contacts, accounts, and deals land already related to each other

Full module reach Typed operations for core modules, generic Record operations for the rest

Support visible in the CRM Tickets mirror into Cases next to the customer's account

Use Case Scenarios

Orders become linked CRM records

A paid order fires from [Shopify](/integrations/shopify). The agent checks List Accounts for the company, creates it with Create Account only when no match exists, and opens the deal with Create Opportunity. Create Relationship ties the buyer's Contact to the Account through the account's contacts link, so the record arrives with its history attached rather than as another orphan. Create Task schedules the fulfillment follow-up. When the account match is ambiguous, two similar names or a shared domain, the agent stops and asks a rep in [Slack](/integrations/slack) before writing anything.

Support tickets mirrored into Cases

When a ticket opens in [Zendesk](/integrations/zendesk), the agent mirrors it with Create Case, sets priority and status from the ticket, and relates it to the customer's Account. As the ticket progresses, Update Case keeps the CRM in step, so a rep opening the account before a renewal call sees the open support issues without leaving SuiteCRM. Sales stops getting surprised by problems support has known about for a week.

Custom modules join the automation

A team tracks equipment installations in a custom module. The agent uses List Records against the module's bean name to pull installations due for service, creates follow-up Tasks for the assigned engineers, and updates each record's status with Update Record as visits complete. The module the team built for their process gets the same automation as the stock objects, through the same connector, with no custom code.

Human-in-Loop Highlight

Delete Record, and its typed siblings like Delete Lead, permanently delete from any SuiteCRM module. In a self-hosted system that permanence has a sharper edge: there is no vendor to file a restore ticket with. If the record was not in your last backup, it is gone. So when a quarterly hygiene agent identifies stale leads, imported years ago, never contacted, no linked activity, it does not purge them. It assembles the list with List Leads, posts the exact records with age and last-touch data, and asks the CRM administrator: "214 leads have no activity and no owner since import. Approve the purge, archive them to a spreadsheet first, or leave them?" The agent executes whichever answer comes back. Deletion in a system you own is a decision, not a side effect.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

38 actions

Generic Module Operations

List Records Lists records from any module by bean name, with pagination, sorting, sparse fieldsets, and filtering. The reach into custom modules.
Get Record Retrieves a single record from any module by ID. Used to load full context from custom or stock modules alike.
Create Record Creates a record in any module from an attributes object. Used to write into custom modules no stock integration covers.
Update Record Updates supplied fields on a record in any module. Used for status changes and enrichment anywhere in the CRM.
Delete Record Permanently deletes a record from any module. Kept behind human approval.
Get Related Records Retrieves records related through a named relationship link, such as all Contacts on an Account. Used to walk the graph before decisions.
Create Relationship Links two records through a named relationship. Used so new records land connected to their account, contact, or case.
Delete Relationship Unlinks two records without deleting either. Used to correct wrong associations safely.

Accounts

List Accounts Lists company records with filters. Used as the match check before creating accounts.
Get Account Retrieves a single account. Used to load context before updates.
Create Account Creates a company record with name, type, and industry. Used when new business introduces a new company.
Update Account Updates supplied account fields. Used for enrichment and ownership changes.
Delete Account Permanently deletes an account. Gated behind a human decision.

Contacts

List Contacts Lists person records with filters. Used for match checks and sweeps.
Get Contact Retrieves a single contact. Used before updates or relationship changes.
Create Contact Creates a person record with name and email. Used when orders, forms, or meetings introduce a new person.
Update Contact Updates supplied contact fields. Used to keep person data current.
Delete Contact Permanently deletes a contact. Kept behind approval.

Leads

List Leads Lists leads with filters. Used for routing and hygiene sweeps.
Get Lead Retrieves a single lead. Used before qualification moves.
Create Lead Creates a lead with status and source. Used to capture inbound interest from any channel.
Update Lead Advances lead status or corrects details. Used as qualification progresses.
Delete Lead Permanently deletes a lead. Reserved for human-approved purges.

Opportunities

List Opportunities Lists deals with filters, including by sales stage. Used for pipeline pulls and reporting.
Get Opportunity Retrieves a single deal. Used to confirm state before a stage move.
Create Opportunity Opens a deal with name, amount, and sales stage. Used when orders or qualified leads become real business.
Update Opportunity Advances the sales stage or adjusts amount and close date. Used to keep the pipeline true, including marking deals Closed Won when payment confirms.
Delete Opportunity Permanently deletes a deal. Gated behind sign-off.

Cases

List Cases Lists support tickets with filters. Used to review open issues on an account.
Get Case Retrieves a single case. Used to load ticket context.
Create Case Opens a support case with status, priority, and description. Used to mirror external tickets into the CRM.
Update Case Changes case status or priority. Used to keep mirrored tickets in step with the source system.
Delete Case Permanently deletes a case. Kept behind approval.

Tasks

List Tasks Lists tasks with filters. Used to audit open follow-ups.
Get Task Retrieves a single task. Used before completion or reassignment.
Create Task Creates a task with status, priority, and due date. Used to schedule follow-ups tied to CRM records.
Update Task Marks tasks complete or shifts dates. Used as work finishes.
Delete Task Permanently deletes a task. Gated behind approval.

Frequently Asked Questions

What can FlowRunner do with SuiteCRM?

FlowRunner agents can run List Records, Get Record, and Create Record in SuiteCRM, plus 35 more actions.

Does connecting SuiteCRM to FlowRunner require OAuth?

Yes. SuiteCRM connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can SuiteCRM trigger a FlowRunner workflow automatically?

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

Start building with SuiteCRM

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

Start Building Free Talk to us