You keep your workflows
Build and run automations where your team already works: Clay tables, n8n canvases, Make scenarios, CRM flows.
Integrations
The data engine behind your GTM stack
BlitzAPI plugs into the orchestration tools you already use. Keep your workflows in Clay, n8n, or your CRM, and let BlitzAPI supply the companies, contacts, emails, and signals.
WORKFLOW
INTEGRATIONSLIVEBLITZ API · V2
Orchestrate anywhere, enrich from one place
BlitzAPI is not another platform to manage. It is the data layer your existing tools call.
Standard REST, everywhere
Every integration uses the same v2 endpoints and x-api-key header, so a recipe built in one tool ports to any other.
Built for volume
High-volume B2B data designed for waterfalls and batch runs, without per-record anxiety.
Works with your stack
The tools your team already uses, one data engine behind them.
ClayGuidePaste a cURL command into Clay's HTTP API and build high-volume enrichment waterfalls without writing code.n8nGuideChain waterfall search, enrichment, and CRM sync into autonomous workflows with the HTTP Request node.MakeGuideAdd BlitzAPI to thousands of app scenarios with the HTTP module: Airtable, HubSpot, Google Sheets, and more.
ZapierHTTP moduleTrigger enrichment from any Zap with a webhook step and write results back to your connected apps.
AirtableHTTP moduleEnrich bases with company, contact, and email data through automations or your orchestration tool of choice.
Google SheetsHTTP moduleTurn spreadsheets into enrichment pipelines via Make, n8n, or a simple script.
HubSpotHTTP moduleRefresh company records, add decision makers, and re-verify emails on workflow triggers.
SalesforceHTTP modulePower flows and buttons with live enrichment: resolve, refresh, and complete records on demand.
PipedriveHTTP moduleKeep deals moving with enriched organizations and verified contact data.
SmartleadHTTP moduleFeed campaigns with validated emails and enriched personalization fields.
InstantlyHTTP moduleLoad clean, verified prospect lists straight into your sending infrastructure.
LemlistHTTP moduleLaunch campaigns on enriched contacts with emails checked before the first send.
Connect in three steps
Grab your API key
Sign up and get 1,000 free credits to test your first integration.
Add an HTTP step
Point your tool's HTTP module at a BlitzAPI endpoint and set the x-api-key header.
Map and run
Map your columns or fields into the JSON body, throttle to stay within rate limits, and run at scale.
Standard REST
No connector? No problem.
Anything that can send an HTTP request can use BlitzAPI. The integration guides cover authentication, batching, and rate-limit patterns for the most common tools, and if your stack looks different, tell us what you're building.
Integration guides
Step-by-step setups for Clay, n8n, and Make, including throttling patterns for large runs.
Talk to us
Running a stack we haven't documented? We'll help you wire it.
ONE ENGINE → EVERY TOOLLIVE
CLAY · N8N · MAKE · CRM
Where to go next
The endpoints behind these connectors.
ProductCompany Enrichment APIEnrich company profiles with structured data, fresh firmographics, websites, and AI-ready context. Clean CRM records, qualify accounts, and segment lists.ProductEmail Enrichment APIFind verified B2B emails using real signals and catch-all validation. Enrich contacts, improve deliverability, and power outbound workflows at scale.ProductWaterfall ICP APIFind the best decision makers inside any target company using a prioritized ICP cascade. Identify the right contacts for ABM, outbound, and enrichment.ProductProfile Enrichment APITurn one LinkedIn profile URL into the complete person record: typed JSON with current role, full experience, education, skills, and matching keys.
Frequently asked questions
Do I need a native connector?
No. BlitzAPI is standard REST: any tool with an HTTP module, Clay, n8n, Make, Zapier, or your own code, can call it with the x-api-key header.
How do I avoid rate-limit errors in Clay or n8n?
Every account on the lifetime offer runs at 50 requests per second, which absorbs most Clay and n8n bursts on its own. If a run is very aggressive, space the calls or batch them; per-endpoint details are listed in the API reference.
Can BlitzAPI sit inside my existing enrichment waterfall?
Yes, that is the intended design. Use BlitzAPI as a high-volume step in your Clay or n8n waterfall and cascade to other providers for whatever remains.
Does it work with my CRM?
HubSpot, Salesforce, and Pipedrive connect through their native automation tools or via n8n, Make, and Zapier, for record refreshes, decision-maker addition, and email re-verification.
