Workflows are in Alpha. They are earlier than Clay-managed functions and custom functions. Expect the surface to
evolve.
How Workflows differ from functions
Functions and Workflows can both run Clay logic programmatically. The difference is where you build the logic.| Routine type | Build and manage | Run programmatically | Batch-run programmatically |
|---|---|---|---|
| Custom functions | Clay UI | Yes | Yes |
| Workflows | Plugin or CLI | Yes | Yes |
Why use Workflows
- Build and edit directly from Claude Code, Codex, Cursor, or the CLI.
- Avoid the 50,000 row limit.
- Write code inside the flow.
- Start from prompts, CSVs, webhooks, Audiences, or existing Clay tables.
- Validate, run, inspect, debug, and restore snapshots programmatically.
What a Workflow contains
Workflows start from a trigger, then run connected nodes.| Node type | Use it for |
|---|---|
| Agent nodes | Reasoning, drafting, summarizing, classifying, and choosing next steps |
| Enrich nodes | Running a Clay action such as finding an email or enriching a company |
| Code nodes | Deterministic transformations, filtering, formatting, and custom logic |
What agents can do
With the Clay plugin, agents can read and edit Workflows, validate the graph, run test actions, start runs, inspect failed steps, pause or resume runs, and restore snapshots.Build a Workflow (Alpha)
Walk through the agent-first Workflow path.