Folder id with encoded drive id, site id, item id

Record Id with the encoded drive id, site id, and item id

Parameters

Content Items

Drive Items

Drives

When creating a new item, provide the file extension in the name field. For example, 'example.txt'.

Drive Item Name

Folders

List Content Types

List Items

Lists

Sites

A freeform text entry field for users to describe themselves.

true if the account is enabled; otherwise, false. This property is required when a user is created.

Sets the age group of the user. Allowed values: null, Minor, NotAdult, and Adult. For more information, see legal age group property definitions.

The licenses that are assigned to the user, including inherited (group-based) licenses. This property doesn't differentiate between directly assigned and inherited licenses. Use the licenseAssignmentStates property to identify the directly assigned and inherited licenses.

The plans that are assigned to the user. Read-only. Not nullable.

Identifiers that can be used to identify and authenticate a user in non-Azure AD environments. This property can store identifiers for smartcard-based certificates that users use to access on-premises Active Directory deployments or federated access. It can also be used to store the Subject Alternate Name (SAN) that's associated with a Common Access Card (CAC). Nullable.

The birthday of the user. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z

The telephone numbers for the user. Only one number can be set for this property. Read-only for users synced from on-premises directory.

The city where the user is located. Maximum length is 128 characters.

Microsoft realtime communication information related to the user.

The name of the company the user is associated with. This property can be useful for describing the company that an external user comes from. The maximum length is 64 characters.

Sets whether consent has been obtained for minors. Allowed values: null, Granted, Denied and NotRequired. Refer to the legal age group property definitions for further information.

The country or region where the user is located; for example, US or UK. Maximum length is 128 characters.

The date and time the user was created in ISO 8601 format and UTC. The value cannot be modified and is automatically populated when the entity is created. Nullable. For on-premises users, the value represents when they were first created in Microsoft Entra ID. Property is null for some users created before June 2018 and on-premises users synced to Microsoft Entra ID before June 2018. Read-only.

Indicates whether the user account was created through one of the following methods: As a regular school or work account (null), As an external account (Invitation), As a local account for an Azure Active Directory B2C tenant (LocalAccount), Through self-service sign-up by an internal user using email verification (EmailVerified), Through self-service sign-up by an external user signing up through a link that is part of a user flow (SelfServiceSignUp).

An open complex type that holds the value of a custom security attribute that is assigned to a directory object. Nullable.

The name of the department where the user works. Maximum length is 64 characters.

The name displayed in the address book for the user. This value is usually the combination of the user's first name, middle initial, and last name. This property is required when a user is created, and it cannot be cleared during updates. Maximum length is 256 characters.

The date and time when the user was hired or will start work if there is a future hire.

The employee identifier assigned to the user by the organization. The maximum length is 16 characters.

The date and time when the user left or will leave the organization.

Represents organization data (for example, division and costCenter) associated with a user.

Captures enterprise worker type. For example, Employee, Contractor, Consultant, or Vendor.

For an external user invited to the tenant using the invitation API, this property represents the invited user's invitation status. For invited users, the state can be PendingAcceptance or Accepted, or null for all other users.

Shows the timestamp for the latest change to the externalUserState property.

The given name (first name) of the user. Maximum length is 64 characters.

The hire date of the user. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.

The unique identifier for the user. It should be treated as an opaque identifier. Inherited from directoryObject. Not nullable. Read-only.

Represents the identities that can be used to sign in to this user account. An identity can be provided by Microsoft (also known as a local account), by organizations, or by social identity providers such as Facebook, Google, and Microsoft and tied to a user account. It may contain multiple items with the same signInType value.

The instant message voice-over IP (VOIP) session initiation protocol (SIP) addresses for the user. Read-only.

Identifies the info segments assigned to the user.

A list for users to describe their interests.

Indicates whether the user is pending an exchange mailbox license assignment. Read-only.

true if the user is a member of a restricted management administrative unit, which requires a role scoped to the restricted administrative unit to manage. Default value is false. Read-only.

The user's job title. Maximum length is 128 characters.

When this Microsoft Entra user last changed their password or when their password was created, whichever date the latest action was performed. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only.

Used by enterprise applications to determine the legal age group of the user. This property is read-only and calculated based on ageGroup and consentProvidedForMinor properties. Allowed values: null, MinorWithOutParentalConsent, MinorWithParentalConsent, MinorNoParentalConsentRequired, NotAdult, and Adult. For more information, see legal age group property definitions.

State of license assignments for this user. It also indicates licenses that are directly assigned and the ones the user inherited through group memberships. Read-only.

The SMTP address for the user, for example, admin@contoso.com. Changes to this property also update the user's proxyAddresses collection to include the value as an SMTP address. This property can't contain accent characters.

The mail alias for the user. This property must be specified when a user is created. Maximum length is 64 characters.

Settings for the primary mailbox of the signed-in user. You can get or update settings for sending automatic replies to incoming messages, locale, and time zone. For more information, see User preferences for languages and regional formats.

The primary cellular telephone number for the user. Read-only for users synced from the on-premises directory.

The office location in the user's place of business. Maximum length is 128 characters.

Contains the on-premises Active Directory distinguished name or DN. The property is only populated for customers synchronizing their on-premises directory to Microsoft Entra ID via Microsoft Entra Connect. Read-only.

Contains the on-premises domainFQDN, also called dnsDomainName synchronized from the on-premises directory. The property is only populated for customers synchronizing their on-premises directory to Microsoft Entra ID via Microsoft Entra Connect. Read-only.

Contains extensionAttributes1-15 for the user. These extension attributes are also known as Exchange custom attributes 1-15.

This property associates an on-premises Active Directory user account to their Microsoft Entra user object. This property must be specified when creating a new user account in the Graph if you're using a federated domain for the user's userPrincipalName (UPN) property. Note: The $ and _ characters can't be used when specifying this property.

Indicates the last time at which the object was synced with the on-premises directory; for example: '2013-02-16T03:04:54Z'. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only.

Errors when using Microsoft synchronization product during provisioning.

Contains the on-premises sAMAccountName synchronized from the on-premises directory. The property is only populated for customers synchronizing their on-premises directory to Microsoft Entra ID via Microsoft Entra Connect. Read-only.

Contains the on-premises security identifier (SID) for the user synchronized from on-premises to the cloud. Read-only.

Contains all on-premises Session Initiation Protocol (SIP) information related to the user. Read-only.

true if this user object is currently being synced from an on-premises Active Directory (AD); otherwise, the user isn't being synced and can be managed in Microsoft Entra ID. Read-only.

Contains the on-premises userPrincipalName synchronized from the on-premises directory. The property is only populated for customers synchronizing their on-premises directory to Microsoft Entra ID via Microsoft Entra Connect. Read-only.

A list of additional email addresses for the user; for example: ['bob@contoso.com', 'Robert@fabrikam.com'].

Specifies password policies for the user. This value is an enumeration with one possible value being DisableStrongPassword, which allows weaker passwords than the default policy to be specified. DisablePasswordExpiration can also be specified. The two may be specified together; for example: DisablePasswordExpiration, DisableStrongPassword.

Specifies the password profile for the user. The profile contains the user's password. This property is required when a user is created. The password in the profile must satisfy minimum requirements as specified by the passwordPolicies property. By default, a strong password is required.

A list for users to enumerate their past projects.

The postal code for the user's postal address. The postal code is specific to the user's country/region. In the United States of America, this attribute contains the ZIP code. Maximum length is 40 characters.

The preferred data location for the user. For more information, see OneDrive Online Multi-Geo.

The preferred language for the user. The preferred language format is based on RFC 4646. The name combines an ISO 639 two-letter lowercase culture code associated with the language and an ISO 3166 two-letter uppercase subculture code associated with the country or region. Example: 'en-US', or 'es-ES'.

The preferred name for the user. Not Supported. This attribute returns an empty string.

The plans that are provisioned for the user. Read-only. Not nullable.

For example: ['SMTP: bob@contoso.com', 'smtp: bob@sales.contoso.com']. Changes to the mail property also update this collection to include the value as an SMTP address. The proxy address prefixed with SMTP (capitalized) is the primary proxy address, while the ones prefixed with smtp are the secondary proxy addresses. For Azure AD B2C accounts, this property has a limit of 10 unique addresses. Read-only in Microsoft Graph; you can update this property only through the Microsoft 365 admin center. Not nullable.

Any refresh tokens or sessions tokens (session cookies) issued before this time are invalid, and applications get an error when using an invalid refresh or sessions token to acquire a delegated access token (to access APIs such as Microsoft Graph). If it happens, the application must acquire a new refresh token by requesting the authorized endpoint. Read-only. Use invalidateAllRefreshTokens to reset.

A list for the user to enumerate their responsibilities.

A list for the user to enumerate the schools they have attended.

Security identifier (SID) of the user, used in Windows scenarios. Read-only.

Errors published by a federated service describing a nontransient, service-specific error regarding the properties or link from a user object.

Do not use in Microsoft Graph. Manage this property through the Microsoft 365 admin center instead. Represents whether the user should be included in the Outlook global address list. See Known issue.

Get the last signed-in date and request ID of the sign-in for a given user. Read-only.

Any refresh tokens or sessions tokens (session cookies) issued before this time are invalid, and applications get an error when using an invalid refresh or sessions token to acquire a delegated access token (to access APIs such as Microsoft Graph). If this happens, the application must acquire a new refresh token by requesting the authorized endpoint. Read-only. Use revokeSignInSessions to reset.

A list for the user to enumerate their skills.

The state or province in the user's address. Maximum length is 128 characters.

The street address of the user's place of business. Maximum length is 1024 characters.

The user's surname (family name or last name). Maximum length is 64 characters.

A two-letter country code (ISO standard 3166). Required for users that are assigned licenses due to legal requirements to check for availability of services in countries. Examples include: US, JP, and GB. Not nullable.

The user principal name (UPN) of the user. The UPN is an Internet-style sign-in name for the user based on the Internet standard RFC 822. By convention, this should map to the user's email name. The general format is alias@domain, where the domain must be present in the tenant's verified domain collection. This property is required when a user is created. The verified domains for the tenant can be accessed from the verifiedDomains property of organization.

A String value that can be used to classify user types in your directory, such as Member and Guest.

Users

Microsoft Sharepoint

Download File

Get Connected Account Details

Dropbox

Google Drive

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

Salesforce

HubSpot

Microsoft Dynamics 365

Zoho CRM

Pipedrive

Monday

Freshsales

Slack

Keap

Jira

SugarCRM

Asana

Outreach

Xero

ActiveCampaign

Capsule CRM

Github

Notion

Salesloft

Clickup

Agile CRM

SalesForce Pardot

SharpSpring

Teamleader

Insightly

Zendesk

Attio

Copper

Microsoft Teams

Greenhouse Harvest

Zoho Books

Front

Calendly

Close

Freshdesk

BambooHR

Breezy HR

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

AWS S3

# Continuous Import of Folders to Your App

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

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

Import Folders and receive created/updated or deleted events

# Get all Folders

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

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


Get all Folders

Imports all Folders from any external application to your App.

# Create Drive

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

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


Create Drive

Creates Drive in any external application

# Create Drive Item

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

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


Create Drive Item

Creates Drive Item in any external application

# Realtime Full two-way Sync of Folders

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

Folder 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 Folders 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 Folders 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 Folders

Bi-directional realtime sync of Folders with records deduplication

# Create File

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

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


Create File

# Download File


This scenario allows your application to download files from Box, Dropbox, Google Drive, OneDrive or Microsoft SharePoint.
File fields will be mapped from schema supported by your application to the application-specific schema

## How it works

1. **Download File**:
   - Call Integration.app REST API or SDK with file ID from external app.
   - When called, Integration.app retrieves the requested file from the original storage, and provides you with a temporary download link. This guarantees same interface for you for downloading files in the same way from any application

2. **Configuration options**:
    - You can get small files via Actions or use this action in Flow to download large files up to a few GBs.
    - Google drive: Since Google Drive supports Docs, Sheets, Slides and more in addition to uploaded files,
you can use an additional `exportAs` parameter to specify which MIME-type (out of [supported](https://developers.google.com/drive/api/guides/ref-export-formats)) you want to export the file to.
By default, we export Google Docs in the Microsoft Office formats (.docx, .xlsx, .pptx).


Download files from Box, Dropbox, Google Drive, OneDrive or Microsoft SharePoint.

# Continuous Import of Drives to Your App

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

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

Import Drives and receive created/updated or deleted events

# Create User

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


## How It Works

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

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


Create User

# Continuous Import of Drive Items to Your App

This scenario enables your application to continuously sync 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 Drive Items 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 Drive Items to my App

Import Drive Items and receive created/updated or deleted events

# Delete Drive Item

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

## How It Works

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


Delete Drive Item

Deletes Drive Item in any external application

# Get all Drive Items

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

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


Get all Drive Items

Imports all Drive Items from any external application to your App.

# Delete File

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

## How It Works

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


Delete File

# Get all Drives

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

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


Get all Drives

Imports all Drives from any external application to your App.

# Update User

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

## How It Works

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

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


Update User

# Delete User

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

## How It Works

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


Delete User

# Realtime Full two-way Sync of Drives

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

Drive 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 Drives 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 Drives 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 Drives

Bi-directional realtime sync of Drives with records deduplication

# Update Drive

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

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


Update Drive

Updates Drive in any external application

# Get all Users

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

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

## How It Works

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


Get all Users

Imports all Users from any external application to your App.

# Realtime Full two-way Sync of Drive Items

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

Drive Item 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 Drive Items 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 Drive Items 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 Drive Items

Bi-directional realtime sync of Drive Items with records deduplication

Microsoft Sharepoint API Integration Profile

Build every single integration your customers need with AI