Integration

Connect Kit to Clay

When New Form Subscriber fires in Kit, your agent runs Create Record in Table in Clay. Describe the whole flow and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want Kit and Clay to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Kit holds your subscribers, tags and purchases; Clay is where you research people and companies and keep working tables. Connecting them means a new Kit subscriber or buyer can land in a Clay table with their tags and custom fields already filled in, or kick off a Clay search on their company, and tags can be written back to Kit once the record is handled.

Example flows

What Kit can start in Clay

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Kit and Clay

Triggers and actions 7 triggers · 11 actions

Each app on its own

Reviews

What our customers say

More from Kit

More into Clay

Questions

Kit and Clay, answered

Can a change in Clay start something in Kit?

No, Clay has no triggers on this connection, so every scenario begins with a Kit event such as a new subscriber, a new purchase or a tag being added. From there the agent can create records in Clay, start a people or company search, and write tags back in Kit.

Will the Clay table need columns set up in advance?

Create Record in Table posts to a table's webhook URL, and each key you send becomes a column, so you can pass the subscriber's email, first name, tags or purchase details. Tell the agent which Kit fields you want sent and it will test each scenario with real subscriber data.

What can start an automation from Kit?

Any of Kit's 7 triggers in the catalog, including New Form Subscriber, New Purchase, New Subscriber and New Unsubscribe. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Clay when something happens in Kit?

Any of Clay's 4 actions, including Create Record in Table, Search People or Companies, Get my user and Get Search Results Page. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Clay to Kit?

Clay has no triggers in the catalog today, so automations start in Kit. If you need the other direction, ask: your agent reads Clay's API documentation and adds it.

Do I have to build a connector for Kit or Clay?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

Can my AI client use Kit and Clay without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.