Clay to Instantly Workflow 2026: A Step-by-Step Guide

A great Clay list is only half the win. You have built the table, enriched every row, written personalization that actually sounds human, and now you need it inside Instantly without breaking a single variable or sending to a dead inbox. That handoff is where a lot of teams lose an afternoon. This guide walks the full clay to instantly workflow, so your enriched leads land in a live campaign clean, mapped, and ready to send.

We run this exact path for clients most weeks, so we have hit every snag worth warning you about. Clay does the building, enrichment, and personalization. Instantly does the sending, inbox rotation, and deliverability management. Your only real job is to connect the two so nothing gets lost in the middle.

What This Workflow Does

Think of it as a clean division of labor. Clay is your data and research engine. It finds accounts, enriches contacts, validates email addresses, and writes the custom lines that make a cold email feel one to one.

Instantly is your sending engine. It rotates messages across your warmed inboxes, spaces sends to look human, handles replies, and protects your domain reputation over time. The workflow simply moves finished rows from the first engine into the second without losing structure.

There is a practical reason to keep the split clean. Clay charges by enrichment credit, so you want every lookup finished and correct before a row leaves the table. Instantly charges nothing per send, so once a clean row lands there, you can sequence and follow up freely. Getting the boundary right keeps your costs down and your sending flexible.

Done right, Clay hands Instantly a list that is already verified and already personalized. Instantly never has to guess, and you never ship an email with a blank variable or a bounced address.

Before You Start: What You Need

A few things need to be in place before you connect anything. Skipping them is the most common reason a push looks fine in Clay and then falls apart in Instantly.

• A Clay table with enriched, validated emails. Every row should carry a verified email and the columns you plan to use in the sequence.
• An Instantly account with warmed inboxes. Your sending accounts should be warmed and active, not brand new domains you set up yesterday.
• A clear field map. Decide which Clay columns become which Instantly fields, first name, company name, and any custom variables, before you start clicking.
• Your connection method chosen. Native integration, HTTP API, webhook, or CSV. More on picking one below.

Get these four right and the connection itself takes minutes. Skip them and you will be debugging inside a live campaign, which is the worst place to find a problem.

Step-by-Step: Connect Clay to Instantly

Here is the full path from a finished Clay table to a live Instantly campaign. Menus may shift as both products update, so treat the labels as a guide rather than gospel.

1. Finalize and verify emails in Clay

Run your email finder and a validation step as the last actions in the table. Filter to keep only the rows marked valid or deliverable. This single filter protects your reputation more than any other step in the workflow.

2. Choose your push method

You have four options, in order of how clean they are:

• Native integration: the built-in Instantly action inside Clay. Best for most teams. It maps your columns to campaign fields and pushes rows straight into a chosen campaign.
• HTTP API: a Clay HTTP API action that sends a POST request to the Instantly API. Use this when you want more control, conditional logic, or fields the native action does not expose.
• Webhook: push rows to an Instantly webhook or automation for real time, row by row delivery as enrichment finishes.
• CSV export: the fallback. Export the table as a CSV and upload it into an Instantly campaign by hand. Slower, but it always works and needs no keys.

For most teams the native integration is the right call. Reach for the HTTP API or a webhook when you need conditional routing, custom fields, or real time delivery, and keep CSV in your back pocket for the day an API key misbehaves.

3. Connect the account (native method)

In Instantly, go to Settings, then Integrations, and generate an API v2 key (menus may shift as the product updates). Copy it once, because a new key replaces the old one. In Clay, open your connections, add a new Instantly account, name it, and paste the key. That single key powers every future push.

4. Map your fields

Map email first, since it is required. Then map first name, last name, company name, and any other standard fields. For custom variables, map each Clay column to a custom field so it travels with the lead. Keep the names tidy and consistent, your future self will thank you when you write the sequence.

If you are using the HTTP API instead, you build the same map as a JSON body, matching each Clay column to the field name Instantly expects. The logic is identical, you are just writing it out rather than clicking it.

5. Create the Instantly campaign

Build the campaign in Instantly first, or select an existing one, so you have a campaign ID to target. Attach your warmed inboxes, write the sequence, and leave placeholders where personalization will go.

6. Set sending limits and schedule

Set a daily send limit per inbox and a sending schedule that matches your prospects' business hours. Conservative limits early protect the entire account.

7. Add personalization variables

In the Instantly sequence, drop your variables where they belong, {{firstName}}, {{companyName}}, and any custom tokens like {{icebreaker}}. Each token has to match the field name you mapped from Clay. A mismatch here is exactly why a variable renders blank.

8. Launch

Push a small test batch first, 10-20 leads, and check that the variables render and the emails look right in the preview. Once the test looks clean, push the full list and activate the campaign. Clay has done its job, Instantly takes it from here.

Personalization Variables That Carry Over

Personalization is the whole reason to run Clay in front of Instantly, so this part matters. Every column you enrich in Clay can become a variable Instantly drops into the copy.

Standard fields map directly, first name to {{firstName}}, company to {{companyName}}. The interesting ones are custom variables, the researched lines that make each email feel written by a person. A column called icebreaker in Clay becomes {{icebreaker}} in Instantly, as long as the names line up.

The rule is simple, the token in your Instantly sequence must match the field name that arrives from Clay, character for character. Casing and spelling both count. Most blank variables trace back to a name that did not match, not data that was missing.

Under the hood, both the native action and the API attach these as lead level custom fields. Instantly stores them against each contact, then swaps the token for the stored value at send time. That is why the field has to exist on the lead before the sequence runs, if it is not there, the token has nothing to pull.

Deliverability Gotchas

The workflow is easy. Protecting your deliverability while you use it is the part that separates a campaign that books meetings from one that lands in spam.

The biggest risk is sending to a list you have not verified recently. The second is treating fresh inboxes like seasoned ones and blasting full volume on day one. Both damage the sender reputation that Instantly spends weeks building.

Infrastructure matters as much as the list. Your sending domains need SPF, DKIM, and DMARC set correctly, and your inboxes need real warm-up time before they carry volume. Instantly handles the warm-up and rotation, but it cannot rescue a domain that was never authenticated or a list that was never cleaned.

Keep bounce rates low, watch your reply and spam signals in Instantly, and slow down the moment either drifts the wrong way. A clean, verified push from Clay is what makes all of that easy to hold.

The Bigger Picture: One Orchestrated System

Clay and Instantly working together is a strong start. It is also just two tools. The real leverage shows up when your enrichment, sending, routing, CRM, and reporting all move as one machine instead of a stack you babysit.

That is the work we do. We wire Clay, Instantly, and 20+ other tools into a single outbound system, then run it day to day so you do not have to. You can see how the pieces fit in our managed outbound system, and what it produces in our case studies.

The difference is ownership. Every table, campaign, and connection we build stays yours. If you ever part ways with us, you keep the entire machine, warm inboxes and all.

"Two tools wired together is a workflow. Twenty wired together and owned by the client is a system that compounds." - Dimitar Petkov, founder of LeadHaste

Ready to run Clay and Instantly as one machine?

We will build your clay to instantly workflow, warm the infrastructure, and launch the first campaigns, all on a free pilot with no contract. If we miss the targets we set together, your billing stays paused until we hit them.

Book your free pilot →