Drift
CRM & salesOAuth 2.0credential probe
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. Anything not covered by a typed node reaches https://driftapi.com through the HTTP node with the same credential.
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
Run your first Drift workflow today.
Create a free workspace, add the connection, pick a template or describe the workflow to Build with AI. Workflow Health checks it before it runs.