Greenhouse Harvest

Lever

# Delete Job Interview

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

## How It Works

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


Delete Job Interview

Deletes Job Interview in any external application

1. Go to the `delete-job-interview` action
2. Check "how to deploy" page to see code example for running this action

Сall the `delete-job-interview` action via REST API or integration.app SDK

Salesforce

HubSpot

Microsoft Dynamics 365

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

Dropbox

Google Drive

Microsoft Sharepoint

MS OneDrive

# Continuous Import of Files and Folders (Drive Items) to Your App

This scenario enables your application to continuously sync and download Files and Folders (Drive Items) from any external application to your app's API. It handles the initial import of Drive Items and keeps them synchronized when a drive item is created, updated, or deleted in the external application.

When receiving Files 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.

3. **Download File**:
   - Make a single API request to start file download from external app, it will return download file URI, that you can use to download file from any source in the same way

Continuously Import Files and Folders to my App

Import files and folders, download files and receive created/updated or deleted events

Quickbooks

Freshbooks

Chargebee

PayPal

# Create Invoice

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

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


Create Invoice

Creates Invoice in any external application

Gmail

Microsoft Outlook

# Send Email

This scenario allows your application to send emails using Gmail or Outlook. The email fields will be mapped from the schema supported by your application to the application-specific schema.

## How It Works

- Make an API request via REST API or the Integration.app SDK with the data required to send the email.
- The email data from your application is transformed into a format compatible with the selected external application (Gmail or Outlook).


Send Email

Send an email via Gmail or Microsoft Outlook

Monday

Slack

Jira

Asana

Github

Notion

Clickup

Microsoft Teams

Calendly

BambooHR

Basecamp

Okta

Deel

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

# Get all Timeoff Requests

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

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


Get all Timeoff Requests

Imports all Timeoff Requests from any external application to your App.

# Continuous Import of Timeoff Requests to Your App

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

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

Import Timeoff Requests and receive created/updated or deleted events

# Delete Timeoff Balance

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

## How It Works

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


Delete Timeoff Balance

Deletes Timeoff Balance in any external application

# Create Timeoff Balance

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

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


Create Timeoff Balance

Creates Timeoff Balance in any external application

# Realtime Full two-way Sync of Timeoff Balances

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

Timeoff Balance 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 Timeoff Balances 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 Timeoff Balances 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 Timeoff Balances

Bi-directional realtime sync of Timeoff Balances with records deduplication

# Realtime Full two-way Sync of Timeoff Requests

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

Timeoff Request 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 Timeoff Requests 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 Timeoff Requests 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 Timeoff Requests

Bi-directional realtime sync of Timeoff Requests with records deduplication

# Get all Timeoff Balances

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

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


Get all Timeoff Balances

Imports all Timeoff Balances from any external application to your App.

# Update Timeoff Request

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

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


Update Timeoff Request

Updates Timeoff Request in any external application

# Create Timeoff Request

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

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


Create Timeoff Request

Creates Timeoff Request in any external application

# Continuous Import of Timeoff Balances to Your App

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

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

Import Timeoff Balances and receive created/updated or deleted events

# Update Timeoff Balance

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

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


Update Timeoff Balance

Updates Timeoff Balance in any external application

# Delete Timeoff Request

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

## How It Works

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


Delete Timeoff Request

Deletes Timeoff Request in any external application

ADP Workforce Now

Ashby

# Job Application Unified API

This scenario contains the complete Job Applications Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Job Applications while also receiving notifications on creation, updates, and deletions of Job Applications 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.


Job Applications Unified API

Workable

Recruitee

# Job Unified API

This scenario contains the complete Jobs Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Jobs while also receiving notifications on creation, updates, and deletions of Jobs 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.


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


Companies Unified API

# Job Candidate Unified API

This scenario contains the complete Job Candidates Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Job Candidates while also receiving notifications on creation, updates, and deletions of Job Candidates 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.


Job Candidates 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

Woosender

# 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

Google Calendar

# Activity Unified API

This scenario contains the complete Activities Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Activities while also receiving notifications on creation, updates, and deletions of Activities 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.


Activities Unified API

SAP S4 HANA

# Invoice Unified API

This scenario contains the complete Invoices Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Invoices while also receiving notifications on creation, updates, and deletions of Invoices 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.


Invoices 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

Shopify

Woocommerce

Lightspeed R-Series

# Order Unified API

This scenario contains the complete Orders Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Orders while also receiving notifications on creation, updates, and deletions of Orders 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.


Orders Unified API

# Note Unified API

This scenario contains the complete Notes Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Notes while also receiving notifications on creation, updates, and deletions of Notes 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.


Notes Unified API

Marketo

# Lead Unified API

This scenario contains the complete Leads Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Leads while also receiving notifications on creation, updates, and deletions of Leads 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.


Leads Unified API

Stripe

BigCommerce

# Product Unified API

This scenario contains the complete Products Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Products while also receiving notifications on creation, updates, and deletions of Products 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.


Products Unified API

Trello Connector

Todoist

Teamwork

HiBob

Linear

# 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

This scenario will show how to send a message to a Slack channel

## Send Message To a Slack Channel Action

We created `send-message-to-slack-channel` action of type `create-data-record` that would send a message to a specific Slack channel, when called.
There are a few action parameters you should configure to make the action fully operational:

- `channel_id`: the ID of a slack channel you want a message to be sent to [required]
- `token_type`: whether you want a message to be sent on behalf of an authorized user or a slack app. Note that the `token_type` defaults to `bot` value, should you choose to leave it empty
- `message_blocks`: a list of blocks your message should consist of. More about the structure of building block you can read [here](https://app.slack.com/block-kit-builder/)



Send Message To Slack Channel

This action will send a message to a slack channel

# Realtime Full two-way Sync of Deal Stages

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

Deal Stage 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 Deal Stages 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 Deal Stages 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 Deal Stages

Bi-directional realtime sync of Deal Stages 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

# Update Product

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

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


Update Product

Updates Product in any external application

# Realtime Full two-way Sync of Campaign Members

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

Campaign Member 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 Campaign Members 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 Campaign Members 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 Campaign Members

Bi-directional realtime sync of Campaign Members with records deduplication

Isolved

# Realtime Full two-way Sync of Customers

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

Customer 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 Customers 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 Customers 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 Customers

Bi-directional realtime sync of Customers with records deduplication

AWS S3

# Get all Files

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

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


Get all Files

Imports all Files from any external application to your App.

# Get all Suppliers

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

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


Get all Suppliers

Imports all Suppliers from any external application to your App.

# Delete Drive

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

## How It Works

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


Delete Drive

Deletes Drive in any external application

# Realtime Full two-way Sync of Activities

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

Activity 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 Activities 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 Activities 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 Activities

Bi-directional realtime sync of Activities with records deduplication

Delete Job Interview

Delete Job Interview

How It Works

Explore Similar Templates

Create Invoice

Send Email

Delete Timeoff Balance

Create Timeoff Balance

Build every single integration your customers need with AI