sync customer data to DevRev to check existing customer
ART-2047_KNOWLEDGE_NODE-35
longer available.\n\n### Sync to DevRev\n\nAfter a successful import from a Salesforce account, you can choose to sync the imported data with DevRev. This feature airdrops any new items and any changes made to previously imported items from Salesforce.\n\nTo perform a one-time sync to DevRev, follow these steps:\n\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\n2. Locate the previously imported project.\n3. Select **\xe2\x8b\xae** > **Sync Salesforce Service to
Salesforce AirSync | AirSync | Snap-ins | DevRev
ART-2002_KNOWLEDGE_NODE-27
Plug, email, and WhatsApp) can be matched to the right customer record.\n\n![]()\n\nYou can create a contact using DevRev's rev-users.create API. Follow the [Create accounts and contacts in DevRev](https://developer.devrev.ai/beta/guides/create-accounts-and-contacts-in-dev-rev) tutorial.\n\n### Bulk import customer records\n\nTo bulk import customer records, see [Account and contact import](/docs/product/account-contact-import).\n\nYou can also use [AirSync](https://docs.devrev.ai/import) to
Contacts | Computer for Growth Teams | DevRev
ART-2049_KNOWLEDGE_NODE-32
to sync the\nimported data with DevRev. This feature airdrops any changes made to previously\nimported items from Freshdesk.\n\nTo perform a one-time sync to DevRev, follow these steps:\n\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\n2. Locate the relevant AirSync.\n3. Select **Sync Snap-ins to DevRev** option.\n\n![]()\n\nPlease be aware that this may override fields in previously imported\nitems, even if they were modified in DevRev.\n\n### Sync to Freshdesk\n\nAfter the initial
Freshdesk AirSync | AirSync | Snap-ins | DevRev
ART-4276_KNOWLEDGE_NODE-32
no longer available.\n\n### Sync to DevRev\n\nAfter a successful import from an Intercom account, you can choose to sync the imported data with DevRev. This feature imports any new data and applies any changes made to previously imported items from Intercom.\n\nTo perform a one-time sync to DevRev, follow these steps:\n\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\n2. Locate the previously imported project.\n3. Select the **\xe2\x8b\xae** > **Sync Intercom to DevRev**
Intercom AirSync | AirSync | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-31
several options to manage and sync your data:\n\n* **Sync to DevRev:** Synchronize new items created and modifications made in the external source to corresponding items in DevRev.\n* **Sync to External Source:** Synchronize new items created in DevRev and modifications made in DevRev to the external source.\n* **Periodic Sync:** Enable automatic periodic sync to keep data updated between DevRev and the external source.\n* **View Report:** Access detailed information about the initial import
AirSync | Snap-ins | DevRev
ART-17215_KNOWLEDGE_NODE-7
to be imported to DevRev. At this point, the DevRev app prompts the user to select an external sync unit from the list.\n3. The snap-in then extracts data from the external system.\n4. Afterwards, the DevRev app requests the mapping of data from the external system to DevRev. The user can decide which fields from each system should match.\n5. Once mapping is complete, the snap-in saves the data to DevRev.\n6. Finally, the snap-in streams any possible attachments from the external system to
Local development | DevRev | Docs
ART-13117_KNOWLEDGE_NODE-5
don't care about updates from Zendesk. How should I set up everything in DevRev?\n\nYou should tell your customer support representative that you want to enable merging of accounts for Salesforce and Zendesk syncs, and that you would like to sync updates from Salesforce even after merging. After the Airdrop team has enabled the automatic merging you should do a full Salesforce import, so that all the accounts from Salesforce are imported into DevRev. Then you can do a Zendesk import into
Airdrop duplicates merging
ART-2040_KNOWLEDGE_NODE-33
**AirSyncs**.\n2. Locate the previously imported project.\n3. Select the **\xe2\x8b\xae** > **Sync Zendesk to DevRev** option.\n\n![]()\n\nPlease be aware that this may override fields in previously imported items, even if they were modified in DevRev.\n\n### Sync to Zendesk\n\nAfter a successful import from a Zendesk account, you can sync changes made in DevRev to the previously imported [supported items](#supported-objects) back to Zendesk. Additionally, any new [DevRev tickets marked for
Zendesk AirSync | AirSync | Snap-ins | DevRev
ART-1991_KNOWLEDGE_NODE-25
helps you bring data from external sources to DevRev and keep them in sync.\n\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/).\n\nSupport\n-------\n\n| Automate | Integrate | AirSync |\n| --- | --- | --- |\n| [Auto parts to conversation](/docs/automations/auto-parts) | [Calendly](/docs/integrations/calendly) | [Salesforce](/docs/integrations/salesforce) |\n| [Auto-reply](/docs/automations/auto-reply) |
Support snap-ins | Computer for Support Teams | DevRev
ART-2045_KNOWLEDGE_NODE-41
matches an existing DevRev email**\n\nNo new user is created in DevRev. All work, comments, and assignments imported from the external source are associated with the existing DevRev user with the matching email.\n\n### Manual user merging\n\nThere are cases where the automatic AirSync [user deduplication logic](#dev-user-deduplication-logic) doesn\'t catch duplicates. This can happen when an imported user has no email address or the email address doesn\'t match that of an existing user in
AirSync | Snap-ins | DevRev
ART-2038_KNOWLEDGE_NODE-32
contacts\nand any changes made to previously imported items from Hubspot.\n\nTo perform a one-time sync to DevRev, follow these steps:\n\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\n2. Locate the previously imported project.\n3. Select the **\xe2\x8b\xae** > **Sync HubSpot to DevRev** option.\n\n![]()\n\nPlease be aware that this may override fields in previously imported\nitems, even if they were modified in DevRev.\n\n### Historical AirSyncs\n\nTo view currently running and
Hubspot AirSync | AirSync | Snap-ins | DevRev
ART-2002_KNOWLEDGE_NODE-34
ingestion\n\nThe identity of your customers can be brought to the DevRev system in multiple ways.\n\n**Plug**  \nYour Plug integration automatically brings customer identity to DevRev with each widget conversation.\n\nWorkspace and external user information provided as part of the [Plug integration](https://developer.devrev.ai/sdks/web/user-identity) identifies or creates corresponding customer identity in the DevRev system and links it to Plug conversations.\n\n**Integrations**  \nDevRev's
Contacts | Computer for Growth Teams | DevRev
ART-2047_KNOWLEDGE_NODE-32
automatically.\n\nPost import options\n-------------------\n\nAfter a successful import, you have the following options available for the imported account:\n\n* [Sync to DevRev](#sync-to-devrev):\n  + This option allows you to synchronize any modifications made in Salesforce with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any new items created in Salesforce after the last sync or import. This is a one-time operation.\n* [Sync to
Salesforce AirSync | AirSync | Snap-ins | DevRev
ART-2038_KNOWLEDGE_NODE-31
the import and all items that were imported from\n    Hubspot into DevRev, you can use this option.\n* Edit Connection\n  + Use this option to change the connection used for any subsequent actions. It\n    can be helpful if a connection becomes inactive or the user who established\n    it's no longer available.\n\n### Sync to DevRev\n\nAfter a successful import from a Hubspot account, you can choose to sync the\nimported data with DevRev. This feature airdrops any new companies and
Hubspot AirSync | AirSync | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-49
associated with the account you want to merge from will be associated with the account to be merged with.\n4. Click **Merge**.\n\nContact deduplication\n---------------------\n\nDevRev contacts help you keep track of your [customers](https://docs.devrev.ai/product/customers). Contacts are the individual users, which may or may not be associated with an account. DevRev contacts aren\'t globally unique. The same user may have multiple contact records.\n\nAirSync imported contacts are deduplicated
AirSync | Snap-ins | DevRev
ART-2040_KNOWLEDGE_NODE-32
options\n-------------------\n\nAfter a successful import, you have the following options available for the imported project.\n\n### Sync to DevRev\n\nAfter a successful import from a Zendesk workspace, you can choose to sync the imported data with DevRev. This feature airdrops any new tickets, customers, organizations, and any changes made to previously imported items from Zendesk.\n\nTo perform a one-time sync to DevRev, follow these steps:\n\n1. Go to **Settings** > **Integrations** >
Zendesk AirSync | AirSync | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-27
sources](#available-sources)\n\n1. [Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[AirSync](/docs/import)\n\nAirSync\n=======\n\nWith DevRev\'s AirSync, you can migrate data from various platforms or keep data in sync between DevRev and external sources. Whether you perform a one-time import, set up a one-way sync, or establish a two-way sync, AirSync supports a flexible data migration or co-existence strategy. (AirSync was previously known as *Airdrop*.)\n\nAirSync
AirSync | Snap-ins | DevRev
ART-17213_KNOWLEDGE_NODE-8
to an external system.\nIt uses a **loader** function, to create or update data in the external system.\n\n### Initial sync\n\nThe first sync is called the *initial sync*.\nIt is triggered manually by the end user in DevRev\xe2\x80\x99s **AirSyncs** UI.\n\nDuring the initial sync, all data from the external sync unit is extracted from the external system and loaded into DevRev.\nThis process typically involves a large import and may take some time.\n\nAn *initial import* consists of the
Getting started | DevRev | Docs
ART-2047_KNOWLEDGE_NODE-33
Salesforce](#sync-to-salesforce):\n  + This option synchronizes any changes made in DevRev to previously synced Salesforce [supported items](#supported-objects) back to Salesforce. It also creates any [items marked in DevRev](#mark-a-devrev-ticket-for-syncing) for creation in Salesforce. This is a one-time operation.\n* [Periodic Sync](#periodic-sync):\n  + By enabling this option, you can automatically sync new changes from Salesforce to DevRev on a periodic basis. The default frequency is
Salesforce AirSync | AirSync | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-46
organizations in Zendesk, or accounts in Salesforce.\n\nAn AirSync doesn\'t deduplicate imported accounts; rather, it modifies them so that new accounts don\'t violate DevRev constraints. These accounts can be merged after the import has been completed. Since DevRev has several constraints on the uniqueness of different DevRev account fields, AirSync avoids breaking these constraints by following these rules when another account is already using the unique value:\n\n| Account Field | Rule |\n|
AirSync | Snap-ins | DevRev
ART-17211_KNOWLEDGE_NODE-0
b'AirSync | DevRev | Docs\n\n[![]()![]()](https://developer.devrev.ai/)\n\nPublic\n\nPublic\n\nSearch\n\n`/`\n\nAirSync\n=======\n\nCopy page\n\n*AirSync* is DevRev\xe2\x80\x99s solution for migrating data between DevRev and an external system.\nIt allows our users to import their existing data from an external system,\nexport any changes in DevRev back to the external system, and keep data in sync.\n\nDevRev provides a range of snap-ins available through the DevRev marketplace for integration
AirSync | DevRev | Docs
ART-1945_KNOWLEDGE_NODE-29
such as Slack and Jira. Automations perform tasks within DevRev based on events, like responding to customer conversations and linking tickets and issues. [AirSync](./import) helps you bring data from external sources to DevRev and keep them in sync.\n\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/about/for-developers).\n\n[PreviousIntroduction](/docs)[NextCore concepts](/docs/product/core)\n\n#### On
Computer by DevRev | DevRev
ART-2038_KNOWLEDGE_NODE-30
items in DevRev for any new companies or contacts created in Hubspot after\n    the last sync or import.\n* [Periodic Sync](#periodic-sync)\n  + By enabling this option, you can automatically sync new changes from Hubspot\n    to DevRev on a periodic basis. The default frequency is once an hour.\n* View Report\n  + This option allows you to access detailed information about the initial\n    import and any subsequent syncs performed.\n* [Delete Import](#delete-import)\n  + If you wish to remove
Hubspot AirSync | AirSync | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-38
Examples of AirSync-created users include engineers working on imported Jira issues, support agents who own imported Zendesk tickets, and account owners for imported Hubspot accounts.\n\nWhen importing external users, the email address is used as a means of deduplication.\n\n### User deduplication logic\n\n#### **User has no email or it\'s not accessible**\n\nA new user is created in DevRev. This user is marked as *Unassigned*. Unassigned users can\'t log in and have no access to DevRev. All
AirSync | Snap-ins | DevRev
ART-15506_KNOWLEDGE_NODE-16
request details and timestamp. |\n\n### How resolution works\n\nWhen you send object information to DevRev, the system automatically creates or finds existing contacts, accounts, and workspaces.\n\nDevRev offers three ways to structure your customer\xe2\x80\x99s data:\n\n| Hierarchy Type | Documents Created | What to Include | Use Case |\n| --- | --- | --- | --- |\n| **Single-level** | Contacts only | Only user information | Recommended for most B2C cases |\n| **Two-level** | Accounts and
Identify your users with Plug | DevRev | Docs
ART-2038_KNOWLEDGE_NODE-24
options](#post-import-options)\n* [Sync to DevRev](#sync-to-devrev)\n\n1. [Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[AirSync](/docs/import)\n[Hubspot AirSync](/docs/integrations/hubspot)\n\nHubspot AirSync\n===============\n\nDevRev's Hubspot AirSync allows you to seamlessly import your Hubspot companies\nand contacts into DevRev.\n\n![]()\n\nFor more information, refer to the\n[Hubspot AirSync snap-in](https://marketplace.devrev.ai/hubspot) on the DevRev\nmarketplace.\n\nSupported
Hubspot AirSync | AirSync | Snap-ins | DevRev
ART-3208_KNOWLEDGE_NODE-25
the target organization. Those marked as **Supported** are eligible for import.\n\n| DevRev Object | Sync to DevRev |\n| --- | --- |\n| Issue | \xe2\x9c\x85 |\n| Ticket | \xe2\x9c\x85 |\n| DevUser | \xe2\x9c\x85 |\n| Customer | \xe2\x9c\x85 |\n| Tag | \xe2\x9c\x85 |\n| Product | \xe2\x9c\x85 |\n| Capability | \xe2\x9c\x85 |\n| Enhancement | \xe2\x9c\x85 |\n| Feature | \xe2\x9c\x85 |\n| Runnable | \xe2\x9c\x85 |\n| Links on works | \xe2\x9c\x85 |\n| Timeline Comment | \xe2\x9c\x85 |\n| Account |
DevRev AirSync | AirSync | Snap-ins | DevRev
ART-13117_KNOWLEDGE_NODE-4
of domain, different websites can still match if their domains match, e.g., google.com/page1 and google.com/page2 are different websites, but have the same domain google.com) and thus accounts with those two websites would be merged\n\nBoth accounts have the same display name and at least one matching domain or websiteExamplesI have the same accounts in Salesforce and Zendesk and would like to import them into DevRev without duplicates. I want to sync updates from Salesforce to DevRev, but I
Airdrop duplicates merging
ART-2895_KNOWLEDGE_NODE-4
that your AAT isn\xe2\x80\x99t exposed.\n\nUsing the `rev_info` method, you can generate and recognize a user within the DevRev system by providing relevant user details. This method enables you to convey information systematically, ensuring alignment between your DevRev CRM and the structured data model. For information regarding terminologies, click [here](https://devrev.ai/docs/product/grow).\n[code]\n\n    $| curl --location \'https://api.devrev.ai/auth-tokens.create\' \\  \n    ---|---  \n
Identify your users with PLuG — DevRev | Docs
ART-2040_KNOWLEDGE_NODE-30
established, select the Zendesk workspace you want to import and specify the DevRev part where the imported tickets should be created. This initiates a bulk import of the selected workspace.\n4. DevRev makes an effort to automatically map the fields from Zendesk to corresponding fields in DevRev. However, you may be prompted to manually map certain fields if needed.\n\n![]()\n\nDevRev supports importing Zendesk organization custom fields. When importing organizations, AirSync will display
Zendesk AirSync | AirSync | Snap-ins | DevRev
ART-2049_KNOWLEDGE_NODE-25
of Freshdesk objects and their corresponding DevRev\nequivalent. Those marked as **Supported** are eligible for AirSync.\n\n| Freshdesk Object | DevRev Object | Sync to DevRev | Sync to Freshdesk |\n| --- | --- | --- | --- |\n| Ticket | Ticket | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Company | Account | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Contact | Customer | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Agent | DevUser | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Conversation | Timeline Comment | \xe2\x9c\x85 | \xe2\x9c\x85
Freshdesk AirSync | AirSync | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-45
user.\n\nTo perform a merge:\n\n1. Open the list of *Unassigned* or *Shadow* users.\n2. Select the action **\xe2\x8b\xae** menu > **Merge User**.\n3. Find the *Active* user you wish to merge with.\n\nAccount deduplication\n---------------------\n\nDevRev accounts help you keep track of your [customers](https://docs.devrev.ai/product/customers). AirSync can import accounts from various external sources. Accounts from external sources can have varying names, such as companies in Hubspot,
AirSync | Snap-ins | DevRev
ART-2895_KNOWLEDGE_NODE-9
and details along with the `account_ref` and details.\n\n**Attributes for users**\n\nAttributes| Description| Type  \n---|---|---  \n`user_ref`| A unique user reference that the DevRev app uses for identifying your users. This parameter is required.| string  \n`email`| The email address of the customer. It\xe2\x80\x99s used for sending email notifications of any support messages.| string  \n`display_name`| The name of the user that\xe2\x80\x99s shown on the widget.| string  \n`phone_numbers`|
Identify your users with PLuG — DevRev | Docs
ART-10697_KNOWLEDGE_NODE-25
built with support for synchronization from DevRev to external systems. Previously, these integrations could only sync data from external systems to DevRev. This enhancement allows developers to create full two-way sync functionality in their Airdrop integrations, if desired.\n\n**Native vs Non-Native Airdrop**\n\nDevRev provides native Airdrop integrations for popular platforms including:\n\n* Jira\n* Zendesk\n* Salesforce\n* ServiceNow\n* And other major systems\n\nWhile these native
February 2025 | Changelog | DevRev
ART-2000_KNOWLEDGE_NODE-28
DevRev:\n\n* **Domains**: Domain names associated with the company to help map contacts to accounts when a contact isn't already linked. Use the format: '[subdomain].domain.com'\n* **External references**: Identifier for this company from your primary customer record, for example, company domain or account ID. This is used to match customer identity across channels to one record.\n* **Created by**: The user who created the account.\n* **Created date**: The date the account was created.\n*
Accounts | Computer for Growth Teams | DevRev
ART-2038_KNOWLEDGE_NODE-29
account with tens of thousands of\nitems with many attachments. DevRev honors the Hubspot API rate limits and\nback-off and resume automatically.\n\nPost import options\n-------------------\n\nAfter a successful import, you have the following options available for the\nimported account:\n\n* [Sync to DevRev](#sync-to-devrev)\n  + This option allows you to synchronize any modifications made in Hubspot with\n    the corresponding items previously imported into DevRev. It also creates new\n
Hubspot AirSync | AirSync | Snap-ins | DevRev
ART-2038_KNOWLEDGE_NODE-25
objects\n-----------------\n\nThe following is a list of Hubspot objects and their corresponding DevRev\nequivalent. Those marked as **Supported** are eligible for import.\n\n| HubSpot Object | DevRev Object | Sync to DevRev |\n| --- | --- | --- |\n| Contact | Contact | \xe2\x9c\x85 |\n| Company | Account | \xe2\x9c\x85 |\n| Deal | Opportunity | \xe2\x9c\x85 |\n| Pipeline of Deal | State/Stage of Opportunity | \xe2\x9c\x85 |\n| Note on Deal | Comment on Opportunity | \xe2\x9c\x85 |\n|
Hubspot AirSync | AirSync | Snap-ins | DevRev
ART-15602_KNOWLEDGE_NODE-26
data export:\n\n| Freshdesk Object | DevRev Object | Sync to DevRev |\n| --- | --- | --- |\n| Ticket | Ticket | \xe2\x9c\x85 |\n| Conversation | Timeline Comment | \xe2\x9c\x85 |\n| Attachment | Attachment | \xe2\x9c\x85 |\n| Agent | DevUser | \xe2\x9c\x85 |\n| Contact | Customer | \xe2\x9c\x85 |\n| Company | Account | \xe2\x9c\x85 |\n\nImporting from Freshdesk\n------------------------\n\nImporting historical tickets from Freshdesk is a two-step process:\n\n### Install and configure the
Freshdesk historical ticket import | AirSync | Snap-ins | DevRev
ART-2047_KNOWLEDGE_NODE-40
view.\n3. Select the context menu (\xe2\x8b\xae) > **View Report**.\n\n### Periodic sync\n\nAfter successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour.\n\nTo configure periodic sync, follow these steps:\n\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\n2. Locate the previously imported project.\n3. Select the **\xe2\x8b\xae** > **Set Periodic
Salesforce AirSync | AirSync | Snap-ins | DevRev