Skip to main content
Agent guide: CLI and SDK instructions →

1. Have your context ready

Have an authorized Clay table, its configuration and sample export, expected outputs, and the existing approval boundaries.

2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:
Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

3. Review the result

The pilot matches the intended table behavior and its acceptance rules. Differences are explained before cutover; a similar-looking enrichment result is not proof of equivalence. Ask your agent:
Approve a larger job, recurring work, or external changes only after reviewing that decision.

Check your understanding

Does reproducing column names establish equivalent workflow behavior?
No. Compare the actual inputs, transformations, acceptance rules, and results under the same test cases.