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

Start free →See real recipes ↓

Typed capabilities · immutable publication · durable run status

Illustrative reviewed recipe: bounded prospect source → optional email verification → schema-constrained transform.

STEP 01

Source

apify.prospect-search

example source step

STEP 02

Verify

millionverifier.verify-email

example optional step

STEP 03

Transform

openrouter.llm-transform

example typed step

Apifyprovider pricing

MillionVerifierprovider pricing

OpenRouterprovider pricing

illustrativeno run state is implied

explicitprovider-spend approval

durableattempt and effect evidence

example workflow

Current Coil recipe templates.

Availability depends on the installed curated template, its reviewed publication, and configured provider connections.

coil.lead-import

Lead List Import

validate→coil.lead-import→inspect

Import a CSV or structured lead list with deterministic identity matching and run-scoped outcomes.

coil.person-find-at-company

Find People at a Company

validate→person.find_at_company→inspect

Find people by current job title at a LinkedIn company page with a bounded result count and explicit spend cap.

coil.prospect-search

Prospect Search

validate→apify.prospect-search→inspect

Find prospects with Atomus Leads Finder from job title, location, one exact contiguous company-size range, and industry filters.

coil.sales-nav-search

Sales Navigator Search

validate→source.sales_navigator→inspect

Scrape a LinkedIn Sales Navigator search URL and import the result as Coil leads.

coil.product-hunt-top-commenters

Product Hunt Top Commenters

validate→apify.product-hunt-comments→coil.rank-product-hunt-commenters→inspect

Scrape recent Product Hunt comments and rank the most active 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.

Source · Apifyprovider pricing

Verify · MillionVerifierprovider pricing

Transform · OpenRouterprovider pricing

Recorded run costinspect cost source

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

Start free →

Explicit provider approval · Free during beta