A contact arrives. A video gets made. It leaves through your tools.
ShowShot does not want to be one more inbox. Connect the CRM, the automation tool or the agent you already run everything through, and a personalized video shows up as a link inside the workflow you already have, not a new one to check.
Two ways in, one result.
An agent that speaks MCP can ask for a personalized video directly. Anything else can POST a contact to a webhook and get a link back. Either way, the video is composited from a recording you already made, with that person's name, company and answers written onto the sections you marked.
- For an agent
Claude, Cursor, n8n's MCP Client node, or your own. It can request a video for a named person, read the leads a watch page collected, and push a contact on to whatever you connected.
- For a CRM or webhook
POST a contact and get back a
watchUrlimmediately. Add acallbackUrland ShowShot posts to it again with what they did once they watched.
Seven tools an agent can call.
The same operations the app itself uses. Nothing runs a second implementation that could drift from what you see in the product.
create_personalized_video
Render a link for one named contact from a recording you already made.
list_recipes
See which recordings have regions marked and are ready to personalize.
list_videos
Every video the account has, with its share status and analytics.
list_leads
Read what a watch page's form has collected, owner-key checked.
get_analytics
Plays, depth, completion and the events log for a share.
list_destinations
Which CRMs and tools this account has connected, by name.
push_contact_to_destinations
Send a contact on to the tools already wired up, mapped field by field.
Where a lead comes from in the first place.
A form on a watch page, shown before play or at a moment you choose. What a viewer types is a lead the instant they submit it, not a batch job later.
Captured, not scraped
Name, email, a website, and up to twelve questions of your own. Answers are matched to the same fields Dynamic Playback and dynamic webhooks already speak.
Never the public bucket
Answers live behind the Worker, keyed by share and viewer, readable only with the owner's key. The manifest stays public; what a person typed does not.
Delivered the moment it lands
A connected destination gets the lead in the background, in your mapping, logged with its outcome. A destination that is down costs the viewer nothing.
Connect what you already run.
Thirteen CRMs, seventeen email tools, eight automation platforms, ten outbound tools, and a plain webhook for everything else.
Freshsales
Record it once. Deliver it a thousand ways.
No card, no trial countdown, no seat to justify. Record something in the next ninety seconds and see what the link does.