Sixtyfour logo

Integrate Sixtyfour with your AI CRM

Sixtyfour provides AI-powered people and company enrichment, contact discovery, verification, and search.

Explore Triggers and Actions

Autocomplete Search Filter

Return autocomplete suggestions for one supported people or company search filter field. Queries can contain sensitive targeting criteria such as location, education, job title, industry, language, or technology. This read-only endpoint is limited by Sixtyfour to 200 requests per minute per user.

ActionTry it

Check Balance

Validate the connected API key and return its organization's current Sixtyfour credit balance without consuming credits. This does not identify the connected user.

ActionTry it

Clear Search History

Permanently delete every search-history entry for the connected Sixtyfour account. This is destructive, affects all saved searches, and cannot be undone.

ActionTry it

Create Exclusion List

Create an immutable, organization-owned people or company exclusion list from an uploaded CSV, inline identifiers, or a saved search. Materialization is asynchronous; poll the returned ID with GET_EXCLUSION_LIST. Sources and saved list state may contain sensitive person or company identifiers.

ActionTry it

Delete Exclusion List

Soft-delete an organization-owned exclusion list and evict its cached member set. This destructive state mutation removes the list from use in searches; verify the list ID before deleting sensitive organization search state.

ActionTry it

Delete Search History Entry

Permanently delete one Sixtyfour search-history entry by ID. This destructive action cannot be undone; use CLEAR_SEARCH_HISTORY only when every entry should be removed.

ActionTry it

Enrich Company

Synchronously research and enrich one company, optionally finding employees. The documented runtime can be several minutes depending on research depth; use START_COMPANY_ENRICHMENT for production. This billable action costs 0.3/1/5/15 credits at micro/low/medium/high, and high requires provider enablement. Company and employee enrichment may send or return sensitive identities, employment and contact details, profile URLs, source URLs, and evidence. Do not blindly retry after a timeout or ambiguous server error because the request may have been billed.

ActionTry it

Enrich LinkedIn Profile

Fetch one LinkedIn person or company profile and extract structured fields in a single model call. This billable action costs 0.3 credits per profile. It sends a profile URL and may return sensitive personal identifiers, employment details, contact data, profile content, source URLs, and evidence. Do not blindly retry after a timeout or ambiguous server error because the request may have been billed.

ActionTry it

Enrich Person

Synchronously research and enrich one person. The documented runtime is P95 about 5 minutes and can reach 10 minutes, so clients need at least a 15-minute timeout; use START_PEOPLE_ENRICHMENT for production. This billable action costs micro 0.3, low 1, medium 20, high 40, scout 10, or xhigh 250 credits per unit. High, scout, and xhigh require provider enablement and can return 403. It sends and may return sensitive personal identifiers, employment and contact data, profile URLs, source URLs, and evidence. Do not blindly retry after a timeout or ambiguous server error because the request may have been billed.

ActionTry it

Export Search Results

Start an asynchronous CSV export from exactly one completed search ID or parsed query. The export costs 0.1 credit per result and creates a billable export task. Poll the returned task ID with search status, then request a download URL from the completed task's resource handle. Do not retry this action after a timeout or ambiguous server response because an export may already be running or billed.

ActionTry it

Find Email

Synchronously find one person's professional or personal email and return the result in the same call; unlike asynchronous discovery, this action does not start a job or use a webhook. Professional discovery costs 0.5 credits per lead and personal discovery costs 2 credits per lead. This high-sensitivity operation sends personal and company identifiers and may return private contact data and source evidence. Do not blindly retry after a timeout or ambiguous 5xx response because the lookup may have completed and been billed.

ActionTry it

Find Emails

Synchronously find professional or personal emails for a batch of leads and return all results in the same call; unlike asynchronous bulk discovery, this action does not start a job or use a webhook. Professional discovery costs 0.5 credits per lead and personal discovery costs 2 credits per lead, so the total cost scales with the number of leads. This high-sensitivity operation sends personal and company identifiers and may return private contact data and source evidence. Do not blindly retry after a timeout or ambiguous 5xx response because the batch may have completed and been billed.

ActionTry it

Find Phone

Synchronously find one person's phone number and return the result in the same call; unlike asynchronous discovery, this action does not start a job or use a webhook. Discovery costs 3 credits per phone number found. This high-sensitivity operation sends personal identifiers and may return private phone data and source evidence. Do not blindly retry after a timeout or ambiguous 5xx response because the lookup may have completed and been billed.

ActionTry it

Find Phones

Synchronously find phone numbers for a batch of leads and return all results in the same call; unlike asynchronous bulk discovery, this action does not start a job or use a webhook. Discovery costs 3 credits per phone number found, so the total cost scales with successful discoveries across the batch. This high-sensitivity operation sends personal identifiers and may return private phone data and source evidence. Do not blindly retry after a timeout or ambiguous 5xx response because the batch may have completed and been billed.

ActionTry it

Get Deep Search Status

Poll the dedicated deep-search-only status route required for explicit endpoint mapping. For new deep-search workflows, GET_SEARCH_STATUS is the documented general route and also supports export tasks. This route does not support lookalike tasks. Status polling is free and retains normal safe-read retries.

ActionTry it

Get Exclusion List

Fetch one organization-owned exclusion list, including its materialization status and size. The name, source metadata, counts, and failure detail may describe sensitive people or company records.

ActionTry it

Get Job Status

Return the current status and, when complete, the task-dependent result for an asynchronous enrichment, email-discovery, or phone-discovery job. Polling is free; poll about every 10 seconds and stop on a terminal status. Completed results may contain sensitive personal identifiers, contact details, employment data, references, and evidence.

ActionTry it

Get Lookalike Search Status

Poll only a task returned by START_LOOKALIKE_SEARCH. The general GET_SEARCH_STATUS route rejects lookalike task IDs. On completion, use search_id with SEARCH_PEOPLE_AND_COMPANIES to page through results. Polling is free and retains normal safe-read retries.

ActionTry it

Get Search Download URL

Return signed URL metadata for a completed search or export without following or fetching the URL. The signed URL expires after 15 minutes. A subsequent fetch of that URL requires the Sixtyfour x-api-key header, but this action will not forward the connected API key to the returned URL.

ActionTry it

Get Search Filter Capabilities

Return Sixtyfour's current searchable fields, operators, nested paths, query limits, cache metadata, and per-result price for people or company filter search. Use this before constructing provider-native search filters.

ActionTry it

Get Search History Entry

Retrieve one decrypted saved-search envelope owned by the connected user or active team. The result can contain sensitive search queries, replay metadata, people or company identifiers, exports, and organization-owned search state. Inaccessible IDs are reported as not found.

ActionTry it

Get Search History Volume

Return search-history volume for a required date-time window. Counts concern sensitive team activity and may reflect saved queries, people or company searches, exports, and organization-owned search state.

ActionTry it

Get Search Limits

Return the maximum number of search rows the connected credential may request, retrieve, or export. Use this value instead of inferring an entitlement from a plan name.

ActionTry it

Get Search Status

Poll the general status route for a task returned by START_DEEP_SEARCH or a search export. Do not use it for lookalike tasks; use GET_LOOKALIKE_SEARCH_STATUS instead. Polling is free; poll every 10 to 15 seconds and stop on any status other than running.

ActionTry it

List Exclusion Lists

List the connected organization's people and company exclusion lists, most recent first. Returned names, source metadata, counts, and errors are organization-owned search state and may describe sensitive records.

ActionTry it

List Search Filter Field Values

Return the most common values for one supported people or company search field, optionally scoped by either simple filters or raw DSL filters. Use filter capabilities first to identify fields that support top values.

ActionTry it

List Search History

List one page of the connected team's decrypted saved-search history for logs and auditing. History can contain sensitive queries, people or company records, identifiers, exports, and organization-owned search state. The raw provider object is returned in result; inspect it for provider continuation data and pass any cursor back unchanged.

ActionTry it

Look Up People by Emails

Synchronously reverse-lookup a batch of people from email addresses. This high-sensitivity operation costs 0.5 credits per lookup, so total cost scales with the number of leads, and may return personal, employment, profile, and contact data. The complete provider JSON response appears in result. Do not blindly retry after a timeout or ambiguous 5xx response because the lookups may already have consumed credits.

ActionTry it

Look Up People by Phones

Synchronously look up people from a batch of phone-number leads and return the results. This sensitive-data operation costs 3 credits per lookup, so total cost scales with the number of leads. Do not blindly retry after a timeout or ambiguous response because lookups may already have consumed credits.

ActionTry it

Look Up Person by Email

Synchronously reverse-lookup one person from an email address. This high-sensitivity operation costs 0.5 credits per lookup and may return personal, employment, profile, and contact data. The complete provider JSON response appears in result. Do not blindly retry after a timeout or ambiguous 5xx response because the lookup may already have consumed credits.

ActionTry it

Look Up Person by Phone

Synchronously look up one person from a phone number and return the result. This sensitive-data operation costs 3 credits per lookup and sends a phone number and other supplied lead details to Sixtyfour. Do not blindly retry after a timeout or ambiguous response because the lookup may already have consumed credits.

ActionTry it

Search People and Companies

Run exactly one page of a people or company search from one query source, or continue using only a prior cursor. Do not loop automatically: Sixtyfour charges 0.1 credit per returned result and each page can incur an additional charge. This read-only action never stores search history. Queries and results may contain people or company records, identifiers, profiles, and organization-owned search state.

ActionTry it

Set Search History Favourite

Set or remove the favourite marker on one Sixtyfour search-history entry. This update is reversible: call it again with the opposite favourite value.

ActionTry it

Start Bulk Company Enrichment

Upload a CSV, JSON, JSONL, or NDJSON file and start an asynchronous company enrichment job. The provider accepts files up to 100 MB and 100,000 rows; file contents and row count are validated by Sixtyfour. Poll GET_JOB_STATUS with the returned task_id. Per-row base rates are 0.3/1/5/15 credits for micro/low/medium/high; the estimate can undercount find_people and other additions. Inputs and results can contain highly sensitive company, person, employment, contact, profile, source, and evidence data. Set idempotency_key and reuse it when retrying after a timeout or ambiguous 5xx response, because the billable job may already have started.

ActionTry it

Start Bulk Email Discovery

Start asynchronous professional or personal email discovery for a batch of leads. This high-sensitivity operation sends personal and company identifiers to Sixtyfour and may return private contact data and source evidence. Professional discovery costs 0.5 credits per lead and personal discovery costs 2 credits per lead, so total cost scales with the number of leads. The provider response appears in result; take any returned job identifier from there and pass it to SIXTYFOUR_GET_JOB_STATUS. Do not blindly retry after a timeout or ambiguous response because a billable job may already have started.

ActionTry it

Start Bulk People Enrichment

Upload a CSV, JSON, JSONL, or NDJSON file and start asynchronous people enrichment in bulk. The provider accepts files up to 100 MB and 100,000 rows; file contents and row count are validated by Sixtyfour. Tiers cost micro 0.3, low 1, medium 20, high 40, scout 10, or xhigh 250 credits per unit. High, scout, and xhigh require provider enablement and can return 403. The returned estimate is a floor and the final charge can be higher depending on options and processing. Uploaded rows may contain sensitive personal and contact data; send only data you are authorized to process. Poll SIXTYFOUR_GET_JOB_STATUS with the returned task_id. Supply idempotency_key for retry safety; after a timeout or ambiguous 5xx response, retry only with the same key because a billable job may already have started.

ActionTry it

Start Bulk Phone Discovery

Start asynchronous, high-sensitivity phone discovery for a batch of leads. This operation costs 3 credits per phone number found, so the total cost varies with successful discoveries. The provider response appears in result; take any returned job identifier from there and poll SIXTYFOUR_GET_JOB_STATUS with it. Do not blindly retry after a timeout or ambiguous 5xx response because a billable bulk job may already have started.

ActionTry it

Start Company Enrichment

Start an asynchronous company research job and return its task ID for polling. This credit-metered action costs 0.3/1/5/15 credits at micro/low/medium/high; high requires provider enablement. Company and optional employee enrichment may send or return employee identities, employment details, profiles, source URLs, and evidence. Do not blindly retry after a timeout or ambiguous 5xx response because a billable job may already have started.

ActionTry it

Start Deep Search

Start an asynchronous agentic people or company search from natural language. Save task_id and poll GET_SEARCH_STATUS, the general route for deep-search and export tasks; GET_DEEP_SEARCH_STATUS is the deep-search-only mapped alternative. On completion, pass search_id to SEARCH_PEOPLE_AND_COMPANIES. Deep Search costs 0.1 credit per result. Reuse a supplied search_id after an ambiguous outcome; without one, determine whether a task started before retrying.

ActionTry it

Start Email Discovery

Start an asynchronous search for one person's professional or personal email. This operation is credit-metered: professional discovery costs 0.5 credits per lead and personal discovery costs 2 credits per lead. It sends person identifiers to Sixtyfour and may return private contact data and source evidence. The provider response appears in result; take any returned job identifier from there and pass it to SIXTYFOUR_GET_JOB_STATUS. Do not blindly retry after a timeout or ambiguous 5xx response because a billable job may already have started.

ActionTry it

Start Lookalike Search

Start an asynchronous people lookalike search from exactly one seed source. Prefer linkedin_urls for a self-contained call; csv_resource_handle_id requires Sixtyfour's documented upload route, which this toolkit does not expose. Poll only GET_LOOKALIKE_SEARCH_STATUS, then use its search_id with SEARCH_PEOPLE_AND_COMPANIES. This start can consume search credits; the saved pricing documentation does not publish a separate lookalike rate. Do not blindly retry after an ambiguous outcome because a billable task may already have started.

ActionTry it

Start People Enrichment

Start an asynchronous research job for one person and return a job ID for GET_JOB_STATUS. This operation costs micro 0.3, low 1, medium 20, high 40, scout 10, or xhigh 250 credits per unit. High, scout, and xhigh require provider enablement and can return 403. Requests and results may contain sensitive names, employment data, contact identifiers, profiles, source URLs, and evidence. Supply dispatch_id for retry safety; after a timeout or ambiguous 5xx response, do not retry without the same dispatch_id because a billable job may already have started.

ActionTry it

Start People Lookup by Emails

Start asynchronous reverse-email lookup for a batch of people. This high-sensitivity operation costs 0.5 credits per lookup, so total cost scales with the number of leads, and may return personal, employment, profile, and contact data. The provider response appears in result; pass its job identifier to SIXTYFOUR_GET_JOB_STATUS. Do not blindly retry after a timeout or ambiguous 5xx response because a billable bulk job may already have started.

ActionTry it

Start People Lookup by Phones

Start asynchronous lookups of people from a batch of phone-number leads. This sensitive-data operation costs 3 credits per lookup, so total cost scales with the number of leads. The provider response appears in result; pass its returned job identifier to GET_JOB_STATUS. Do not blindly retry after a timeout or ambiguous response because a billable bulk job may already have started.

ActionTry it

Start Person Lookup by Email

Start an asynchronous reverse-email lookup for one person. This high-sensitivity operation costs 0.5 credits per lookup and may return personal, employment, profile, and contact data. The provider response appears in result; pass its job identifier to SIXTYFOUR_GET_JOB_STATUS. Do not blindly retry after a timeout or ambiguous 5xx response because a billable job may already have started.

ActionTry it

Start Person Lookup by Phone

Start an asynchronous lookup of one person from a phone number. This sensitive-data operation costs 3 credits per lookup and sends a phone number and other supplied lead details to Sixtyfour. The provider response appears in result; pass its returned job identifier to GET_JOB_STATUS. Do not blindly retry after a timeout or ambiguous response because a billable job may already have started.

ActionTry it

Start Phone Discovery

Start an asynchronous search for one person's phone number. This credit-metered operation costs 3 credits per phone number found and sends person identifiers that may lead to private phone data and source evidence. The provider response appears in result; take any returned job identifier from there, pass it to GET_JOB_STATUS, and poll about every 10 seconds. Do not blindly retry after a timeout or ambiguous 5xx response because a billable job may already have started.

ActionTry it

Verify Email

Check whether one email address can receive mail and return its delivery status and optional 0-100 score. This transmits and evaluates personal contact data. The operation consumes 0.1 Sixtyfour credits unless the result is UNKNOWN; documented 503 failures are also not charged.

ActionTry it

How the Sixtyfour integration works

The Sixtyfour integration connects your Dench AI CRM directly to Sixtyfour, so agents can read and act on your Sixtyfour data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.

48 actions are available for agents to invoke on your behalf. Every call runs through Sixtyfour's own authorization, scoped to the account you connect.

Set up Sixtyfour in Dench

  1. 1

    Sign in to your Dench workspace and open Integrations.

  2. 2

    Find Sixtyfour and click Connect — you'll authorize access through Sixtyfour's own sign-in flow. No API keys or code required.

  3. 3

    Ask an agent to use Sixtyfour in chat, or call it from an automation.

  4. 4

    Manage or disconnect the connection any time from workspace settings.

Frequently asked questions

How does the Sixtyfour integration work with Dench?

The Dench Sixtyfour integration connects your AI CRM to Sixtyfour, so AI agents can work with your Sixtyfour data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.

What actions can AI agents perform with Sixtyfour via Dench?

The Sixtyfour integration currently exposes 48 actions, including Autocomplete Search Filter, Check Balance, Clear Search History, Create Exclusion List, Delete Exclusion List, and Delete Search History Entry. Agents invoke them on your behalf from chat or from automations.

Do I need to write code to connect Sixtyfour to Dench?

No. You connect Sixtyfour from your Dench workspace using Sixtyfour's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.

Is the Sixtyfour integration secure?

Connections are authorized through Sixtyfour's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Sixtyfour connection from your workspace settings at any time.

Sixtyfour | Dench AI CRM