Move a Clay workflow
Turn a Clay table’s rules into Deepline code. Compare the results with the original table before switching.
The original Clay table is the comparison source. Review any differences before switching.
Keep your workflow when you move it.
Read the table
Capture the columns, formulas, and actions in Clay.
Map the steps
Find the matching tools and note any gaps.
Write the code
Rebuild the workflow with the same rules.
Compare the results
Run sample rows and check them against the Clay output.
Read the full instructions
# Clay → Deepline Migration
## Quick Start
```bash
npm install -g deepline
deepline -h
```
This is a recipe shortcut. It pre-selects the clay-to-deepline recipe but the **deepline-gtm governs the entire session**.
## Execution order
1. **Invoke `deepline-gtm`** using the Skill tool.
2. **Follow the meta-skill's full routing instructions** - analyze the user's complete prompt and load every sub-doc the meta-skill tells you to. Do not skip docs just because a recipe is pre-selected.
3. **Follow the meta-skill's routing gate for this recipe.** Read the clay-to-deepline recipe at `../deepline-gtm/recipes/clay-to-deepline.md` (relative to this file) only when that gate routes you to it. Conditional access and safety checks still apply.
The recipe only covers one part of the task. The meta-skill handles everything else the user asked for.