Superpower · Capability

Lead Conversion Enrollment

Published by Synap

The source → playbook router. When a new lead (person) is created, this automation reads the lead's `source` and starts the matching conversion-journey session on it: cold-outreach/linkedin → Cold Outreach, landing-page/inbound-call → Inbound, referral → Referral, everything else → Standard. Pairs with the `lead-conversion` LoopDefinition seed (synap-backend/templates/loops/lead-conversion.loop.json), which materializes those four playbooks — install BOTH into the same CRM workspace so the playbook_run nodes resolve by name. Enrollment is idempotent per lead (runPlaybook idempotentBySubject),…

Adding this to your pod

This opens the Synap Browser and fills in the install for you. Nothing is added until you confirm it there, on your own Data Pod — this page has no way to reach it. If your pod reviews changes before they land, confirming queues the install for your approval rather than adding it straight away.

Or from the CLI

synap market install lead-conversion-enrollment

Runs against whichever pod your CLI is already connected to. Same install, same confirmation.

What it can do once it is in

An installed package proposes. You approve.

Consequential changes an agent makes through an installed package arrive as proposals you review — the same path every agent write takes on a Data Pod. Approving is a decision you make, with the change described in front of you.

Installing does not hand anything a standing permission to write to your pod.

What is in it

1capability

Read from the package's own published definition, not from an install.

Details

Kind: Capability
Identifier: lead-conversion-enrollment
Version: h-d5449f4cbfe4A content hash — it changes when the package's content does.
Tags: capability
Publisher: Synap