Skip to main content
Functions and Workflows both live under Routines. Both can run Clay logic programmatically and support batch execution. Choose based on where you want to build the logic.
Use caseChoose
You want Clay-provided enrichment or researchClay-managed functions
You already built reusable logic in the Clay UICustom functions
You want to create or edit the logic from an agent or terminalWorkflows (Alpha)
You want an agent to inspect and debug the run step-by-stepWorkflows (Alpha)
You want to avoid the 50,000 row limitWorkflows (Alpha)

​
Use functions when

Use functions for:
  • Existing Clay enrichment waterfalls.
  • Common jobs handled by Clay-managed functions.
  • Team-specific functions that are already trusted.
  • Backend jobs and agents that just need to call the logic.
  • Batch execution where the function already does what you need.

​
Use Workflows when

Use Workflows when you want to build and edit outside the Clay UI. Workflows are in Alpha. Use them for:
  • Agent-built flows in Claude Code, Codex, or Cursor.
  • CLI-first iteration, validation, testing, and debugging.
  • Multi-step flows that benefit from run inspection and snapshots.
  • Flows that need code inside the process.
  • Large runs where you want to avoid the 50,000 row limit.
Workflows are in Alpha. For common enrichment and existing reusable logic, start with Clay-managed functions or custom functions.