Capsule CRM is a customer relationship management platform that helps businesses track contacts, sales opportunities, projects, and tasks in one place. The Capsule API (v2) exposes this data over REST, letting you extract parties, opportunities, pipelines, tasks, and related CRM records for reporting, analytics, and integration.
Power end-to-end data operations for your Capsule CRM API with Nexla. Our bi-directional Capsule CRM connector is purpose-built for Capsule CRM, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Capsule CRM or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Capsule CRM workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Capsule API v2 (https://api.capsulecrm.com/api/v2) with a Capsule Personal Access Token, which Nexla sends as a bearer token in the Authorization header. Personal Access Tokens are tied to the Capsule user who creates them, so Nexla can read and change only what that user can.
To generate a Personal Access Token:
Sign in to your Capsule CRM account.
Open My Preferences > API Authentication Tokens.
Under Personal Access Tokens, generate a new token, and copy its value. Store it securely; it grants access to your Capsule data.
If you plan to use Capsule CRM as a destination, the token must allow writes. Capsule rejects writes made with a read-only token, and operations that need administrator rights made by a non-administrator, with HTTP 403 (Requires additional scope). Several destination templates below, such as creating lost reasons, boards, or stages, need a Capsule administrator. Tokens you no longer need can be revoked from the same API Authentication Tokens page. For details, see Capsule's Authentication guide.
Capsule API rate limits
Capsule allows each user up to 4,000 API requests per hour for bearer-token requests, and returns HTTP 429 once the limit is reached until the window resets. Listing large accounts uses one request per page of 100 records, and each destination record is one request. See Capsule's rate limit documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Capsule Personal Access Token in the API Key field. The field is masked. Enter the token only, without a Bearer prefix; Nexla adds the prefix when it calls the Capsule API.
If your Personal Access Token is compromised, revoke it from My Preferences > API Authentication Tokens in Capsule, generate a new one, and update the credential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by reading the Capsule user that the token belongs to (GET /api/v2/users/current).
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Capsule CRM connector tile, then select the credential that will be used to connect to your Capsule account, and click Next; or, create a new Capsule CRM credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Capsule CRM endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List templates fetch every page: Nexla requests 100 records per page (50 for List Entries for Record) and follows the rel="next" URL in the Link header that Capsule returns until there are no more pages. Capsule calls projects kases in its API, so Record Type settings use parties, opportunities, or kases. Templates that read one record by ID need that ID, which you can get from the matching list or search template.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Capsule CRM data sources can also be manually configured to ingest data from any valid Capsule API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters such as the since filter on parties, opportunities, and projects. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. See the Capsule API v2 reference for the available endpoints.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Capsule CRM data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Capsule CRM destination, and select the Send to Destination option from the menu. Select the Capsule CRM connector from the list of available destination connectors, then select the credential that will be used to connect to your Capsule account, and click Next; or, create a new Capsule CRM credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Capsule CRM endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request, one record at a time. Capsule expects the record to be wrapped in the object's name, for example {"party": {"type": "organisation", "name": "Acme"}} for Create Party; each template below shows the expected shape. ID settings, such as Party ID or Opportunity ID, are fixed on the destination and apply to every record it sends, so update and delete templates act on the same Capsule record for every record in the Nexset. Templates marked Side effect change or remove data in ways that can't be undone from Nexla.
Capsule has no separate endpoint for tagging a record. To add a tag, include "tags": [{"name": "..."}] in an Update Party, Update Opportunity, or Update Project record; to remove one, include {"id": ..., "_delete": true} in the same list.
Create a person or organisation from each record: {"party": {"type": "person"|"organisation", ...}}. Tags, custom fields and tracks can be set in the same body.
Update a person or organisation with each record ({"party": {...}}); omitted fields stay unchanged. Add tags with tags:[{name}], remove with {id, _delete: true}.
Enter the Party ID. Capsule id of the party. Use the List Parties or Search Parties source template to find it.
Create an opportunity from each record: {"opportunity": {"name", "party": {id}, "milestone": {id}, ...}}. Tags and custom fields can be set in the same body.
Update an opportunity with each record ({"opportunity": {...}}); omitted fields stay unchanged. Add tags with tags:[{name}], remove with {id, _delete: true}.
Enter the Opportunity ID. Capsule id of the opportunity. Use the List Opportunities source template to find it.
Add a note from each record: {"entry": {"type": "note", "content", and exactly one of party|opportunity|kase: {id}}}. Notes are the only entry type the API creates.
Side effect: Applies a track definition to a party, opportunity or project and creates its tasks. Record: {"track": {"definition", "party"|"opportunity"|"kase", ...}}.
Create a track definition (task template) from each record: {"trackDefinition": {"description", "captureRule", "direction", "taskDefinitions": [...]}}.
Define a new party, opportunity or project tag from each record: {"tag": {"name", "dataTag": false}}. To tag a record, use Update Party/Opportunity/Project.
Select the Record Type: parties, opportunities, kases (projects are kases in the Capsule API). Default: parties.
Capsule CRM destinations can also be manually configured to send data to any valid Capsule API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks. See Capsule's Writing to the API guide for request formats.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Capsule CRM endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Capsule CRM until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.