AI Use Cases for Business
Submit
SponsoredSynergy45Stronger looking, Thicker looking Hair SerumVisit Synergy45

Your business here

Documented setupGrok Bot + Clay

Grok Bot + Clay: build and check GTM workflows through the Clay CLI

Install Clay's agent plugin on your Bot's cloud computer so a Grok Bot can build Clay workflows from a chat or voice description, then read the results and suggest fixes while Clay runs the rows.

AgenciesStartups
Get the starter prompt

How does an AI agent stack for outbound prospecting with Clay work?

In this AI agent workflow stack for outbound prospecting, a Grok Bot uses Clay's agent plugin and CLI to build Clay workflows from a chat or voice description, then reads the results and suggests fixes while Clay runs the rows. Only Admin and Editor users can sign in, CLI runs use Clay credits, and campaigns stay in draft.

Setup

  1. Check your Clay role first: only Admin and Editor users can sign in to the Clay CLI. Clay's agent plugin, which includes the CLI, is in open beta on Mac and Linux.
  2. Ask your Bot to set up the Clay plugin by following the steps in github.com/clay-run/agent-plugins, as Clay's quickstart suggests. The plugin's setup puts the clay CLI on the Bot's computer and starts the sign-in.
  3. Sign in with clay login --device, since you can't use a browser on the Bot's computer: open the printed link on your phone or laptop, approve the sign-in and pick the workspace.
  4. Have the Bot run clay whoami, which Clay calls the canonical check that sign-in worked.
  5. Give each Bot one job (list building, copy, deliverability) and tell it to build new things as Clay Workflows and keep campaigns in draft until you say go live.

Starter prompt

Context / Role

Grok Bot with Clay (documented setup). Do the setup steps above first.

The copy-paste prompt
Starter promptWritten by our editors from the source
You build and maintain our outbound workflows in Clay using the Clay CLI.

Rules:
- Build new things as Clay Workflows, not tables.
- ICP: [definition]. Never target anyone outside it.
- Reuse our existing functions for [scoring / routing] instead of writing new logic.
- Only send to emails that pass validation, and keep every campaign in draft until I say go live.

First task: review our existing Clay tables and write a preference guide (which data provider for which job, how we build our email waterfall) and save it to [location]. Then wait for my first campaign brief.
Variables to customize
  • [definition]
  • [scoring / routing]
  • [location]
Expected output / next step

A preference guide saved to [location] (which data provider for which job, how you build your email waterfall), then a Bot that waits for your first campaign brief and keeps every campaign in draft until you say go live.

Stack next step: Grok Bot + Claude Code and Codex CLIs: route each task to a model.

Business fit

How this stack helps specific businesses:

  • Outbound and lead-gen agencies: run one Bot per client that builds lists and checks campaigns against their reply targets.

    Agencies

  • Founder-led sales: describe the list you need and let the Bot build the Clay workflow while you're away from your desk.

    Startups

Watch-outs

  • Clay's quickstart lists Claude Code, Codex and Cursor as plugin hosts; the Grok Bot setup is shown in Clay's blog, not its docs. Test before relying on it.
  • A CLI session has edit rights to the workspace and its credentials sit in a config file on the Bot's computer; Clay says to treat that file as a live credential.
  • CLI runs use the same Clay credits and actions as work done in the app.
  • Whatever you type and whatever the CLI returns is processed by the agent's provider, per Clay's security page.

Workflows on this page at a glance

The starter prompt, then the use cases and prompts linked below. Input data is what each prompt asks you to fill in; the last column is what it produces, or the time or money result the source states.

Summary of the workflows on this stack page: tool, input data and expected output
Workflow / use casePrimary AI role / tool slotInput dataExpected business output / time saved
Starter prompt for this stackGrok Bot + Clay[definition]; [scoring / routing]; [location]Expected outputA preference guide saved to [location] (which data provider for which job, how you build your email waterfall), then a Bot that waits for your first campaign brief and keeps every campaign in draft until you say go live.
An Outbound Agency Has Grok Bot Build Clay Workflows and Review Every Campaign DailyGrok Bot, Clay, Grok Build CLI +3 (Approve-to-send)[client]; [the hand-written templates and the one slot you may vary]; [ICP definition and filters]; [positive replies / booked meetings]; [number]; [channel]Time savedNot published: the source gives no time or money figure
A Revenue Team That Had Never Shipped Code Built Its Own Call Review Tools in Claude CodeClaude Code, n8n, Clay +4 (Assisted)None: the prompt runs as writtenMoney$200K+ in pipeline after one fix
Choose which industry to sell to with a 15-minute AI research passChatGPT, Claude, Clay (Assisted)[OFFER]; [PRICE]; [CANDIDATE_MARKETS]; [CONSTRAINTS]Time15 minutes; sales result not reported

Related

Related stacks and workflows