All integrationsCRM & Contacts

Dex

Manage personal CRM contacts, reminders, and notes with the Dex API.

actions
20
triggers
6

Triggers

Start a workflow when something happens in Dex.

  • New contactStarts a workflow when new contact.
  • New reminderStarts a workflow when new reminder.
  • New tagStarts a workflow when new tag.
  • New groupStarts a workflow when new group.
  • New companyStarts a workflow when new company.
  • New contact noteStarts a workflow when new contact note.

Actions

Steps a workflow can run in Dex.

  • Get the current userRetrieve the authenticated user. Supports `include` (related records like `mobile_settings`, `workflow_settings`) and `fresh` (skip cache). Returns the canonical /v2 envelope `{ data: { user } }`. With any API key the response leaves out the account's stored credentials (`email_key`, `zapier_key`, saved sync sessions), and a workspace-bound key's `include` is ignored: its response carries no related records.
  • List contactsRetrieve contacts for the authenticated user with cursor pagination, filtering (`where`), sorting (`orderBy`), and field selection (`include` / `select`). Returns `{ data: { contacts: [...], pagination: { nextCursor, count } } }`.
  • Search contacts by nameName-only typeahead. Matches the contact's full name accent-insensitively (`f_unaccent`) and returns full contact rows in the list envelope `{ data: { contacts: [...] } }`. `query` is required. send `POST /v2/contacts/search` if you need an empty-query listing, a wider field fan-out, or geographic search.
  • Get a contactRetrieve a contact by ID. Email and phone relations are omitted by default; request them with `?include[contact_emails]=true` or `?include[contact_phone_numbers]=true`.
  • Create a contactCreate ONE contact. The common case. TanStack DB optimistic mutations, mobile add-contact, MCP tools. **Requires `Idempotency-Key`.** Returns `{ data: { contact: {...} } }` with status 201. For bulk create, use `POST /v2/contacts/batch`.
  • Update a contactPartially update a contact by its ID. **Requires `Idempotency-Key`.** Returns `{ data: { contact: {...} } }` with the post-update row. Also fires a Pub/Sub message to auto-add the contact to social groups when LinkedIn / Twitter / Instagram / etc. fields are set.
  • Delete a contactPermanently delete a contact by its ID. Returns the canonical bulk envelope: `{ data: { affected: 1, ids: [contactId] } }`. `Idempotency-Key` is optional.
  • List a contact's notesList one contact's notes, newest first, in the canonical notes list envelope, cursor-paginated. Also served in a workspace (`X-Dex-Workspace`), where it returns the workspace's shared notes on that contact plus your own private ones.
  • Create a noteCreate a note (a `timeline_items` row) optionally linked to contacts. Returns the created note in the canonical single-entity envelope.
  • Get a noteRetrieve a single note by id in the canonical single-entity envelope.
  • Update a notePartially update a note. PATCH semantics. only the supplied fields change. Returns the updated note.
  • Delete a noteDelete a note by id. Returns the bulk-ack envelope (`affected`, `ids`).
  • List remindersRetrieve all reminders for the authenticated user. Supports filtering, sorting, and cursor pagination. Recurring reminders are placed by their next occurrence: `orderBy` on `due_at_date` (the default sort) and `where[has_due_at_date]` compare `next_occurrence_at` for a recurring reminder, falling back to `due_at_date`, and `due_at_date` for every other reminder, so a recurring row can sort or match on a date other than the `due_at_date` it returns. A cursor is valid only with
  • Get a reminderRetrieve a single reminder by its unique ID. Returns the canonical /v2 envelope `{ data: { reminder } }`. see Migration notes below. With `X-Dex-Workspace`, `include[tags]` or `include[reminders_tags]` (or the same keys in `select`) adds `reminders_tags`: the reminder's workspace tags as `{ tag_id, tags: { id, name } }`, by name. Reminder tags are workspace-only: a Personal request asking for them gets `reminders_tags: []`.
  • Create a reminderCreate a new reminder for the authenticated user. With `X-Dex-Workspace`, `tag_ids` (up to 100 workspace tag ids; duplicates are dropped) tags the reminder; a tag outside the workspace is 400 `invalid_reference` and creates nothing. Reminder tags are workspace-only: a Personal request with `tag_ids` is 400 `workspace_context_required`. **Requires an `Idempotency-Key` header**. see Idempotency below. Returns `{ data: { reminder: {...} } }` with status 201.
  • Delete a reminderPermanently delete a reminder by its ID. `Idempotency-Key` is optional on DELETE (the operation is HTTP-idempotent by semantics). Returns `{ data: { affected: 1, ids: [reminderId] } }`.
  • List tagsList the authenticated user's tags with cursor pagination (`?take=` / `?cursor=`). Pass `?include[contacts_count]=true` to attach `_count.tags_contacts` per tag; sort with `?orderBy[name]=asc|desc` or `?orderBy[contacts_count]=asc|desc`. Returns `{ data: { tags: [...], pagination: { nextCursor } } }`.
  • List groupsList all of the authenticated user's groups. Returns the canonical list envelope: `{ data: { groups: [...] } }`. Supports `?orderBy[name]=asc|desc` and `?orderBy[number_of_contacts]=asc|desc`, plus `?where[has_parent]=true` / `?where[has_subgroups]=true` for sidebar tree navigation.
  • List companiesList the workspace's companies by name, then id. `archived` false (default) lists active companies, true archived ones only. `assignee_id` filters on the company's owner: a user id (active or not), `me` for the caller, or `none` for companies without an owner. `limit` (default 100, max 500) and `cursor` (from `pagination.nextCursor`; a cursor this endpoint did not issue is 400 `invalid_cursor`). Workspace-only: send the `X-Dex-Workspace` header (404 `record_not_found` without
  • Get a companyGet one company by its ID, archived or not. 404 `record_not_found` when it is not in the workspace. Workspace-only: send the `X-Dex-Workspace` header (404 `record_not_found` without it). Returns `{ data: { company: {...} } }`.

Automate Dex with Lodol.

Connect Dex, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.