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

  • 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

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.

Last updated

Was this helpful?