Run a Clay table workflow in Deepline

1. Have your context ready

Have the smallest useful Clay export, expected fields, formulas and conditions, and examples of acceptable output.

2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

/deepline-gtm Turn this Clay table sample into a Deepline workflow. Document the current behavior first, including formulas, provider selection, suppression, and write boundaries. Identify missing information rather than replacing unknown behavior with a generic shortcut. Propose one custom Play and a ten-record pilot with external writes disabled. Compare source identity, output values, exceptions, and usage before discussing migration of the full table.

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 comparison accounts for each pilot source record and all material rules. An undocumented Clay branch remains unresolved until it is inspected. Ask your agent:

/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.

Approve a larger job, recurring work, or external changes only after reviewing that decision.

Check your understanding

Can a new provider route be treated as equivalent solely because it returns the same field name?

Show the answer

No. Compare meaning, identity, validation, and failure behavior. A shared label does not establish equivalent evidence.

​1. Have your context ready

​2. Ask your agent

​3. Review the result

​Check your understanding

​Related guides

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

Related guides