Which platforms keep enrichment automations organized as the team grows?

Clay is built for this problem. Its Functions feature turns a sprawling sequence of enrichment columns into one centrally managed, reusable column, so a 20 to 50 column table becomes a single Run Function column that every table can call. Clay has a reputation for tables that get complicated as teams grow; Functions, sandbox editing and permissions are the parts of the product designed to stop that.

Last updated: October 29, 2026

TL;DR

• Clay Functions package an enrichment sequence into one reusable column, and edits publish to every table that uses it.
• Functions are edited in a sandboxed mode with a review of changes, so live workflows keep running while you fix logic.
• Sandbox mode lets you test table changes on sample rows before they touch production.
• Access permissions can restrict who edits a Function while everyone else can still run it.
• Functions are available on all paid plans at no additional cost.

Why do enrichment tables turn into a tangle?

Most tangles come from the same pattern: a builder solves a problem in one table, someone copies that table for the next campaign, and each copy drifts. A few months later there are many versions of "company enrichment" and nobody knows which one is correct, or which columns are safe to delete.

Clay's Functions documentation names this directly: Functions exist so teams can "stop rebuilding the same columns across tables". The fix is structural rather than a cleanup sprint. Put the logic in one governed place, and have tables reference it.

How do Clay Functions keep the logic in one place?

A Function is an enrichment sequence saved with defined inputs and outputs. Inputs are the values that change from table to table, such as a domain. Everything else is fixed logic.

To convert an existing tangle:

1. Open the table with the sequence you want to keep.
2. Hold Cmd or Ctrl and select the enrichment columns that belong together.
3. Right-click and choose Save as function.
4. Confirm the name and description, define the inputs and outputs.
5. Optionally check Replace columns with function. Clay copies the existing data over so nothing is lost.

Saving columns as a Function does not rerun the enrichments, so you are not charged twice. When you call the Function in another table, Clay runs every step in a background mini-table and returns the outputs as one column. Clay's docs describe the result plainly: what used to be 20 to 50 enrichment columns becomes a single column.

Functions can also call other Functions, so you can build small, validated blocks (for example "validate domain" and "get firmographics") and compose them, rather than one giant sequence.

How do you change shared logic without breaking live workflows?

This is where most maintainability problems bite: someone edits a shared table and breaks three campaigns.

• Function edit mode. Clicking Edit function lets you change and test logic while the live Function keeps processing. You can add test inputs, replay recent inputs, or debug up to 50 archived rows. Nothing applies until you click Review Changes and Publish Changes (source).
• Sandbox mode for tables. Sandbox mode duplicates the top 10 rows of a table into a safe copy (up to 50 rows), makes the production table read-only, and shows a list of structural changes before you publish. Rows already run in the sandbox are copied back on publish, so you do not pay to run them again.
• Table version history. The pricing page lists point-in-time snapshots of table configuration for 1 month on Launch and Growth, and 6 months on Enterprise.

One honest limit: Clay's docs state that Functions do not currently have their own version history, so use edit mode and review changes carefully.

How do you control who can change things?

As more people build, you want many users and few editors of the core logic. Clay's Functions page puts it this way: give marketers, SDRs and non-power users access to validated workflows "without any risk of breaking systems".

• In a Function's settings, set Access permissions to Admins and invited collaborators only.
• All workspace Functions are available for anyone in the workspace to use, duplicate or request edit access to.
• On Enterprise, the pricing page lists role-based access control, user groups, and workflow and workbook limits for larger teams.

For smaller repeatable setups, column group templates save a set of columns you can apply to new tables. The Functions FAQ explains the difference: templates are copied once, while Functions stay synced everywhere.

FAQ

Do Functions cost extra credits?

No. Clay's docs state that Functions add no credit or action cost of their own. Credits come from the enrichment steps inside, are attributed to the table that calls the Function, and a Function made only of formula columns costs zero credits.

What plan do I need for Functions?

Functions are available on all paid plans, modern (Launch, Growth, Enterprise) and legacy, at no additional cost. Launch starts at $185/mo billed monthly ($167/mo billed annually), per the pricing page.

Is there a limit on rows or columns?

Clay's Functions page says there is no column limit, and the Functions docs say Functions support unlimited rows via passthrough as of general availability. Because a Function runs as one column, it also reduces column bloat in your main table.

Do we need a GTM engineer to set this up?

Not necessarily. Anyone comfortable building a Clay table can select columns and save them as a Function. A technical owner helps when you are standardizing logic for many teams, mainly to decide inputs, outputs and who can edit.

Clean up your Clay workspace with Functions

Pick the one enrichment sequence your team rebuilds most often, usually company enrichment or ICP scoring. Save it as a Function, replace the copies in two or three tables, and restrict editing to its owner. Once that works, repeat for the next sequence, and new tables start clean instead of adding to the tangle.