Define the graph. Claude
preserves the run evidence.
A recipe is a versioned chain of supported capabilities. Validate a draft, publish the reviewed version as a human admin, explicitly approve provider usage, and inspect durable attempts through terminal state.
Recipes · typed, reviewed workflows
Source
Verify
Transform
Current Coil recipe templates.
Availability depends on the installed curated template, its reviewed publication, and configured provider connections.
Lead List Import
Prospect Search
Sales Navigator Search
Product Hunt Top Commenters
Provider evidence without invented prices.
Each external step names its provider. Exact vendor pricing is not hard-coded on this page; review the provider account and the run's recorded cost source before approving or interpreting spend.
Recipe questions, asked early.
The ones you'd ask in a 15-minute call. Answered here so the call can go somewhere more useful.
Do I have to "build" a recipe?
Start from a curated template or create a draft definition in the dashboard, API, or JSON CLI. Validate the exact capabilities and inputs before a human admin publishes it.
What if a step fails halfway through?
The durable run records step attempts, failure state, and server-provided next actions. Retry, resume, cancellation, or reconciliation is available only when the run contract exposes that action.
Can I edit a saved recipe later?
Yes. Edit the draft definition, validate it again, and publish the reviewed version as a human organization admin. Published versions remain immutable run evidence.
Where do provider keys live?
Provider credentials are stored through the encrypted organization integration surface. Secret-like recipe inputs are rejected; runs persist credential references rather than plaintext provider secrets.
Publish the graph you reviewed.
Start from a curated template or draft a typed definition, validate it, publish as an admin, and inspect the durable run.
Recipes