> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/capsule-crm.md).

# Capsule CRM

Pull Capsule CRM contacts, deals, and activities into Google Sheets or BigQuery. Sync pipeline data without manual exports via Coupler.io.

Capsule CRM is a lightweight customer relationship management tool designed to help small and growing businesses manage contacts, track sales opportunities, and organize tasks and projects. It keeps your team aligned around the relationships and deals that matter most.

Connecting Capsule CRM to Coupler.io lets you pull your CRM data into the tools you already use for reporting, analysis, and automation — without manual exports or copy-pasting.

**Why connect Capsule CRM to Coupler.io?**

* Sync contacts, opportunities, tasks, and pipeline data to Google Sheets, Excel, BigQuery, Looker Studio, or AI tools like ChatGPT, Claude, or Gemini
* Combine data from multiple entities — for example, Join opportunities with pipelines and stages to see the full deal journey in one view
* Track lost reasons and win rates over time with scheduled refreshes
* Use Aggregate transformations to summarize deal values by stage, owner, or pipeline

## Prerequisites

Before you connect, make sure you have:

* An active Capsule CRM account (any paid plan)
* Access to generate an API token in your Capsule CRM account settings
* A Coupler.io account

## Quick start

{% hint style="success" %}
If you want a pipeline performance report, start with the **Opportunities**, **Pipelines**, and **Stages** entities — then use a Join transformation to combine them in a single table.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Get your Capsule CRM API key.** In Capsule CRM, click your profile avatar in the top-right corner and go to **My Preferences**. Select **API Authentication Tokens** and generate a new token. Copy it.
{% endstep %}

{% step %}
**Create a new data flow in Coupler.io.** In your Coupler.io account, click **Add data flow**. Search for **Capsule CRM** and select it as your source.
{% endstep %}

{% step %}
**Enter your API key.** Paste the API token you copied into the API key field and click **Authorize**.
{% endstep %}

{% step %}
**Select an entity.** Choose the data entity you want to import — for example, Opportunities, Parties, or Tasks. Set a start date using the date picker to limit how far back data is pulled.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Perplexity.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your data will appear in the destination you configured.
{% endstep %}
{% endstepper %}

## Capsule CRM data overview

Capsule CRM organizes your business data around contacts, deals, and activities. When you connect it to Coupler.io, you get access to 16 entities covering everything from pipeline structure to individual tasks and custom fields.

## Entities at a glance

| Entity         | What it contains                                                           |
| -------------- | -------------------------------------------------------------------------- |
| Users          | Profile info and roles for your CRM team members                           |
| Parties        | Contacts — people and organizations with address and communication details |
| Tasks          | Individual follow-up items linked to parties, deals, or projects           |
| Employees      | Internal employee records                                                  |
| Projects       | Project records with associated tasks and activities                       |
| Opportunities  | Sales deals with monetary value, owner, stage, and expected close date     |
| Pipelines      | Pipeline definitions — names and stage sequences                           |
| Milestones     | Checkpoint events within projects or opportunities                         |
| Sites          | Digital properties linked to party records                                 |
| Tags           | Categorization labels applied to records                                   |
| Custom fields  | Extra data fields defined by your team                                     |
| Lost reasons   | Reasons recorded when an opportunity is marked as lost                     |
| Boards         | Kanban board configurations for visualizing work                           |
| Categories     | Classification labels for organizing records                               |
| Activity types | Definitions for logged interaction types                                   |
| Stages         | Stage definitions within pipelines or projects                             |

## Key fields by entity

#### Opportunities

| Field           | Description                          |
| --------------- | ------------------------------------ |
| id              | Unique opportunity identifier        |
| name            | Deal name                            |
| value           | Monetary value of the opportunity    |
| currency        | Currency code                        |
| probability     | Estimated likelihood of closing (%)  |
| expectedCloseOn | Expected close date                  |
| closedOn        | Actual close date                    |
| lostReasonId    | ID of the recorded lost reason       |
| owner           | Assigned team member                 |
| stage           | Current pipeline stage               |
| pipeline        | Pipeline this opportunity belongs to |
| createdAt       | Record creation timestamp            |
| updatedAt       | Last update timestamp                |

#### Parties

| Field                | Description                |
| -------------------- | -------------------------- |
| id                   | Unique party identifier    |
| type                 | Person or organization     |
| firstName / lastName | Contact name fields        |
| emailAddresses       | Associated email addresses |
| phoneNumbers         | Associated phone numbers   |
| addresses            | Physical address records   |
| tags                 | Tags applied to this party |
| owner                | Assigned CRM user          |
| createdAt            | Record creation timestamp  |
| updatedAt            | Last update timestamp      |

#### Tasks

| Field       | Description                    |
| ----------- | ------------------------------ |
| id          | Unique task identifier         |
| description | Task details                   |
| dueOn       | Due date                       |
| completedAt | Completion timestamp           |
| status      | Open or completed              |
| owner       | Assigned user                  |
| party       | Linked contact or organization |
| opportunity | Linked opportunity             |
| project     | Linked project                 |

#### Pipelines and Stages

| Field       | Description                       |
| ----------- | --------------------------------- |
| id          | Unique identifier                 |
| name        | Pipeline or stage name            |
| stagesCount | Number of stages in pipeline      |
| probability | Default probability for the stage |
| order       | Stage position in the pipeline    |

#### Lost reasons

| Field | Description       |
| ----- | ----------------- |
| id    | Unique identifier |
| name  | Reason label      |

## Common field combinations

* **Opportunities + Stages + Pipelines** — Join these three entities to get a full picture of where each deal sits and how it maps to your pipeline structure.
* **Opportunities + Lost reasons** — Match `lostReasonId` to the Lost reasons entity to analyze why deals are being lost.
* **Tasks + Parties** — Link tasks to contacts to see follow-up activity per account or person.
* **Parties + Tags + Categories** — Combine these to segment your contact base for targeted analysis.

## Use cases by role

{% tabs %}
{% tab title="Sales teams" %}

* Monitor open opportunities by stage and pipeline to spot bottlenecks
* Track deal value and probability to forecast monthly revenue
* Analyze lost reasons to refine your sales approach
* Use Aggregate transformation in Coupler.io to sum opportunity values by owner or stage
  {% endtab %}

{% tab title="Team managers" %}

* Review task completion rates by user to track team activity
* Compare pipeline velocity — how long deals spend in each stage
* Identify which team members have the most overdue tasks
  {% endtab %}

{% tab title="Operations" %}

* Audit custom field usage to ensure data quality across records
* Export tags and categories to standardize contact segmentation
* Use Append transformation to combine Capsule CRM data with records from other sources
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **start date** parameter controls how far back data is pulled — use the date picker to set this when configuring your data flow.
* **Parties** can represent either a person or an organization; use the `type` field to filter them in your destination.
* **Custom fields** are exported as a separate entity — you'll need to join them with Parties or Opportunities by record ID to enrich your main tables.
* Capsule CRM's API returns data in pages; Coupler.io handles pagination automatically.
* Some fields like `emailAddresses` and `phoneNumbers` may return nested arrays — flatten these in your destination tool if needed.

## Capsule CRM common issues

### Connection issues

<details>

<summary>Authorization fails after entering the API key</summary>

Double-check that you copied the full API token from Capsule CRM without any trailing spaces. Tokens are found under **My Preferences → API Authentication Tokens**. If the token still doesn't work, try regenerating a new one and pasting it fresh.

</details>

<details>

<summary>The data flow returns no data after a successful connection</summary>

Check the **start date** setting in your data flow configuration. If the start date is set too far in the future, or if no records exist within the selected date range, the sync will return empty results. Use the date picker to set an earlier start date and re-run the flow.

</details>

### Missing data

<details>

<summary>Custom fields are not appearing in my destination</summary>

Custom fields are exported as a separate **Custom fields** entity in Coupler.io — they are not automatically merged into Parties or Opportunities. Add the Custom fields entity as an additional source in your data flow and use a Join transformation to connect records by their ID.

</details>

<details>

<summary>Some opportunities or parties are missing from the export</summary>

This is usually caused by the start date filter. If a record was created before the configured start date, it may not be included. Try setting your start date further back using the date picker. Also check whether the missing records have been archived or deleted in Capsule CRM — archived records may not appear in API results.

</details>

<details>

<summary>Lost reasons are not showing text — only IDs appear</summary>

The Opportunities entity stores `lostReasonId` as a reference ID, not the label text. To see reason names, add the **Lost reasons** entity as a second source in your data flow and use a Join transformation to match IDs to names.

</details>

### Permission errors

<details>

<summary>API key works but certain entities return a permission error</summary>

Some Capsule CRM plan tiers restrict access to certain features. If your account doesn't have access to Projects or Boards (for example), those entities will return errors. Check that your Capsule CRM subscription includes the features you're trying to export.

</details>

### Data discrepancies

<details>

<summary>Opportunity values in Coupler.io don't match what I see in Capsule CRM</summary>

Capsule CRM stores opportunity values with a currency code. If your account uses multiple currencies, totals in your destination may not be converted — each row will carry its original currency. Aggregate values by currency first, or handle conversion in your destination tool.

</details>

<details>

<summary>Contact records show duplicate entries</summary>

Capsule CRM allows the same person to exist as both a Person and an Organization party type, or the same contact may have been added more than once. Use the `type` field to separate people from organizations, and check for duplicate entries by matching on email address.

</details>

### Rate limits

<details>

<summary>The sync fails midway with a rate limit error</summary>

Capsule CRM's API enforces rate limits on requests. If you're syncing many large entities simultaneously, you may hit this ceiling. Try splitting your data flow into separate flows per entity, or reduce the number of entities running in a single sync.

</details>

## Capsule CRM FAQ

<details>

<summary>Where do I find my Capsule CRM API key?</summary>

In Capsule CRM, click your profile avatar in the top-right corner and go to **My Preferences**. Under the **API Authentication Tokens** section, you can generate a new token. Copy it and paste it into the API key field in Coupler.io when setting up your data flow.

</details>

<details>

<summary>Can I pull data from multiple Capsule CRM accounts into one destination?</summary>

Yes. Create a separate source connection for each Capsule CRM account within the same data flow, then use the **Append** transformation to stack the data into a single table. This is useful if your organization manages multiple Capsule accounts for different regions or brands.

</details>

<details>

<summary>Which entities should I use to build a sales pipeline report?</summary>

Start with **Opportunities**, **Pipelines**, and **Stages**. Use a Join transformation to connect them — Opportunities carry the deal data, Pipelines provide the pipeline name, and Stages give you readable stage labels. Add **Lost reasons** if you want to analyze why deals didn't close.

</details>

<details>

<summary>Why do I see only IDs in the lost reason column instead of reason names?</summary>

The Opportunities entity stores a `lostReasonId` reference, not the label text. Pull in the **Lost reasons** entity as an additional source and use a Join transformation to replace the ID with the corresponding reason name.

</details>

<details>

<summary>Does Coupler.io sync Capsule CRM custom fields?</summary>

Yes, but custom fields are a separate entity — they won't automatically appear inside your Party or Opportunity rows. Add **Custom fields** as a second source in your data flow and join records by ID to enrich your main tables.

</details>

<details>

<summary>Can I send Capsule CRM data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your Capsule CRM data — contacts, deals, tasks — directly to these tools for analysis, summarization, or generating insights from your CRM data.

</details>

<details>

<summary>What does the start date parameter control?</summary>

The start date limits how far back in time Coupler.io pulls records from Capsule CRM. Use the date picker when configuring your data flow to set the earliest date you want data from. Records created before this date won't be included in the sync.

</details>

<details>

<summary>How do I separate person contacts from organization contacts in my export?</summary>

The **Parties** entity includes a `type` field that indicates whether a record is a `person` or an `organization`. Filter or group by this field in your destination to work with each type separately.

</details>

{% hint style="info" %}
For a full list of available fields per entity, see [Data Overview](#capsule-crm-data-overview). If your sync isn't behaving as expected, check [Common Issues](#capsule-crm-common-issues) for troubleshooting steps. For setup recommendations specific to Capsule CRM, visit [Best Practices](https://docs.coupler.io/sources/category/crm/capsule-crm/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/crm/capsule-crm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
