Drift is a conversational AI platform that helps B2B revenue teams engage website visitors, qualify leads, and build relationships through AI chatbots, live chat, and playbooks. Now part of Salesloft's Revenue Orchestration Platform, it automates lead qualification, routes buyers to the right reps, and books meetings instantly. Connect to manage conversations, contacts, accounts, users, and bot playbooks.
Power end-to-end data operations for your Drift API with Nexla. Our bi-directional Drift connector is purpose-built for Drift, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Drift or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Drift workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to the Drift API, you will need a Drift API access token and the Drift API base URL. Drift uses Bearer token authentication — each request to the API includes the access token in the Authorization request header in the format Bearer {your_token}.
Drift issues access tokens through its developer portal at dev.drift.com. You can generate a non-expiring access token by creating a Drift app and installing it to your organization. This approach is suitable for internal integrations where access to a single Drift organization is needed.
Sign in to the Drift developer portal at dev.drift.com.
Click the Build Your App button under the Your Apps section to create a new application.
Enter a name and description for your app — for example, "Nexla Integration" — then click Create.
Navigate to the OAuth & Permissions page within your app settings.
Scroll to the Scopes section and select the permissions your integration requires. For Nexla integrations involving conversations, contacts, accounts, and users, enable the relevant read and/or write scopes based on the operations you plan to perform.
Drift API scopes control which resources and actions your access token can interact with. Grant only the scopes required for your intended use case to follow the principle of least privilege. For a complete list of available scopes, refer to the Drift Authentication and Scopes documentation.
Scroll to the Activate Your App section and click Install to install the app to your Drift organization. Installing the app generates a non-expiring access token scoped to your account.
Copy the generated Access Token. This is the value you will enter as the API Key Value when creating the credential in Nexla.
Important
Store your Drift access token securely. This token provides access to your Drift organization's data according to the scopes configured in your app. Do not share it in public repositories or unsecured locations.
The default Drift API base URL is https://driftapi.com. This value is pre-populated in Nexla and does not typically need to be changed. Refer to the Drift developer documentation if your organization uses a custom API endpoint.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Drift access token in the API Key Value field. This is the non-expiring token generated when you installed your app in the Drift developer portal (see Prerequisites). This value is treated as a secret and will be masked after saving.
Confirm or update the value in the Base URL field. The field is pre-populated with https://driftapi.com, which is the standard Drift API base URL. Update this value only if your organization uses a custom or regional Drift API endpoint.
The Drift API enforces a default rate limit of 600 requests per minute. Rate limit information is returned in the response headers of each API call. For guidance on handling rate limit responses in your data flows, refer to the Drift API FAQs.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Drift connector tile, then select the credential that will be used to connect to the Drift instance, and click Next; or, create a new Drift credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Drift endpoints. Each template is designed specifically for the corresponding Drift API endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Retrieve Conversation
Retrieves the full details for a specific conversation by its unique Drift conversation ID. Use this endpoint when you need to pull metadata and status information for a known conversation — such as creation time, assigned user, contact information, and conversation status (open, closed, or pending).
Enter the numeric Drift conversation ID in the Conversation ID field. Conversation IDs can be obtained from the Drift UI, from webhook events, or by first running the List Conversations endpoint to enumerate available conversations.
If no Conversation ID is provided, the request may return an error or empty result. Ensure a valid conversation ID is supplied before testing.
This endpoint retrieves a single conversation record. To retrieve messages within a conversation, use the Get Conversation Messages endpoint. To retrieve the full text transcript, use the Retrieve Conversation Transcript endpoint. For additional details, refer to the Drift Conversations API documentation.
Retrieve Conversation Transcript
Retrieves the full text transcript of all messages exchanged in a specific Drift conversation. Use this endpoint when you need the complete message history for a conversation — for example, for quality assurance review, sales coaching, or compliance archiving.
Enter the numeric Drift conversation ID in the Conversation ID field. This is the same identifier used in the Retrieve Conversation endpoint.
The transcript includes all messages in the conversation, including those from the contact, agents, and any bots that participated.
Conversation transcripts can include both human and bot-generated messages. The transcript is returned as an ordered list of message objects. For additional details, refer to the Drift Conversations API documentation.
Get Conversation Messages
Retrieves a paginated list of individual messages from a specific Drift conversation. Use this endpoint when you need structured message-level data from a conversation — for example, for analysis of response times, message content, or bot performance.
Enter the numeric Drift conversation ID in the Conversation ID field to specify which conversation's messages to retrieve.
The Next field is a pagination token used to retrieve subsequent pages of results. This field is managed automatically by Nexla when paginating through large result sets — leave it empty for the initial request.
This endpoint uses token-based pagination. Nexla will automatically follow pagination tokens to retrieve all available messages when this source is executed.
Message data includes the message body, sender ID, message type, and timestamp. This endpoint returns data from the $.data[*] path in the API response. For additional details, refer to the Drift developer documentation.
List Conversations
Returns a paginated list of conversations in your Drift organization, optionally filtered by conversation status. Use this endpoint to retrieve a broad set of conversations for reporting, auditing, or synchronizing conversation data to an external system.
Enter a value in the Limit field to control the maximum number of conversations returned per page. Leave this field empty to use the Drift API default page size.
Enter a value in the Status ID field to filter results by conversation status. Common Drift status IDs include:
1 — Open conversations
2 — Closed conversations
3 — Pending conversations
This endpoint uses token-based pagination. Nexla will automatically follow pagination tokens to retrieve all matching conversations when this source is executed.
Conversation data is returned from the $.data[*] path in the API response. For additional details on status IDs and response fields, refer to the Drift API documentation.
Retrieve Contact
Retrieves the full profile details for a specific Drift contact by its unique contact ID. Contacts in Drift represent people external to your organization who have interacted with your chatbots or been added through integrations. Use this endpoint to pull a single contact's attributes, custom fields, and engagement data.
Enter the numeric Drift contact ID in the Contact ID field. Contact IDs can be obtained from the Drift UI, from conversation records, or by first using the Get Contacts by Email endpoint to look up a contact by email address.
Contact records include standard fields (name, email, phone) as well as any custom attributes configured for your Drift organization. For additional details, refer to the Drift Contacts API documentation.
Get Contacts by Email
Searches for Drift contacts by email address or by an external identifier. Use this endpoint when you need to look up contacts using an email address or a non-Drift identifier such as a CRM record ID or external system ID.
Enter the email address to search for in the Email field. This performs a search against the email attribute of all contacts in your Drift organization.
To search by an external identifier instead of email, enter the identifier type in the ID Type field (for example, externalId) and the corresponding identifier value in the ID field.
Enter a numeric value in the Limit field to control the maximum number of contact records returned. Leave this field empty to use the Drift API default.
Contact results are returned from the $.contacts[*] path in the API response.
You can search using either the Email field alone or a combination of the ID Type and ID fields. For additional details on external ID types, refer to the Drift Contacts API documentation.
List Custom Attributes
Returns a list of all custom contact attributes defined in your Drift organization. Use this endpoint to discover what custom fields are available for contacts in your account — useful for mapping Drift contact attributes to fields in other systems.
No additional parameters are required for this endpoint. Nexla will retrieve all custom attributes configured for contacts in your Drift account automatically.
Results are returned from the $.data[*] path in the API response, with each element representing one custom attribute definition.
Custom attribute definitions include the attribute name, data type, and label. For additional details, refer to the Drift API documentation.
Get User
Retrieves the profile and availability information for a single Drift user (agent) by their unique user ID. Users in Drift are members of your organization — agents, managers, or admins — who interact with contacts through conversations or manage the platform.
Enter the numeric Drift user ID in the User ID field. User IDs can be obtained from the Drift UI or by first using the List Users endpoint to enumerate all users in your organization.
User data includes the agent's name, email, availability status, and role. For additional details, refer to the Drift API documentation.
Get Multiple Users
Retrieves profile information for one or more Drift users in a single API call by providing their user IDs. Use this endpoint when you need to retrieve data for a known set of users without enumerating all users in the organization.
Enter one or more Drift user IDs in the User IDs field. To retrieve multiple users, provide the IDs as a comma-separated list (for example, 12345,67890).
Results are returned from the $.data[*] path in the API response.
For additional details on user ID formats and response fields, refer to the Drift API documentation.
List Users
Returns a complete list of all users (agents) in your Drift organization. Use this endpoint to retrieve a full roster of your Drift team members, including their IDs, names, email addresses, and availability statuses — for example, to synchronize your Drift users with an external HR or CRM system.
No additional parameters are required for this endpoint. Nexla will retrieve all users in your Drift organization automatically.
Results are returned from the $.users[*] path in the API response.
Retrieves the details for a single Drift account by its unique account ID. Accounts in Drift represent companies or organizations associated with your contacts, and typically correspond to records in your CRM. Use this endpoint when you need to pull the attributes, domain, and custom properties for a specific account.
Enter the numeric Drift account ID in the Account ID field. Account IDs can be obtained from the Drift UI or by first using the List Accounts endpoint to enumerate accounts in your organization.
For additional details on account data fields and custom properties, refer to the Drift API documentation.
List Accounts
Returns a paginated list of all accounts in your Drift organization. Use this endpoint to synchronize your Drift account records with an external system such as a CRM, data warehouse, or analytics platform.
No additional parameters are required for this endpoint. Nexla will automatically paginate through all available accounts using offset-based pagination.
Results are returned from the $.accounts[*] path in the API response.
This endpoint uses offset-based pagination with a default page size of 100 records. Nexla handles pagination automatically when running this source. For additional details, refer to the Drift Accounts API documentation.
Retrieve Bot Playbooks
Returns a list of all bot playbooks configured in your Drift organization. Playbooks are automated conversation workflows that define how Drift's chatbot interacts with website visitors. Use this endpoint to audit your playbook library, track active playbooks, or synchronize playbook configuration with an external system.
No additional parameters are required for this endpoint. Nexla will retrieve all playbooks configured in your Drift account automatically.
Results are returned from the $.playbooks[*] path in the API response.
Returns a list of all Conversational Landing Pages (CLPs) configured in your Drift organization. CLPs are standalone pages that replace traditional lead capture forms with real-time Drift conversations, allowing visitors to engage directly with your chatbot or sales team. Use this endpoint to audit your CLP library or synchronize CLP configuration with external reporting tools.
No additional parameters are required for this endpoint. Nexla will retrieve all CLPs configured in your Drift account automatically.
Results are returned from the $.clps[*] path in the API response.
Returns a list of all teams defined in your Drift organization. Teams are groups of Drift users (agents) that can be assigned to conversations or targeted by playbooks. Use this endpoint to audit your team structure or synchronize team data with an external system.
No additional parameters are required for this endpoint. Nexla will retrieve all teams in your Drift organization automatically.
Results are returned from the $.teams[*] path in the API response.
Returns a list of all Drift teams that a specific user belongs to. Use this endpoint when you need to determine a user's team memberships — for example, to understand routing configurations or to synchronize user-team relationships with an external system.
Enter the numeric Drift user ID in the User ID field. The teams that this user belongs to will be returned in the response.
Results are returned from the $.teams[*] path in the API response.
Returns metadata and scope information about a given Drift access token. Use this endpoint to verify the scopes, organization, and user associated with an access token — useful for validating credential configuration or auditing token permissions.
Enter the Drift access token you want to inspect in the Access Token field. The API will return information about this token, including its associated scopes and organization.
Retrieves all personal data stored in Drift that is associated with a specific email address, in support of GDPR data access requests. Use this endpoint when responding to a data subject access request (DSAR) to compile all information Drift holds about an individual.
Enter the email address of the data subject in the Email Address field. Drift will return all personal data associated with this email address from across your organization's Drift account.
Results are returned from the $.data[*] path in the API response.
This endpoint is intended for compliance use cases and should be used in accordance with your organization's GDPR data handling policies. For additional details, refer to the Drift GDPR API documentation.
Search Users via SCIM
Returns a list of Drift users using the SCIM (System for Cross-domain Identity Management) protocol. SCIM is an open standard used for automating the provisioning and deprovisioning of user accounts between identity providers (such as Okta or Azure AD) and applications. Use this endpoint to synchronize Drift user data with your identity management system.
No additional parameters are required for this endpoint. Nexla will retrieve all SCIM user records in your Drift organization automatically.
Results are returned from the $.Resources[*] path in the API response, following the SCIM schema.
SCIM user records follow the SCIM 2.0 schema and include standard user attributes such as userName, displayName, and emails. For additional details, refer to the Drift SCIM API documentation.
Get User via SCIM
Retrieves a single Drift user by their SCIM ID using the SCIM protocol. Use this endpoint when you need to retrieve the SCIM-formatted profile for a specific user — for example, to verify provisioning status or synchronize a user record with an identity provider.
Enter the SCIM user ID in the Id field. This is the SCIM-assigned identifier for the user, which may differ from the standard Drift user ID.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Drift data sources can also be manually configured to ingest data from any valid Drift API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The base URL for the Drift API is https://driftapi.com (for example, https://driftapi.com/accounts to list all accounts). Drift list responses typically use $.data[*] as the path to data, while endpoints such as contact search and account listing use $.contacts[*] and $.accounts[*] respectively. You do not need to include the Authorization header — Nexla automatically includes the Bearer token from your Drift credential in every API request.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Drift data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Drift destination, and select the Send to Destination option from the menu. Select the Drift connector from the list of available destination connectors, then select the credential that will be used to connect to the Drift organization, and click Next; or, create a new Drift credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Drift endpoints. Each template is designed specifically for the corresponding Drift API endpoint, making destination setup easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create Contact
Creates a new contact record in your Drift organization. Use this endpoint to add new leads, prospects, or customers to Drift — for example, when syncing new contacts from a CRM, marketing automation platform, or data warehouse into Drift.
No URL parameters are required for this endpoint. The contact attributes (such as name, email, and any custom fields) should be included in the data payload sent from the Nexset.
The request body is sent as a JSON object. Ensure that the Nexset fields are mapped to the appropriate Drift contact attribute names before activating this destination.
Drift contact records support both standard attributes (name, email, phone) and custom attributes defined in your organization's Drift account. For a complete list of supported contact fields and the request body format, refer to the Drift Contacts API documentation.
Update Contact
Updates an existing Drift contact by their Drift contact ID. Use this endpoint to modify contact attributes such as name, email, phone, or custom properties — for example, when syncing updated CRM data or enriching contact records with new information from an external system.
Enter the Drift contact ID in the Contact ID field. This is the numeric identifier assigned by Drift to the contact record. The contact with this ID will be updated with the data from the Nexset payload.
Only the fields included in the request payload will be updated. Fields not included in the payload will retain their existing values (PATCH behavior).
Contact IDs can be retrieved using the Retrieve Contact or Get Contacts by Email source endpoints. For additional details on updatable fields, refer to the Drift Contacts API documentation.
Update Contact via Non-Drift ID
Updates a Drift contact using an external identifier rather than the Drift contact ID. Use this endpoint when you want to update contacts by matching them to an external system's identifier — such as a CRM record ID, email address, or other external ID — without needing to know the Drift-assigned contact ID.
Enter the external identifier type in the ID Type field. This specifies which type of external identifier is being used to locate the contact. Common values include:
email — Locate the contact by email address
externalId — Locate the contact by an external CRM or system ID previously set on the contact
Enter the value of the external identifier in the ID field. This is the actual identifier value corresponding to the type entered in the ID Type field.
The contact attributes to update should be included in the data payload sent from the Nexset.
This endpoint is particularly useful for update workflows where you are pushing data from an external system (such as a CRM) and only have access to that system's own identifiers rather than Drift-native contact IDs. For additional details, refer to the Drift Contacts API documentation.
Delete Contact
Deletes a contact record from Drift by its Drift contact ID. This endpoint performs a standard contact deletion and is distinct from the GDPR purge endpoint, which deletes personal data by email address for compliance purposes. Use this endpoint to remove stale, duplicate, or unwanted contact records from your Drift organization.
Enter the Drift contact ID in the Contact ID field. The contact with this ID will be permanently deleted from your Drift organization.
:::warning Important
Contact deletion is permanent and cannot be undone. Verify that the correct Contact ID is being passed before activating this destination. For GDPR-related data deletion by email address, use the GDPR Data Deletion endpoint instead.
:::
Post Timeline Event
Creates a new timeline event on a Drift contact's activity timeline. Timeline events allow you to record external activities — such as product events, CRM updates, or behavioral triggers — directly on a contact's Drift record. This enables your sales team to see a unified view of prospect activity within Drift conversations.
Enter the Drift contact ID in the Contact ID field. The timeline event will be added to this contact's activity history.
Include the event details in the data payload sent from the Nexset. Timeline event payloads typically include an event type, timestamp, and any relevant attributes describing the event.
Timeline events are visible to agents within Drift conversations and can be used to personalize outreach based on recent contact activity. For additional details on the event payload format, refer to the Drift Contacts API documentation.
Unsubscribe Contacts From Emails
Unsubscribes one or more email addresses from Drift email communications. Use this endpoint to honor opt-out requests, maintain compliance with email marketing regulations, or synchronize unsubscribe lists from an external system into Drift.
Include the list of email addresses to unsubscribe in the data payload sent from the Nexset. The request body should contain the email addresses in the format expected by the Drift Emails API.
This endpoint is designed for bulk unsubscribe operations driven by data from external systems. For additional details on the request body format, refer to the Drift Emails API documentation.
Create Conversation
Creates a new conversation in Drift. Use this endpoint to programmatically initiate conversations — for example, to proactively start a conversation with a contact as part of an automated outreach workflow or to create conversations triggered by external events.
No URL parameters are required for this endpoint. The conversation details (such as the contact to associate, the initial message, and the assigned user) should be included in the data payload sent from the Nexset.
For additional details on the conversation creation payload format, refer to the Drift API documentation.
Update Conversation
Updates an existing Drift conversation's status or assigned user. Use this endpoint to programmatically close, open, or mark conversations as pending, or to reassign conversations to different agents — for example, as part of an automated triage or escalation workflow.
Enter the Drift conversation ID in the Conversation ID field. This is the numeric identifier for the conversation to update.
Include the update fields in the data payload. Common updatable fields include:
status — Set to open, closed, or pending to change conversation status
assignedAgentId — Set to a Drift user ID to reassign the conversation to a different agent
For additional details on updatable conversation fields and status values, refer to the Drift API documentation.
Create Message
Sends a new message to an existing Drift conversation. Use this endpoint to programmatically send messages from a bot or agent — for example, to deliver automated follow-up messages, share information triggered by external events, or add messages to conversations as part of a workflow.
Enter the Drift conversation ID in the Conversation ID field. The message will be posted to this conversation.
Include the message content in the data payload sent from the Nexset. The payload supports plain text messages as well as rich content with buttons and user attribution.
Messages can be attributed to a specific Drift agent by including a user ID in the payload, allowing automated messages to appear as if sent by a named agent. For additional details on message payload formats, refer to the Drift developer documentation.
Create Account
Creates a new account record in Drift. Accounts in Drift represent companies or organizations associated with your contacts and typically correspond to records in your CRM. Use this endpoint to sync new company records from an external system into Drift — for example, from Salesforce, HubSpot, or a data warehouse.
No URL parameters are required for this endpoint. The account attributes (such as name, domain, owner, and custom properties) should be included in the data payload sent from the Nexset.
For additional details on the account creation payload format and supported fields, refer to the Drift API documentation.
Update Account
Updates an existing Drift account record's properties, including name, domain, and custom attributes. Use this endpoint to keep Drift account data synchronized with an authoritative source such as a CRM or data warehouse.
Enter the Drift account ID in the Account ID field. The account with this ID will be updated with the data from the Nexset payload.
Only the fields included in the request payload will be updated. Fields not included in the payload will retain their existing values (PATCH behavior).
Account IDs can be retrieved using the Retrieve Account or List Accounts source endpoints. For additional details on updatable fields, refer to the Drift Accounts API documentation.
Delete Account
Deletes an account record from Drift by its Drift account ID. Use this endpoint to remove outdated or unwanted account records from your Drift organization — for example, as part of a data cleanup workflow triggered by account deletions in an external CRM.
Enter the Drift account ID in the Account ID field. The account with this ID will be permanently deleted from your Drift organization.
:::warning Important
Account deletion is permanent and cannot be undone. Verify that the correct Account ID is being passed before activating this destination.
:::
Update User
Updates a Drift user's (agent's) profile information, including name, email, phone, locale, avatar URL, and availability status. Use this endpoint to keep Drift user profiles synchronized with an external identity or HR system.
Enter the Drift user ID in the User ID field. This is a required field — the user with this ID will be updated with the data from the Nexset payload.
Include the fields to update in the data payload. Only the fields provided in the payload will be changed; all other user attributes will remain unchanged.
User IDs can be retrieved using the List Users or Get User source endpoints. For additional details on updatable user fields, refer to the Drift developer documentation.
Provision User via SCIM
Creates a new Drift user account using the SCIM (System for Cross-domain Identity Management) protocol. Use this endpoint to automate user provisioning as part of an identity management workflow — for example, when onboarding new employees whose accounts need to be created in Drift as part of an automated provisioning process.
No URL parameters are required for this endpoint. The user profile information (following the SCIM 2.0 schema) should be included in the data payload sent from the Nexset.
The request body must conform to the SCIM 2.0 User schema, including required fields such as userName and at least one email address.
Replaces a Drift user resource entirely using the SCIM PUT method. Unlike PATCH, a PUT request replaces the entire user resource with the supplied payload, so all required attributes must be included. Use this endpoint for full user profile replacements as part of an identity provider synchronization workflow.
Enter the SCIM user ID in the Id field. This is the SCIM-assigned identifier for the user to replace.
The complete SCIM user resource (all required fields) must be included in the data payload. Omitted optional fields will be cleared.
Partially updates a Drift user resource using the SCIM PATCH method. Unlike PUT, a PATCH request only updates the attributes included in the payload, leaving all other attributes unchanged. Use this endpoint when you need to update specific user attributes — such as availability status or display name — without overwriting the entire user record.
Enter the SCIM user ID in the Id field. This is the SCIM-assigned identifier for the user to update.
Include only the attributes to be modified in the data payload, following the SCIM PATCH operation format.
Deletes a Drift user account using the SCIM protocol. Use this endpoint to automate user deprovisioning — for example, when an employee leaves the organization and their Drift account should be removed as part of an automated offboarding workflow driven by your identity provider.
Enter the SCIM user ID in the Id field. This is the SCIM-assigned identifier for the user to delete.
:::warning Important
User deprovisioning via SCIM is permanent. Ensure that the correct SCIM user ID is being passed before activating this destination.
:::
GDPR Data Deletion
Permanently deletes all personal data associated with a specific email address from your Drift organization, in support of GDPR right-to-erasure requests. Use this endpoint when processing data subject deletion requests (DSAR) to ensure full compliance with GDPR obligations.
Enter the email address of the data subject in the Email Address field. All personal data associated with this email address will be permanently and irreversibly deleted from your Drift account.
:::danger Critical
GDPR data deletion is permanent and cannot be reversed. This endpoint deletes all personal data associated with the specified email address across your Drift organization. Ensure this operation is authorized before activating this destination.
:::
Drift destinations can also be manually configured to send data to any valid Drift API endpoint.
The base URL for the Drift API is https://driftapi.com (for example, https://driftapi.com/contacts to create a new contact); for update operations, include the resource ID at the end of the URL (e.g., https://driftapi.com/contacts/12345). The Drift API expects request bodies in JSON format for all write operations. You do not need to include the Authorization header — Nexla automatically includes the Bearer token from your Drift credential in every API request.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Drift endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Drift API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
