Capsule connector icon

Capsule Connector

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.

01

Embed customer integrations

Deliver Capsule workflows inside your product UI for end users.

02

Reusable orchestration

Author a flow once and reuse it across customer accounts.

03

Tenant governance

Centralize credentials, permissions and versioned workflows for tenants.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

What teams can integrate or automate with Capsule

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

Top Use Cases for Capsule Integrations

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.

Two-way contact sync

Sync Capsule parties (contacts and organisations) with your application to keep customer records aligned and reduce manual data entry.

Opportunity-driven automation

Create or update Capsule opportunities from lead forms and trigger downstream task creation or notifications when stage changes.

Task and activity automation

Create Capsule tasks and entries automatically from support tickets, onboarding events or marketing campaign responses.

ORCHESTRATION

How Capsule works with Cyclr

Cyclr sits between your SaaS product and Capsule to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    Capsule

    Capsule processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Capsule methods you can orchestrate through Cyclr.

Parties9

Create Party

Action

This method allows you to add a Party.

List Updated Parties

Action

This method allows you to get the details of all Parties that have been updated since the last run.

List Deleted Parties

Action

This method allows you to get the details of all deleted Parties.

Get Party

Action

This method allows you to get the details of a single Party.

Delete Party

Action

This method allows you to delete a Party.

Update Party

Action

This method allows you to update a party.

List New Deleted Parties

Action

This method allows you to get the details of all Parties deleted since the last run.

List Parties

Action

This method allows you to get the details of all Parties.

List Party Custom Fields

Action

This method allows you to get the details of parties custom fields.

Organisations7

Get Organisations

Action

This method allows you to get the details of all organisations.

Get Organisation

Action

This method allows you to get the details of a single organisation.

Delete Organisation

Action

This method allows you to delete a organisation.

Create Organisation

Action

This method allows you to add a organisation.

Update Organisation

Action

This method allows you to update a organisations.

Get Updated Organisations

Action

This method allows you to get the details of all organisations that have been updated since last run.

List Organisation Custom Fields

Action

Gets the custom field definitions for organisations.

Tasks5

Create Task

Action

This method allows you to add a Task.

Get Tasks

Action

This method allows you to get the details of all Tasks.

Update Task

Action

This method allows you to update a tasks.

Delete Task

Action

This method allows you to delete a Task.

Get Task

Action

This method allows you to get the details of a single Task.

Internal1

Get Contacts By Email (BETA - DO NOT USE)

Action

This method gets contacts that have a matching email address.

Opportunities8

Update Opportunity

Action

This method allows you to update a opportunities.

Create Opportunity

Action

This method allows you to add a Opportunity.

Get Opportunities

Action

This method allows you to get the details of all Opportunities.

Add Additional Party

Action

Add a person or organisation as an additional contact to the Opportunity.

List Party Opportunities

Action

List all opportunties for the specified party.

Get Updated Opportunities

Action

This method allows you to get the details of all Opportunities that have been updated since last run.

Delete Opportunity

Action

This method allows you to delete a Opportunity.

Get Opportunity

Action

This method allows you to get the details of a single Opportunity.

Contacts10

Delete Contact

Action

This method allows you to delete a contact.

Update contact

Action

This method allows you to update a contact.

Create Contact

Action

This method allows you to add a contact.

Get Contacts

Action

This method allows you to get the details of all contacts.

Get Contacts By Email Address

Action

This method gets contacts that have a matching email address.

Get Contact

Action

This method allows you to get the details of a single contact.

Get Updated Contacts With Email Addresses

Action

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.

Get Updated Contacts

Action

This method allows you to get the details of all contacts who have been updated since the last run.

Get Contacts With Email Addresses

Action

This method gets contacts that have at least one email address. For each email address, a separate contact is returned.

Contact CFL (List)

Action

Users1

Get Users

Action

This method allows you to get the details of all users.

Webhooks1

Party Deleted

Webhook

Employees1

List Employees

Action

This method allows you to get a list of People in an organisation.

TECHNICAL DETAILS

Capsule integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Capsule integrations in Cyclr.

API and authentication

API host
https://api.capsulecrm.com
Authentication
OAuth 2 (Authorization Code) and personal bearer tokens
Credentials

Client ID, Client Secret (OAuth app); redirect callback to your Cyclr service domain.

Method categories

Parties (contacts), Opportunities, Tasks, Entries, Attachments, Tags, Custom fields, REST hooks

View vendor API documentation →

Pagination and rate limits

Pagination

Offset/page pagination using page and per_page (or perPage) query parameters; use since for incremental syncs and iterate pages until results are exhausted.

Rate limits

Capsule returns X-RateLimit headers; typical limit is 4,000 requests per hour per bearer token; API returns HTTP 429 when exceeded.

IMPLEMENTATION

Authentication at a glance

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.

Authentication method
OAuth 2 (Authorization Code) and personal bearer tokens
Credential required

Client ID, Client Secret (OAuth app); redirect callback to your Cyclr service domain.

Before you begin:

Register a Capsule OAuth app and add Cyclr’s callback redirect exactly.

View setup guide

COMMON QUESTIONS

Frequently asked 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.