Faster time to market
Pre-built SuiteCRM steps and templates reduce build time.
Build embedded, customer-facing automations that create, update and query SuiteCRM Accounts, Contacts, Leads, Opportunities and Cases from inside your application using reusable Cyclr templates.
Pre-built SuiteCRM steps and templates reduce build time.
Create templates once and deploy per customer account.
Console controls templates, credentials and versions per Account.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Teams can integrate and automate CRM records and workflows between your product and customers’ SuiteCRM instances — Accounts, Contacts, Leads, Opportunities, Cases and custom modules. Use Cyclr to build reusable templates, publish per-customer workflows and run them inside your app with tenant-level configuration and governance. (docs.suitecrm.com)
PRODUCT USE CASES
Publish in-app automations that create Leads from web forms, sync Contacts and Accounts, create Opportunities from orders and log Cases or Notes in SuiteCRM per customer account. Cyclr’s templates scale these workflows across many customer instances. (docs.suitecrm.com)
When a lead submits in your app, create a Lead record in the customer’s SuiteCRM via the Modules API. (docs.suitecrm.com)
On signup, create Account and Contact records in SuiteCRM and map owner and custom fields. (docs.suitecrm.com)
On order completion, create an Opportunity and relate it to the customer Account in SuiteCRM. (docs.suitecrm.com)},{
ORCHESTRATION
Cyclr sits between your SaaS product and SuiteCRM to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
SuiteCRM processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore SuiteCRM methods you can orchestrate through Cyclr.
List tasks modified since last run.
Update an existing task.
Create a new task.
List all tasks.
List tasks created since last run.
Get task by ID.
Get account by ID.
List accounts created since last run.
List all accounts.
List accounts modified since last run.
Create a new account.
Update an existing account.
Update an existing contact.
Create a new contact.
Get contact by ID.
Get contact record by email address. (nb. Full email address required, not a partial search.)
List contacts modified since last run.
List all contacts.
List contacts created since last run.
List all cases created since the last cycle.
Create a new case.
List all cases updated since the last cycle.
Update an existing case.
List all cases.
List leads modified since last run.
Update an existing lead.
List all leads.
Get lead by ID.
List leads created since last run.
Get lead record by email address. (nb. Full email address required, not a partial search.)
Create a new lead.
All fields for the "List Accounts" method.
All fields for the "Update Case" method.
All fields for the "Update Opportunity" method.
All fields for the "List Tasks" method.
All fields for the "Create Account" method.
All fields for the "Get Lead" method.
All fields for the "Update Task" method.
All fields for the "Update Account" method.
All fields for the "Create Lead" method.
Original "Get Module Fields".
All fields for the "Create Case" method.
All fields for the "Update Lead" method.
All fields for the "Get Account" method.
All fields for the "Update Targets" method.
All fields for the "List Opportunities" method.
All fields for the "List Cases" method.
All fields for the "Create Account" method.
All fields for the "List Accounts" method.
All fields for the "List Leads" method.
All fields for the "Get Opportunity" method.
All fields for the "Create Task" method.
All fields for the "Create Opportunity" method.
All fields for the "Get Account" method.
All fields for the "Get task" method.
Logs into SuiteCRM and returns a session id used for subsequent API calls.
Logs the web user out of SuiteCRM and destroys the session.
List all course delegates.
Get course delegate by ID.
List all course delegates added since last run.
List all course delegates modified since last run.
List targets created since last run.
Get target by ID.
List all targets.
Create a new Target.
Update an existing target.
List targets modified since last run.
List all course sales recorded since last run.
List all course sales.
Get a course sale record by ID.
List all course sales modified since last run.
List all course attendance records.
List all course attendance records modified since last run.
List all course attendance records added since last run.
Get course attendance record by ID.
Get opportunity by ID.
List all opportunities.
List opportunities created since last run.
Create a new opportunity.
List opportunities modified since last run.
Update an existing opportunity.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing SuiteCRM integrations in Cyclr.
https://your-crm.example.comDomain; Username; Password; Application Name.
CRUD module records; module metadata; list/filter queries; token management.
V8 JSON API uses page[size] and page[number]; legacy v4.1 uses limit/offset query params. Confirm your instance API version. (docs.suitecrm.com)
No vendor-wide rate limit documented; enforce limits via hosting, API gateway or Cyclr Console policies. (docs.suitecrm.com)
IMPLEMENTATION
Cyclr’s SuiteCRM connector installs with domain, username, password and an application name. SuiteCRM v8 supports OAuth 2.0 (client_credentials and password grants). Confirm the Console authentication option you enable. (community.cyclr.com)
Domain; Username; Password; Application Name.
Use a dedicated API user to avoid “Invalid Session”; only first two emails returned by API. (community.cyclr.com)
COMMON QUESTIONS
It syncs CRM records: Accounts, Contacts, Leads, Opportunities, Cases and custom modules between your app and customer SuiteCRM instances. The connector uses SuiteCRM’s module endpoints to create, update and query records. (docs.suitecrm.com)
It supports username/password session installs (Cyclr setup) and SuiteCRM v8’s OAuth 2.0 (client_credentials and password grants); choose or confirm the Console option during installation. (community.cyclr.com)
Yes. Cyclr installs connectors per Account and publishes reusable templates that run in each customer account with tenant-level credentials and governance. (community.cyclr.com)
Yes. If your Cyclr Console has MCP Servers enabled you can select connectors and expose approved methods as managed MCP tools under Console governance. (community.cyclr.com)
KEEP EXPLORING
Related Crms connector for customer-facing integration workflows.
Related connectorRelated Crms connector for customer-facing integration workflows.
Related connectorRelated Crms connector for customer-facing integration workflows.