--- title: Capsule API Integration on Truto slug: capsule category: CRM canonical: "https://truto.one/integrations/detail/capsule/" --- # Capsule API Integration on Truto **Category:** CRM **Status:** Generally available ## Unified APIs ### Unified CRM API - **Accounts** — The accounts represent a company in a CRM. - **Contacts** — The contacts represent an existing point of contact at a company in a CRM. - **Engagement Types** — The engagement types represent an interaction activity in a CRM. - **Engagements** — The engagements represent an interaction noted in a CRM. - **Fields** — The fields of entities in a CRM. - **Notes** — The notes represent a note on another object in a CRM. - **Opportunities** — The opportunities represent an opportunity in a CRM. - **Pipelines** — - **Projects** — - **Stages** — The stages represent a stage of an opportunity in a CRM. - **Tasks** — The tasks represent a task in a CRM. - **Users** — The users represent a user in a CRM. ### Unified User Directory API - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Capsule account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Capsule.** The Proxy API is a 1-to-1 mapping of the Capsule API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Auto-populate proposals with CRM data** — Proposal and e-signature platforms can pull Accounts, Contacts, and Opportunity details from Capsule to auto-fill documents, then update the deal Stage to 'Won' and log the signed contract as a Note — eliminating manual data entry for SMB sales teams. - **Enrich support tickets with CRM context** — Helpdesk and ticketing SaaS products can look up incoming customers against Capsule Contacts, surface active Opportunities and custom Fields in the support UI, and create follow-up Tasks assigned to the right account owner — all without the agent leaving your app. - **Log call activity back to the CRM timeline** — Cloud telephony and sales engagement platforms can sync Contacts for caller ID, then push call recordings, duration, and outcomes as Engagements or Notes on the Capsule contact record so the CRM stays the single source of truth. - **Sync marketing engagement signals into Capsule** — Marketing automation tools can pull segmented Contact lists using Capsule's custom Fields and tags, then write campaign events like email opens and link clicks back as Engagements — giving Capsule users a 360-degree view of lead activity. - **Trigger onboarding workflows from closed deals** — Client onboarding and project management SaaS can monitor Capsule Pipelines and Stages, automatically spinning up Projects and Tasks in Capsule when an Opportunity moves to a 'Closed/Won' stage, ensuring nothing falls through the cracks. ## What you can build - **Bi-directional contact and account sync** — Keep Contacts and Accounts in your product continuously in sync with Capsule, including custom Fields and tags, so your users never work with stale CRM data. - **Pipeline-aware workflow triggers** — Read Opportunities, Pipelines, and Stages from Capsule to trigger actions in your product — like generating an invoice or launching an onboarding sequence — when a deal reaches a specific stage. - **Automatic activity timeline logging** — Push events from your product — support tickets resolved, contracts signed, calls completed — into Capsule as Notes or Engagements so the CRM timeline is always complete. - **In-app CRM task creation** — Let your users create Capsule Tasks directly from your product's UI, assigned to the right User, so follow-ups identified in your app are tracked where the sales team actually works. - **Custom field-driven segmentation** — Read Capsule's custom Fields to power audience filters, lead scoring, or conditional logic inside your product without requiring users to re-enter segmentation criteria. - **User directory lookup for assignment and routing** — Use the Unified User Directory API to pull Capsule Users into your product for owner-based routing, task assignment, and permission mapping. ## FAQs ### How do end users authenticate their Capsule accounts through Truto? Capsule supports OAuth 2.0 for third-party integrations. Truto handles the full OAuth flow — token exchange, storage, and refresh — so your end users connect their Capsule account with a single click and you never manage credentials directly. ### Which Capsule data models are available through Truto's Unified CRM API? Truto's Unified CRM API maps Capsule data to the following standardized models: Accounts, Contacts, Engagement Types, Engagements, Fields, Notes, Opportunities, Pipelines, Projects, Stages, Tasks, and Users. A Unified User Directory API is also available for Users. ### Does Truto handle Capsule's API pagination and rate limits automatically? Yes. Truto abstracts away Capsule's pagination logic and respects its rate limits behind the scenes, so you can request full data sets without writing cursor or throttle management code. ### Can I read and write Capsule custom fields through the Unified API? Yes. Capsule relies heavily on custom fields and tags for segmentation. The Fields model in Truto's Unified CRM API lets you read custom field definitions and their values on Contacts and Accounts, giving you access to the same segmentation your users rely on inside Capsule. ### Are Capsule-specific tools available in Truto today? Capsule is currently available through Truto's Unified CRM API and Unified User Directory API. Additional Capsule-specific tools or proxy API access can be built on request if you need functionality beyond the unified models. ### How fresh is the data when reading from Capsule through Truto? By default, Truto makes real-time API calls to Capsule when you query a unified endpoint, so data is as fresh as the source. Truto also supports scheduled syncs and caching strategies if you prefer to reduce API calls and work with periodically refreshed data.