Drift
Create, read, update, delete and search Drift contacts, and list the contact attributes an organisation has defined, through the Drift platform API.
OCNORA ships 6 typed Drift operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://driftapi.com through the HTTP node with the same credential.
Before you connect Drift
- Authentication
- OAuth 2.0
- Credential
- {"client_id": "…", "client_secret": "…", "refresh_token": "…"}, or {"access_token": "…"} for an Install-to-Drift token
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Drift
Operations, grouped by what they do to your data.
Create and send 1
Read and search 3
Update 1
Delete and cancel 1
A sample Drift workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Drift trigger is needed.
- 2Get Contactdrift.get_contactRetrieve one contact by Drift's numeric contact id.
- 3Create Contactdrift.create_contactCreate a contact. Email is the only attribute Drift requires; sending an external_id makes that the de-duplication key instead of the email.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 6
- Create ContactCreate a contact. Email is the only attribute Drift requires; sending an external_id makes that the de-duplication key instead of the email.drift.create_contact
- Delete ContactRemove a contact from the Drift Contacts view. Drift documents this as indexing removal; a full erasure is its separate GDPR API.drift.delete_contact
- Get ContactRetrieve one contact by Drift's numeric contact id.drift.get_contact
- Search ContactsFind contacts by email address or by your own external id. Email is not unique in Drift, so this always emits an array.drift.list_contacts
- List Contact AttributesList every contact property Drift knows, standard and custom, with its internal name and type. Needs the all_contact_read scope on the app.drift.list_custom_attributes
- Update ContactPatch a contact's attributes. Drift reports success only when something actually changed, so at least one attribute must be given.drift.update_contact
Drift questions
- How does OCNORA authenticate with Drift?
- With a stored OAuth 2.0 credential, shaped {"client_id": "…", "client_secret": "…", "refresh_token": "…"}, or {"access_token": "…"} for an Install-to-Drift token. A connection test can check it when you add it.
- What can I automate with Drift?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Drift operation I need is not listed?
- Call https://driftapi.com from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Drift?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Drift calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Drift workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.