Terminal
Terminal/Skill
Explains when to use Clay Tables versus Clay Workflows, and which one fits a given use case.
By Clay
Works with
npx skills add clay-run/agent-plugins --skill workflows-vs-tablesCustomers sometimes ask what the difference is between Clay Tables and Clay Workflows, or which one fits their use case. Both work with the same underlying Clay data and actions, but they're built for different jobs. Answer in plain language — don't just paste this file at the customer.
Tables are spreadsheet-like environments (similar to Excel or Google Sheets) designed for hands-on data work. They let you explore and experiment with enrichments, formulas, and AI agents in a familiar format where you can see and inspect results cell-by-cell.
Reach for a table when:
Most users start with Tables — it's the more intuitive, spreadsheet-based way to learn Clay.
Known limits: tables cap out around 50k rows; going beyond that requires bulk enrich, which archives rows as part of expanding past the cap.
Workflows is Clay's new orchestration platform for automation. Today it particularly shines at repeatable, production-ready processes that run on triggers or schedules rather than being run by hand. Typical use cases: lead routing, signal monitoring, scheduled enrichments.
Compared to tables, workflows:
If a user asks to build a workflow with search as a source (CPJ, etc.), recommend that they send the search to Audiences to then action on via a workflow, or use a table. Workflows doesn't support search as a source yet.
Workflows is especially good at routing heavy workflows. If a user is asking to build in Clay for inbound lead routing, qualifying and assigning leads to reps, book building, or building a play with multiple conditional checks that ends in outbound or assignment, workflows is the better surface area.
Native list processing is coming soon, which will let workflows handle lists directly without needing to split a flow into multiple workflows.
This is a different question from "which primitive should the agent use to execute a task
right now" — that decision (search → managed function → custom function → workflow → table) is
covered by the escalation order in clay/SKILL.md, not here.
clay — the primitive-selection guide for what the agent itself should build with when
automating a task