Resources · Zapier integration

Clay Zapier integrationAutomate Clay with Zapier.

The Clay Zapier integration offers 0 triggers, 2 actions and 3 searches. Clay does not start Zaps, it receives them. A lead, a signup or a status change from another tool becomes a new row in a Clay table, or fixes a row that is already there.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Clay Zapier integration is for

Clay looks like a spreadsheet, but every table sits on top of an automation platform built for marketing, sales and recruiting teams. Through Zapier, Clay becomes a destination: other apps drop rows into it or change values in it, with no CSV exports and no manual imports in between.

Three concrete outcomes cover most setups. Every new CRM contact lands as a row through Create Record in Table. When a deal moves stage, Find Row in Table locates the matching row and Update Record in Table rewrites it. And Find User looks up a workspace member by email or name, so each row gets assigned to the right rep. The first of those three runs on the free plan; the other two chain a search and an action, so they need a paid one.

Clay is not a premium app either, so none of this waits on a paid plan for the app itself. Now the limits. Clay has no visible trigger in Zapier, so a new row in Clay cannot start a Zap; data flows from other tools into Clay, not the other way. No action deletes a row either, and nothing in this integration removes one. And every search adds a step, which turns the Zap multi-step and puts it on a paid plan.

Clay is on Make too. The Clay Make integration page covers what it offers there, handy for comparing before you choose a tool.

Vocabulary

Zapier vocabulary in one minute

Seven words worth knowing before you open the editor.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. With Clay it always comes from another app: a form, a CRM, a signup tool.
Action
What the Zap does after it starts. Here, the step that creates or edits a row in a Clay table.
Task
The unit Zapier bills: one successful action. Your plan quota counts tasks, not how many Zaps ran.
Search step
A step that finds something that already exists, a row or a user, and passes it to the steps after it.
Filter
A step that lets the Zap through only when the incoming data meets your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. One filter or one search is enough, and the Zap then needs a paid plan.
Cost

What it really costs

Clay is not a paid-only app, so the simplest Zap runs on the free plan.

  • Free plan100 tasks a month
  • Steps on the free plan2 (one trigger, one action)
  • Trigger cost0 tasks
  • Paid-only appNo

The trigger is free. Each successful action counts as one task, and a failed action is not counted at all. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps each: one trigger, one action. A CRM contact going straight into Create Record in Table fits. Add a filter, a search such as Find Row in Table, or a second action, and the Zap becomes multi-step, which requires a paid plan.

Connect

Connect your Clay account

  1. 01

    Open Apps

    In your Zapier account, open the Apps page and click + Add connection. A search dialog shows up so you can find the app you want to link by name and add it.

  2. 02

    Pick Clay

    Type Clay in the dialog, select the app and confirm with Add connection. A new tab opens on the Clay sign-in page, which is where the link is actually made.

  3. 03

    Authorize Zapier

    Sign in to Clay in that tab and grant Zapier access. From then on the connection is reused by every Clay step in your Zaps, so you never have to set it up twice.

First Zap

Your first Clay Zap

GoalWhen a new contact with a company email lands in the CRM, add a row to the Clay leads table.

  1. 01

    Set the trigger

    Create a Zap, pick your CRM and its new-contact event. Test it: Zapier brings back the three most recent contacts, so pick a real one to map against.

  2. 02

    Add the filter

    Click the plus icon, choose Filter and fill the three boxes: the email field, a text rule, and the value to exclude. A text rule only works on text.

  3. 03

    Add the Clay action

    Choose Clay, then Create Record in Table. Select the leads table and map each column to a field coming from the CRM contact.

  4. 04

    Test the action

    Run the step once and open your table in Clay. The new row should be there, with the right values sitting in the right columns.

  5. 05

    Publish

    Click Publish. Because of the filter this Zap is multi-step, so it needs a paid plan. Our Zapier training walks through builds like this one.

Actions

Clay actions

Clay gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Record in Table

Action

In Zapier“Creates a new record in a table.”

This action adds a fresh row to the Clay table you pick, filled with whatever the earlier steps brought in. It is the most direct way into Clay from any other tool.

When to use it
every webinar registrant should join your prospecting table without a CSV export in the middle.
Watch out
to fill a select field from a text value, the search Find Select Option ID for Table Field turns that text into the option ID.
2

Update Record in Table

Action

In Zapier“Updates a record in a table.”

It changes a row that already exists in a Clay table instead of adding a new one.

When to use it
a deal moves to the next stage in your CRM and the account row in Clay should show the new status.
Watch out
you first need to know which row to change, so Find Row in Table usually goes right before it, which makes the Zap multi-step.
Searches

Clay searches

3 search steps look for data that already exists in Clay, so a later step can use it.

A search finds what already exists before the Zap acts on it. Three settings decide what happens when the result is not what you expected.

1

Find Row in Table

Search

In Zapier“Find a row in a table.”

It scans a Clay table and returns the row matching your value, so the next step knows exactly where to act.

When to use it
right before Update Record in Table, to target an account row from its email or domain.
Watch out
when several rows match, the first one wins by default, so make sure the value you search on is truly unique in that table.
2

Find Select Option ID for Table Field

Search

In Zapier“Finds a Select Option ID by its text value”

Some Clay columns are dropdowns. This search starts from the text of an option and gives you back its ID, which is the value actions need to fill that column.

When to use it
your CRM sends a status spelled out in words and the matching Clay column is a pick list.
Watch out
the text has to match an option that already exists in the column.
3

Find User

Search

In Zapier“Finds a user in a Workspace by email, name, or id”

To locate a member of your Clay workspace, this search accepts an email, a name or an ID and hands the matching user to the following steps.

When to use it
assigning each new row to the rep whose email arrives along with the lead.
Watch out
the result feeds later steps only; on the free plan, a search plus an action is already one step too many.

The three settings every search exposes

  1. Successful if no search results are found?
    By default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Clay exposes no such variant in Zapier, so it does not appear here.
  3. If multiple search results are found?
    Three ways out when several items match: take the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When it breaks

Zapier documents no Clay-specific limit. Failures follow Zapier's general rules.

Four situations, all of them general Zapier rules, explain most Zaps that go off the rails. For more, the Zapier troubleshooting guide covers the usual causes.

  • History never comes across

    A Zap only handles what arrives after you publish it. Contacts already sitting in your CRM will not reach Clay on their own; that backfill is a separate job.

  • A search pushes you off the free plan

    Find Row in Table, Find User or the option search each add a step. The Zap turns multi-step the moment one is in, and the free plan no longer runs it.

  • A flood gets held back

    A trigger that suddenly returns a huge batch, after a bulk import into your CRM, can be held back by Zapier's flood protection.

  • The row nobody found

    By default, if Find Row in Table comes back empty, the Zap stops and the update never happens. The success-with-no-results setting changes that.
Need help

Need help automating Clay with Zapier?

A person reads every message.

FAQ

Frequently asked questions

01Is the Clay Zapier integration free?
Yes, for simple Zaps. Clay is not reserved for paid plans, and Zapier's free plan gives you 100 tasks a month with unlimited two-step Zaps: one trigger and one action. A CRM contact that creates a row in a Clay table fits inside that. As soon as you add a search, a filter or a second action, though, the Zap becomes multi-step and needs a paid subscription. Updating an existing row usually means a search first, so it lands on a paid plan.
02How many tasks does a Zap into Clay use?
One task per successful action, nothing for the trigger. When a new contact hits your CRM, that event is free. Creating the row in Clay counts as one task if it goes through, and a failed action is not billed. A Zap that creates a row and then sends a notification uses two tasks per run. On the free plan you have 100 tasks a month to share across all your Zaps.
03Does Clay react in real time through Zapier?
Clay has no visible trigger, so it depends on the app that starts the Zap. If its trigger is instant, the Zap runs the moment the event happens, whatever your plan. If it is a polling trigger, Zapier checks on a timer: 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. The write into Clay then happens straight away, as the Zap reaches the action.
04What do you need to connect Clay to Zapier?
A Clay account and a Zapier account. You add the connection from the Apps page in Zapier with + Add connection, sign in to Clay in the tab that opens, then grant access. Check your permissions above all: on any table you do not own, you need read or write access. Clay is not a premium app, so the connection works on the free plan too. After that, the same connection serves every Clay step. Set it up once and reuse it.
05How do you fill a Clay select field from a text value?
With a search placed before the action. Find Select Option ID for Table Field takes the text of an option, say Closed Won coming from your CRM, and returns the ID of that option in the Clay field. You then map that ID into Create Record in Table or Update Record in Table. The text has to match an option that already exists in the field. Keep in mind that the search is a step of its own, so the Zap becomes multi-step and needs a paid plan.
06What if the operation you need is not there?
Clay offers two actions and three searches in Zapier, and no visible trigger. So you cannot start a Zap when a row changes in Clay, and you cannot delete a row from Zapier. If that is what you need, look at what the Clay integration on Make offers, since it does not necessarily expose the same operations. Otherwise design the flow so Clay stays the destination and other apps start the Zap.
07Zapier, Make or n8n for Clay?
No tool wins by default; it depends on your criteria. First, the Clay operations each one exposes, compared one by one, especially on the trigger side. Second, how each tool counts what you consume, bearing in mind that on Zapier a search makes the Zap multi-step. Third, where the automation runs and who maintains it. Run those questions against your real use case before you settle on one. The right answer varies from team to team.
Same platform

Other docs you might need on this stack.

Browse all integrations