Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sixtyfour.ai/llms.txt

Use this file to discover all available pages before exploring further.

Workflows in Sixtyfour are linear pipelines that process data through a sequence of blocks. Each block performs a specific function — importing data, finding and enriching it, cleaning and organizing it, or sending results. Every workflow follows the same pattern: Open the Workflow Editor to start building. For API-driven workflow management, see the Workflows API reference.

Source Blocks

For a complete list of source blocks, see the Workflow Blocks Reference.
Every workflow starts with a source block. Pick one based on where your data lives.
BlockDescription
SearchFind people or companies from Sixtyfour’s dataset using a natural language query. The most common starting point.
Read NotebookPull data from a previously saved Sixtyfour notebook.
Google MapsSearch for local businesses and places.
GitHub Find PeopleDiscover developers from GitHub repositories (contributors, stargazers, watchers).
GitHub SearchSearch GitHub for repositories, users, or code.
KagglePull competitors from Kaggle competition leaderboards.
Y CombinatorFetch YC company data by batch, industry, or tags.
HubSpot ImportImport contacts or companies directly from HubSpot CRM.
XSearch X/Twitter for profiles (e.g., “AI researchers”, “crypto founders in NYC”).
TikTokGet the following list from TikTok profile URLs or handles.
Incoming WebhooksReceive data from external systems via API call.
Workflows starting with an Incoming Webhooks block can be triggered via API. Other source blocks run from the Workflow Editor.

Enrichment Blocks

Enrichment blocks research and append new information to each row. The block you choose depends on whether you’re working with Lead (people) or Company (organization) data.

Core Enrichment

BlockInput TypeDescription
Enrich PeopleLeadAI web research on people. Define custom return fields (job title, LinkedIn URL, skills, etc.) and the system researches each person.
Enrich CompaniesCompanyAI web research on companies. Define custom return fields (revenue, employee count, industry, etc.). Optionally discover people at each company.

Contact Finding

BlockInput TypeDescription
Email addressLeadFind professional or personal email addresses. Returns a verification status (OK, UNKNOWN, RISKY, NOT_FOUND).
PhoneLeadFind phone numbers.
Verify EmailLeadCheck if existing email addresses are valid and deliverable.
Verify PhoneLeadCheck if existing phone numbers are valid and return carrier, line type, activity score, prepaid flag, and country signals.

Reverse Lookup

BlockInput TypeDescription
Reverse EmailLeadLook up person and company info from an email address.
Reverse PhoneLeadLook up person and company info from a phone number.

Specialized

BlockInput TypeDescription
Web Research AgentAnyGeneral-purpose AI agent that browses the internet to answer custom questions per row. Best for highly specialized queries.
Scrape WebsiteAnyScrape web content from URLs in a column. Output as markdown or HTML; supports geo, JS rendering, and proxies.
Find SubdomainsCompanyFind subdomains for a domain using the DNSDB API; supports time filters.
BacklinksCompanyGet referring domains for a target domain or URL via DataForSEO Backlinks; supports pagination.
For the underlying APIs, see People Intelligence, Company Intelligence, Find Email, and Find Phone.

Transform Blocks

Transform blocks filter, deduplicate, reshape, and prepare data between enrichment and output.
BlockDescription
FilterKeep or remove rows based on column conditions (e.g., only verified emails, companies with 100+ employees).
DeduplicateRemove duplicate rows based on one or more columns.
Deduplicate with NotebookRemove rows that already exist in a specified notebook. Prevents duplicates across recurring runs.
Generate TextGenerate custom text per row using a prompt template with column references. Use {column_name} for substitution. Useful for personalized messaging.
LLM OutputGenerate structured or unstructured text per row using configurable LLM models. Use when you need typed output via a schema.
Remove ColumnsRemove selected columns from the output, keeping all rows intact.
Group ByGroup rows by column values with aggregation functions (sum, count, list, etc.).
Extract LeadsExtract people discovered during Company Enrichment into individual lead rows. Required before using any lead-only block on company-enriched data.
Leads to CompanyConvert lead rows into company rows with nested lead arrays.

Data Type Conversion

Sixtyfour workflows operate on two data types: Lead (people) and Company (organizations). Some blocks require a specific type.
If you run Enrich Companies with people discovery enabled, the output is still Company data. You must use the Extract Leads block to convert it to Lead data before using lead-only blocks like Find Email or Find Phone.

Output Blocks

Output blocks deliver your results. They are typically the final step in a workflow.
BlockDescription
NotebookSave results to a Sixtyfour notebook. Create a new notebook or append to an existing one.
SlackSend messages to a Slack channel. Use {column} for substitution and {@column} to tag users by email.
Outgoing WebhooksPOST workflow results to an external URL when the run completes. See Outgoing Webhooks.

Common Workflow Patterns

Find people and get their emails

Research companies, find decision-makers, get contact info

Enrich an existing list and save clean results

Import from CRM, enrich, and notify your team

Tips

  • Filter early. Filtering before enrichment reduces rows processed, saving time and credits.
  • Deduplicate across runs. Use Deduplicate with Notebook on recurring workflows to avoid saving the same results twice.
  • Request only what you need. Define only the return fields you need in enrichment blocks to keep results focused and costs efficient.
  • Bridge company to lead data. Use Extract Leads any time you need to go from company data to people data — it is the only way to cross that boundary.
  • To build programmatic workflows, see Programmatic Workflows.