Microsoft Dynamics 365

Get Business Process Flow Instances for a lead or opportunity

Get Business Process Flow Instances

Salesforce

HubSpot

Zoho CRM

Pipedrive

Freshsales

Keap

SugarCRM

Outreach

Xero

ActiveCampaign

Capsule CRM

Salesloft

Agile CRM

SalesForce Pardot

SharpSpring

Teamleader

Insightly

Zendesk

Sage Accounting

Attio

Copper

Intercom

Zoho Books

Front

Close

Freshdesk

Breezy HR

Affinity

Exact Online

Mautic

# 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

AWeber

Apollo.io

GoHighLevel

Ontraport

Jobnimbus

# 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

Asana

Github

Notion

Clickup

Microsoft Teams

Greenhouse Harvest

Calendly

BambooHR

Basecamp

Okta

Deel

Lever

Google Workspace

Microsoft Entra ID

# 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

# Create Note

This scenario allows your application to create a Note in any external application in the same way. 
You will pass Note 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 Note with and configure mapping to our default model

2. **Create Note 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 Note data into a format compatible with the selected external application.
   - It then makes an API call to create the Note in that specific application.


Create Note

# 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

Google Calendar

# Get all Activities

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

When receiving Activities 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 Activities along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Activities page by page.


Get all Activities

Imports all Activities from any external application to your App.

Marketo

# Update Campaign

This scenario allows your application to update a Campaign in any external application in the same way. 
You will pass  ID of the Campaign you want to update and Campaign 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 Campaign with and configure mapping to our default model

2. **Create Campaign 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 Campaign data into a format compatible with the selected external application.
   - It then makes an API call to update the Campaign in that specific application.


Update Campaign

Updates Campaign in any external application

# Update Activity

This scenario allows your application to update a Activity in any external application in the same way. 
You will pass  ID of the Activity you want to update and Activity 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 Activity with and configure mapping to our default model

2. **Create Activity 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 Activity data into a format compatible with the selected external application.
   - It then makes an API call to update the Activity in that specific application.


Update Activity

Updates Activity in any external application

# Update Lead

This scenario allows your application to update a Lead in any external application in the same way. 
You will pass  ID of the Lead you want to update and Lead 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 Lead with and configure mapping to our default model

2. **Create Lead 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 Lead data into a format compatible with the selected external application.
   - It then makes an API call to update the Lead in that specific application.


Update Lead

Trello Connector

Todoist

Teamwork

HiBob

Linear

Recruitee

# 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

# Continuous Import of Leads to Your App

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

When receiving Leads 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 Leads to my App

Import Leads and receive created/updated or deleted events

# Get all Notes

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

When receiving Notes 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 Notes along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Notes page by page.


Get all Notes

Imports all Notes from any external application to your App.

# 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.

# Update Meeting

This scenario allows your application to update a Meeting in any external application in the same way. 
You will pass  ID of the Meeting you want to update and Meeting 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 Meeting with and configure mapping to our default model

2. **Create Meeting 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 Meeting data into a format compatible with the selected external application.
   - It then makes an API call to update the Meeting in that specific application.


Update Meeting

Updates Meeting in any external application

Google Meet

# Continuous Import of Meetings to Your App

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

When receiving Meetings 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 Meetings to my App

Import Meetings and receive created/updated or deleted events

# Delete Note

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

## How It Works

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


Delete Note

# Create Contact Activity

This scenario allows your application to add a new Activity to the Contact in any external application in the same way. 
You will pass Contact and Activity data that will be used to find (create if not found) contact and then attach a new activity to it.
This scenario can work with data 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 Activity / Contact with and configure mapping to our default model

2. **Run Create Contact Activity Flow**:
   - 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 data into a format compatible with the selected external application.
   - It then makes an API calls to find the Contact by Email and creates a new one if not found based on the field mapping from Configuration step.
   - After Integration.app will create a new Activity with the data you provided and attach it to existing contact


Create Contact Activity

Create a new activity for a contact found by email

# Create Lead

This scenario allows your application to create a Lead in any external application in the same way. 
You will pass Lead 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 Lead with and configure mapping to our default model

2. **Create Lead 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 Lead data into a format compatible with the selected external application.
   - It then makes an API call to create the Lead in that specific application.


Create Lead

# Enrich newly created Leads

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

It handles subscription to the created events and Lead 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 Lead 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 Lead 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 Leads**:
   - Integration.app flow will be launched when new Lead 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 Leads

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

# 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.

Gmail

Microsoft Outlook

Whatsapp

# Realtime Full two-way Sync of Emails

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

Email 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 Emails 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 Emails 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 Emails

Bi-directional realtime sync of Emails with records deduplication

# Create Email

This scenario allows your application to create a Email in any external application in the same way. 
You will pass Email 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 Email with and configure mapping to our default model

2. **Create Email 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 Email data into a format compatible with the selected external application.
   - It then makes an API call to create the Email in that specific application.


Create Email

Creates Email in any external application

# Get all Emails

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

When receiving Emails 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 Emails along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Emails page by page.


Get all Emails

Imports all Emails from any external application to your App.

Woosender

# 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

# Get all Leads

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

When receiving Leads 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 Leads along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Leads page by page.


Get all Leads

Imports all Leads from any external application to your App.

# Continuous Import of Campaigns to Your App

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

When receiving Campaigns 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 Campaigns to my App

Import Campaigns and receive created/updated or deleted events

# Delete Campaign

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

## How It Works

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


Delete Campaign

Deletes Campaign in any external application

# Create Activity

This scenario allows your application to create a Activity in any external application in the same way. 
You will pass Activity 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 Activity with and configure mapping to our default model

2. **Create Activity 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 Activity data into a format compatible with the selected external application.
   - It then makes an API call to create the Activity in that specific application.


Create Activity

Creates Activity in any external application

# 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

# Realtime Full two-way Sync of Notes

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

Note 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 Notes 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 Notes 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 Notes

Bi-directional realtime sync of Notes with records deduplication

# 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 Meeting

This scenario allows your application to create a Meeting in any external application in the same way. 
You will pass Meeting 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 Meeting with and configure mapping to our default model

2. **Create Meeting 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 Meeting data into a format compatible with the selected external application.
   - It then makes an API call to create the Meeting in that specific application.


Create Meeting

Creates Meeting in any external application

# Get all Meetings

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

When receiving Meetings 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 Meetings along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Meetings page by page.


Get all Meetings

Imports all Meetings from any external application to your App.

# Delete Activity

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

## How It Works

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


Delete Activity

Deletes Activity in any external application

# Realtime Full two-way Sync of Meetings

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

Meeting 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 Meetings 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 Meetings 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 Meetings

Bi-directional realtime sync of Meetings with records deduplication

# 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 Campaign

This scenario allows your application to create a Campaign in any external application in the same way. 
You will pass Campaign 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 Campaign with and configure mapping to our default model

2. **Create Campaign 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 Campaign data into a format compatible with the selected external application.
   - It then makes an API call to create the Campaign in that specific application.


Create Campaign

Creates Campaign in any external application

# 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

# Delete Lead

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

## How It Works

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


Delete Lead

# 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

# Continuous Import of Emails to Your App

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

When receiving Emails 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 Emails to my App

Import Emails and receive created/updated or deleted events

# Get all Campaigns

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

When receiving Campaigns 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 Campaigns along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Campaigns page by page.


Get all Campaigns

Imports all Campaigns from any external application to your App.

# 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.

Microsoft Dynamics 365 API Integration Profile

Configuration

Testing

Build every single integration your customers need with AI