Embed customer integrations
Deliver Capsule workflows inside your product UI for end users.

Embed Capsule CRM into your SaaS product to sync contacts, opportunities, tasks and attachments, run automations on tag or opportunity changes, and publish in-app integrations for customers.
Deliver Capsule workflows inside your product UI for end users.
Author a flow once and reuse it across customer accounts.
Centralize credentials, permissions and versioned workflows for tenants.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Teams can integrate Capsule to sync parties (contacts and organisations), opportunities, tasks, entries and attachments, trigger workflows on tag or opportunity changes, and subscribe to REST hooks for near‑real‑time events. Use Cyclr to orchestrate multi-step syncs, map custom fields and expose controlled Capsule actions to your customers inside your app.
PRODUCT USE CASES
Turn Capsule records and events into in-app automations and published integrations. Build contact syncs, lead routing, task creation and opportunity-driven campaigns using Capsule parties, opportunities, tasks, entries and REST hooks.
Sync Capsule parties (contacts and organisations) with your application to keep customer records aligned and reduce manual data entry.
Create or update Capsule opportunities from lead forms and trigger downstream task creation or notifications when stage changes.
Create Capsule tasks and entries automatically from support tickets, onboarding events or marketing campaign responses.
ORCHESTRATION
Cyclr sits between your SaaS product and Capsule 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.
Capsule processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore Capsule methods you can orchestrate through Cyclr.
This method allows you to add a Party.
This method allows you to get the details of all Parties that have been updated since the last run.
This method allows you to get the details of all deleted Parties.
This method allows you to get the details of a single Party.
This method allows you to delete a Party.
This method allows you to update a party.
This method allows you to get the details of all Parties deleted since the last run.
This method allows you to get the details of all Parties.
This method allows you to get the details of parties custom fields.
This method allows you to get the details of all organisations.
This method allows you to get the details of a single organisation.
This method allows you to delete a organisation.
This method allows you to add a organisation.
This method allows you to update a organisations.
This method allows you to get the details of all organisations that have been updated since last run.
Gets the custom field definitions for organisations.
This method allows you to add a Task.
This method allows you to get the details of all Tasks.
This method allows you to update a tasks.
This method allows you to delete a Task.
This method allows you to get the details of a single Task.
This method gets contacts that have a matching email address.
This method allows you to update a opportunities.
This method allows you to add a Opportunity.
This method allows you to get the details of all Opportunities.
Add a person or organisation as an additional contact to the Opportunity.
List all opportunties for the specified party.
This method allows you to get the details of all Opportunities that have been updated since last run.
This method allows you to delete a Opportunity.
This method allows you to get the details of a single Opportunity.
This method allows you to delete a contact.
This method allows you to update a contact.
This method allows you to add a contact.
This method allows you to get the details of all contacts.
This method gets contacts that have a matching email address.
This method allows you to get the details of a single contact.
This method gets contacts that have been updated since the last run and have at least one email address. For each email address, a separate contact is returned.
This method allows you to get the details of all contacts who have been updated since the last run.
This method gets contacts that have at least one email address. For each email address, a separate contact is returned.
This method allows you to get the details of all users.
This method allows you to get a list of People in an organisation.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing Capsule integrations in Cyclr.
https://api.capsulecrm.comClient ID, Client Secret (OAuth app); redirect callback to your Cyclr service domain.
Parties (contacts), Opportunities, Tasks, Entries, Attachments, Tags, Custom fields, REST hooks
Offset/page pagination using page and per_page (or perPage) query parameters; use since for incremental syncs and iterate pages until results are exhausted.
Capsule returns X-RateLimit headers; typical limit is 4,000 requests per hour per bearer token; API returns HTTP 429 when exceeded.
IMPLEMENTATION
Capsule supports OAuth 2 Authorization Code for shared apps and personal bearer tokens for quick or internal integrations; include Authorization: Bearer {token} on API requests.
Client ID, Client Secret (OAuth app); redirect callback to your Cyclr service domain.
Register a Capsule OAuth app and add Cyclr’s callback redirect exactly.
COMMON QUESTIONS
You can sync parties (contacts and organisations), create and update opportunities, tasks and entries, upload attachments, manage tags and use REST hooks to trigger near‑real‑time workflows.
Capsule uses OAuth 2 Authorization Code for shared apps and supports personal bearer tokens; Cyclr stores OAuth client ID and secret and uses the returned bearer token in Authorization headers.
Yes. Use a registered Capsule OAuth app and Cyclr’s multi-tenant flows to let each customer authorize their Capsule account independently while reusing centralized orchestration.
Yes. Cyclr can expose selected Capsule actions and reads as managed MCP tools with centralized governance, versioning and tenant-level controls for product teams.
KEEP EXPLORING
Related Marketing connector for customer-facing integration workflows.
Related connectorRelated Marketing connector for customer-facing integration workflows.
Related connectorRelated Marketing connector for customer-facing integration workflows.