Resources · Make integration

Clay Make integrationAutomate Clay with Make.

Need fresh rows in a Clay table without copying them by hand? The Clay Make integration gives you 1 action module that writes a record into a Clay table. This page shows growth and sales teams how to wire the webhook and build a first working scenario.

Try the Clay integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clay Make integration do for you?

The Clay Make integration sends data from any app Make can read straight into a table of your Clay workbook. In Make you build a scenario, the automation made of modules, and the Clay module is its last brick: it takes each item that reaches it and adds it as a new record in Clay.

A sales list that fills itself. A form tool, a CRM or a spreadsheet catches a new prospect, and Create a record in table drops that prospect into the Clay table your team works from. Nobody exports a CSV again.

Event signups, centralized. A booking or webinar app records a registration, Make passes the name and email along, and Clay receives one row per person so marketing can work the list from a single place.

Handoffs between tools. When a deal changes stage in another system, the same module can log the account in Clay for a research pass before the next call.

What the app does not do: Clay has no trigger in Make, so nothing in Clay can start a scenario, and there is no module to read, update or delete records. The flow always goes one way, toward Clay. Another point to know before starting: the Clay app in Make requires a paid Clay account.

If you are still weighing platforms, the n8n vs Make comparison lays out the differences, and the Make review covers the editor in depth. Teams that would rather hand the setup over can bring in the Make agency team.

Connect

How do you link Clay to Make?

  1. 01

    Create a webhook source in Clay

    Log in to Clay, click + New and create a Workbook. In the left sidebar, open Add a source and add webhooks, either as a new source or an existing one. Clay then shows a URL: copy it and keep it somewhere safe.

  2. 02

    Add a token if you want one

    This part is optional. Click +Add auth token, then Create, and Clay generates an authentication token for that webhook. Copy the value right away: Make will ask for it in the next step.

  3. 03

    Paste both values into Make

    In your Make scenario, add the Create a record in table module. Paste the URL into Webhook URL, the token into Authentication Token if you made one, list your columns and values in Data, then click Save.

First scenario

Your first scenario with Clay

GoalWhen a new lead shows up in another app, Make adds it as a record in your Clay table.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big +. This first module is the one that starts everything, so pick the app where your leads land.

  2. 02

    Set the starting module

    Search that app by name, choose its module and click Create a connection to link the account. Fill its fields; once the connection exists, Make lists the sheets or objects it can read.

  3. 03

    Add the Clay module

    Click the + on the right of the first module, search Clay and pick Create a record in table. Paste your webhook URL, then map each column in Data to a value coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles, the items passed between modules, that each step received. Open Clay and check that the new row sits in the right columns.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule; a new scenario runs every 15 minutes by default. Switch the scenario on, and each new lead now reaches Clay without anyone touching it.

Modules

The Clay module in Make

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

Clay1

Create a record in table

Action

In Make“Creates a webhook record in a table.”

You get a fresh row in your Clay table for every bundle that reaches this module, sent through the webhook URL copied from your workbook. It is the only Clay module in Make, so every flow that feeds Clay ends here.

When to use it
a new contact, company or signup appears in another tool and you want it in Clay without retyping it.
Watch out
a column name used twice in Data keeps only the latest value, so check your mapping before you switch the scenario on.
Need help

Need help automating Clay with Make?

A person reads every message.

FAQ

Clay and Make: common questions

01Is the Clay Make integration free?
On the Make side, yes. Clay is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans lower the interval to 1 minute and lift the limit on active scenarios. On the Clay side it is a different story: the documentation states that the Clay app in Make needs a paid Clay account, so check your Clay subscription before building anything.
02What is needed to connect Clay to Make?
Three things. First, a paid Clay account, which the Make documentation lists as a prerequisite. Second, a workbook in Clay with a webhook source, from which you copy the webhook URL. Third, if you want to lock the webhook, an authentication token created with the Add auth token option. There is no login window to approve: you paste the URL, and the token when you use one, straight into the fields of the Create a record in table module, then click Save.
03Does Clay trigger Make scenarios in real time?
No, because Clay has no trigger module in Make at all. Clay only receives data; it never starts a scenario. To get things moving, open the scenario on another app's trigger, for example the form or CRM where leads first appear, or rely on the schedule set on the first module, which runs every 15 minutes by default. Whether that first step is scheduled or instant depends on the app you choose to start with, not on Clay.
04What if a Clay module is missing in Make?
Make offers a single Clay module, Create a record in table, and no Make an API Call module for this app, so reading, updating or deleting Clay records is not possible from Make. The practical answer is to keep Clay as the destination and do the reading or sorting in another app of the scenario before the data reaches Clay. If your need goes further than that, the Hackceleration team can look at your case and suggest a different route.
05Should you use Make or n8n for Clay?
It depends on where the rest of your automations already live. In Make, Clay is a single action module that sends records through a webhook, which covers the classic case of feeding a table from other tools. The same app often has a node in n8n as well, so check what it offers for Clay before choosing. Pick the platform your team already knows and where your other data sources are connected, rather than switching tools for one module.
Same platform

Other docs you might need on this stack.

Browse all integrations