Contact Unlimited Enrichment Cascade

States plainly that the workflow will write enriched values onto any table you later bind, post finished records to a callback URL when one is given, and never asks for or stores an API key; then checks that the Clay command line can reach your workspace.

Decides whether this is a brand-new cascade or an addition of one provider to a cascade this Skill already built, based on whether you supply existing config files.

Asks only one question it cannot derive on its own: whether your provider agreements allow sending contact identities to third parties.

Asks which providers you hold, reads each one's real capabilities, and builds a capability map showing what each can fill and what it needs first.

Presents the full cascade plan with costs and gaps, then stops and waits for you to approve or request changes before collecting your Clay connection names.

Writes the configuration and runs two free, offline checks that catch bad code or unresolved provider names before anything is created in your workspace.

Builds the workflow as an unpublished draft in your Clay workspace, states plainly that this writes to your workspace, and stops and waits for your confirmation first.

Runs two real test records, one with nothing supplied and one with a LinkedIn URL already filled in, to prove the cascade finds data correctly and never re-looks-up a value you already gave it.

Shows the measured credit cost, states plainly that flat-rate calls are not truly free and that the workflow writes data and can post to a callback URL, then stops and waits for approval before publishing.

Delivers the reach-rate report, flags providers or fields worth removing, and explains the three ways to call the finished cascade from a table, another workflow, or an outside system.