Access Token

Refresh Token

Capsule CRM

Milestones

Related To

Opportunities

Organisations

People

Related Person/Organisation

Tasks

Users

GET Opportunities

GET Titles

GET Fields

GET Users

Get Organisations

Get Milestones

Get ActivityTypes

Get Pipelines

Get Tasks

Task Categories

Salesforce

HubSpot

Zoho CRM

Microsoft Dynamics 365

Pipedrive

Attio

Xero

Freshsales

Keap

SugarCRM

Outreach

ActiveCampaign

Salesloft

Zendesk

Sage Accounting

Zoho Books

Agile CRM

SalesForce Pardot

SharpSpring

Teamleader

Insightly

Intercom

Copper

Close

Front

Freshdesk

Breezy HR

Affinity

Exact Online

# Realtime Full two-way Sync of Companies

This scenario enables your application to fully sync Companies between your app and any external application in both directions. It handles the initial import/export of Companies and then sends events when a Company is created, updated, or deleted on any side, as close to real-time as possible.

Company fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Companies in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Companies to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Companies

Bi-directional realtime sync of Companies with records deduplication

Mailchimp

NetSuite

GoHighLevel

AWeber

Apollo.io

# Continuous Import of Contacts to Your App

This scenario enables your application to continuously sync Contacts from any external application to your app's API. It handles the initial import of Contacts and keeps them synchronized when a Contact is created, updated, or deleted in the external application.

When receiving Contacts data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Contacts to my App

Import Contacts and receive created/updated or deleted events

Microsoft Sharepoint

Monday

Slack

Jira

Notion

Asana

BambooHR

Github

Clickup

Microsoft Teams

Calendly

Greenhouse Harvest

Trello Connector

Okta

Google Workspace

Lever

Basecamp

Deel

# Continuous Import of Users to Your App

This scenario enables your application to continuously sync Users from any external application to your app's API. It handles the initial import of Users and keeps them synchronized when a User is created, updated, or deleted in the external application.

When receiving Users data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Users to my App

Import Users and receive created/updated or deleted events

# Delete Company

This scenario allows your application to delete a Company from any external application. 
You will pass ID of the Company you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete Company API call**:
   - Call Integration.app REST API or SDK with ID of the Company you want to delete and Integration.app will send the correct request to the external app.


Delete Company

Deletes Company in any external application

Linear

Todoist

Teamwork

HiBob

# Continuous Import of Tasks to Your App

This scenario enables your application to continuously sync Tasks from any external application to your app's API. It handles the initial import of Tasks and keeps them synchronized when a Task is created, updated, or deleted in the external application.

When receiving Tasks data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Tasks to my App

Import Tasks and receive created/updated or deleted events

# Get all Companies

This scenario enables your application to get a complete list of Companies from any external application to your app's API in the same way. 

When receiving Companies data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Companies along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Companies page by page.


Get all Companies

Imports all Companies from any external application to your App.

# Get all Contacts

This scenario enables your application to get a complete list of Contacts from any external application to your app's API in the same way. 

When receiving Contacts data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Contacts along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Contacts page by page.


Get all Contacts

Imports all Contacts from any external application to your App.

# Enrich newly created Contacts

This scenario enables your application to enrich with the new data any newly createad Contacts in external application. 

It handles subscription to the created events and Contact fields mapping from your application's schema to the application-specific schema.

## How It Works
1. **Configuration**:
   - You will setup the schema of fields that you wish to enrich Contact with and configure mapping to our default model.
   - If needed - your customer can customize this mapping based on their specific setup or even custom fields

2. **Enable receiving of Contact created events**:
   - Enable subscription via a single API or SDK call to continuously receive created events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

2. **React to created Contacts**:
   - Integration.app flow will be launched when new Contact is created
   - It will send existing data to your app API, so you can decide how to enrich. Your API will return enriched data.
   - Integration.app will send enriched data to the external application mapped to the supported format based on the configuration above


Continuously Enrich Contacts

Receive all newly created contacts, send it to your app API to enrich with the new data and update contact back

# Create User

This scenario allows your application to create a User in any external application in the same way. 
You will pass User fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create User with and configure mapping to our default model

2. **Create User API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your User data into a format compatible with the selected external application.
   - It then makes an API call to create the User in that specific application.


Create User

# Create Company

This scenario allows your application to create a Company in any external application in the same way. 
You will pass Company fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create Company with and configure mapping to our default model

2. **Create Company API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Company data into a format compatible with the selected external application.
   - It then makes an API call to create the Company in that specific application.


Create Company

Creates Company in any external application

# Continuous Import of Companies to Your App

This scenario enables your application to continuously sync Companies from any external application to your app's API. It handles the initial import of Companies and keeps them synchronized when a Company is created, updated, or deleted in the external application.

When receiving Companies data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Companies to my App

Import Companies and receive created/updated or deleted events

# Continuous Import of Deals to Your App

This scenario enables your application to continuously sync Deals from any external application to your app's API. It handles the initial import of Deals and keeps them synchronized when a Deal is created, updated, or deleted in the external application.

When receiving Deals data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Deals to my App

Import Deals and receive created/updated or deleted events

# Delete Contact

This scenario allows your application to delete a Contact from any external application. 
You will pass ID of the Contact you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete Contact API call**:
   - Call Integration.app REST API or SDK with ID of the Contact you want to delete and Integration.app will send the correct request to the external app.


Delete Contact

Deletes Contact in any external application

# Create Deal

This scenario allows your application to create a Deal in any external application in the same way. 
You will pass Deal fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create Deal with and configure mapping to our default model

2. **Create Deal API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Deal data into a format compatible with the selected external application.
   - It then makes an API call to create the Deal in that specific application.


Create Deal

# Create Contact

This scenario allows your application to create a Contact in any external application in the same way. 
You will pass Contact fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create Contact with and configure mapping to our default model

2. **Create Contact API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Contact data into a format compatible with the selected external application.
   - It then makes an API call to create the Contact in that specific application.


Create Contact

Creates Contact in any external application

# Delete Deal

This scenario allows your application to delete a Deal from any external application. 
You will pass ID of the Deal you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete Deal API call**:
   - Call Integration.app REST API or SDK with ID of the Deal you want to delete and Integration.app will send the correct request to the external app.


Delete Deal

# Update Task

This scenario allows your application to update a Task in any external application in the same way. 
You will pass  ID of the Task you want to update and Task fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update Task with and configure mapping to our default model

2. **Create Task API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Task data into a format compatible with the selected external application.
   - It then makes an API call to update the Task in that specific application.


Update Task

# Update Deal

This scenario allows your application to update a Deal in any external application in the same way. 
You will pass  ID of the Deal you want to update and Deal fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update Deal with and configure mapping to our default model

2. **Create Deal API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Deal data into a format compatible with the selected external application.
   - It then makes an API call to update the Deal in that specific application.


Update Deal

# Get all Deals

This scenario enables your application to get a complete list of Deals from any external application to your app's API in the same way. 

When receiving Deals data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Deals along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Deals page by page.


Get all Deals

Imports all Deals from any external application to your App.

# Delete Task

This scenario allows your application to delete a Task from any external application. 
You will pass ID of the Task you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete Task API call**:
   - Call Integration.app REST API or SDK with ID of the Task you want to delete and Integration.app will send the correct request to the external app.


Delete Task

# Enrich newly created Deals

This scenario enables your application to enrich with the new data any newly createad Deals in external application. 

It handles subscription to the created events and Deal fields mapping from your application's schema to the application-specific schema.

## How It Works
1. **Configuration**:
   - You will setup the schema of fields that you wish to enrich Deal with and configure mapping to our default model.
   - If needed - your customer can customize this mapping based on their specific setup or even custom fields

2. **Enable receiving of Deal created events**:
   - Enable subscription via a single API or SDK call to continuously receive created events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

2. **React to created Deals**:
   - Integration.app flow will be launched when new Deal is created
   - It will send existing data to your app API, so you can decide how to enrich. Your API will return enriched data.
   - Integration.app will send enriched data to the external application mapped to the supported format based on the configuration above


Continuously Enrich Deals

Receive all newly created deals, send it to your app API to enrich with the new data and update deal back

# Create Task

This scenario allows your application to create a Task in any external application in the same way. 
You will pass Task fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create Task with and configure mapping to our default model

2. **Create Task API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Task data into a format compatible with the selected external application.
   - It then makes an API call to create the Task in that specific application.


Create Task

# Update Contact

This scenario allows your application to update a Contact in any external application in the same way. 
You will pass  ID of the Contact you want to update and Contact fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update Contact with and configure mapping to our default model

2. **Create Contact API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Contact data into a format compatible with the selected external application.
   - It then makes an API call to update the Contact in that specific application.


Update Contact

Updates Contact in any external application

# Realtime Full two-way Sync of Tasks

This scenario enables your application to fully sync Tasks between your app and any external application in both directions. It handles the initial import/export of Tasks and then sends events when a Task is created, updated, or deleted on any side, as close to real-time as possible.

Task fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Tasks in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Tasks to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Tasks

Bi-directional realtime sync of Tasks with records deduplication

# Enrich newly created Companies

This scenario enables your application to enrich with the new data any newly createad Companies in external application. 

It handles subscription to the created events and Company fields mapping from your application's schema to the application-specific schema.

## How It Works
1. **Configuration**:
   - You will setup the schema of fields that you wish to enrich Company with and configure mapping to our default model.
   - If needed - your customer can customize this mapping based on their specific setup or even custom fields

2. **Enable receiving of Company created events**:
   - Enable subscription via a single API or SDK call to continuously receive created events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

2. **React to created Companies**:
   - Integration.app flow will be launched when new Company is created
   - It will send existing data to your app API, so you can decide how to enrich. Your API will return enriched data.
   - Integration.app will send enriched data to the external application mapped to the supported format based on the configuration above


Continuously Enrich Companies

Receive all newly created companies, send it to your app API to enrich with the new data and update company back

# Get all Tasks

This scenario enables your application to get a complete list of Tasks from any external application to your app's API in the same way. 

When receiving Tasks data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Tasks along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Tasks page by page.


Get all Tasks

Imports all Tasks from any external application to your App.

# Update User

This scenario allows your application to update a User in any external application in the same way. 
You will pass  ID of the User you want to update and User fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update User with and configure mapping to our default model

2. **Create User API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your User data into a format compatible with the selected external application.
   - It then makes an API call to update the User in that specific application.


Update User

# Realtime Full two-way Sync of Deals

This scenario enables your application to fully sync Deals between your app and any external application in both directions. It handles the initial import/export of Deals and then sends events when a Deal is created, updated, or deleted on any side, as close to real-time as possible.

Deal fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Deals in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Deals to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Deals

Bi-directional realtime sync of Deals with records deduplication

# Delete User

This scenario allows your application to delete a User from any external application. 
You will pass ID of the User you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete User API call**:
   - Call Integration.app REST API or SDK with ID of the User you want to delete and Integration.app will send the correct request to the external app.


Delete User

# Update Company

This scenario allows your application to update a Company in any external application in the same way. 
You will pass  ID of the Company you want to update and Company fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update Company with and configure mapping to our default model

2. **Create Company API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Company data into a format compatible with the selected external application.
   - It then makes an API call to update the Company in that specific application.


Update Company

Updates Company in any external application

# Get all Users

This scenario enables your application to get a complete list of Users from any external application to your app's API in the same way. 

When receiving Users data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Users along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Users page by page.


Get all Users

Imports all Users from any external application to your App.

# Realtime Full two-way Sync of Users

This scenario enables your application to fully sync Users between your app and any external application in both directions. It handles the initial import/export of Users and then sends events when a User is created, updated, or deleted on any side, as close to real-time as possible.

User fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Users in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Users to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Users

Bi-directional realtime sync of Users with records deduplication

# Realtime Full two-way Sync of Contacts

This scenario enables your application to fully sync Contacts between your app and any external application in both directions. It handles the initial import/export of Contacts and then sends events when a Contact is created, updated, or deleted on any side, as close to real-time as possible.

Contact fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Contacts in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Contacts to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Contacts

Bi-directional realtime sync of Contacts with records deduplication

# Task Unified API

This scenario contains the complete Tasks Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Tasks while also receiving notifications on creation, updates, and deletions of Tasks in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Tasks Unified API

# Deal Unified API

This scenario contains the complete Deals Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Deals while also receiving notifications on creation, updates, and deletions of Deals in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Deals Unified API

# Contact Unified API

This scenario contains the complete Contacts Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Contacts while also receiving notifications on creation, updates, and deletions of Contacts in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Contacts Unified API

# User Unified API

This scenario contains the complete Users Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Users while also receiving notifications on creation, updates, and deletions of Users in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Users Unified API

# Company Unified API

This scenario contains the complete Companies Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Companies while also receiving notifications on creation, updates, and deletions of Companies in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Capsule CRM API Integration Profile

Data Collections

Operations

Integration Scenarios