Sixtyfour workflows process data in batch — upload a list or send records via API, and every row flows through your enrichment pipeline automatically. Use the Workflow Editor for a no-code approach, or trigger workflows programmatically with the Workflows API. For a full reference of available blocks, see Building Workflows.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.
Batch Processing in the Workflow Editor
The Workflow Editor lets you build and run batch pipelines without writing code. See Building Workflows for a full walkthrough of how to import, find, enrich, clean, and send data.Example
A typical batch pipeline to find and verify emails for a list of people:Batch Processing via API
Trigger workflows programmatically by sending records to a workflow that starts with a Webhook block. Build the workflow in the editor, then call it from your code.Step 1: Trigger the workflow
Send your batch of records toPOST /workflows/run with a webhook_payload array. Each object in the array is one row.
job_id for tracking:
Step 2: Poll for progress
Check workflow status withGET /workflows/runs/{run_id}/live_status. Poll every 5-10 seconds until overall_status reaches completed, failed, or cancelled.
overall_progress_percentage to track progress.
Step 3: Download results
Once completed, retrieve signed download URLs for the result CSV files.Tips
- Filter before enrichment. Reducing rows early saves time and credits.
- Deduplicate across runs. Use the Deduplicate with Notebook block on recurring batch workflows to avoid processing the same records twice.
- Request only what you need. Define only the return fields you need in enrichment blocks to keep results focused and costs efficient.
- Use Webhook for API triggers. Any workflow you want to trigger programmatically must start with a Webhook source block.