Signed, verifiable payloads
Every POST carries X-VividProp-Signature (HMAC-SHA256). Verify it with the endpoint secret before trusting the body.
CRM and webhooks
Enquiries land in the CRM the same minute
Enquiries and QR scans delivered to the CRM as signed webhooks, with a delivery log.
Live: signed outbound webhooks (ping, enquiry.received, qr.scanned) with a delivery log in settings. No native one-click CRM connector and no film-attach yet.
An agency lives in its CRM, not in a video tool. Webhooks push the enquiry and the scan the moment they happen — signed, logged and retry-visible — so follow-up starts in the pipeline, not in an inbox.
How it is meant to work
A log, not a hope
Each delivery records its HTTP status in settings. A ping proves the URL works before a real enquiry depends on it.
No duplicate source of truth
The project record stays canonical. The CRM holds a copy of the deliverable and a link back, never a second editable project.
Specification
- Connectors
- Generic signed webhook today; native one-click CRM connector not built
- Events
- ping, enquiry.received, qr.scanned — signed payloads
- Direction
- VividProp pushes out; the project record stays canonical
- Status
- Live in settings; film-ready events follow the render pipeline
Questions
Will it sync contacts both ways?
No. Two-way contact sync is how duplicates are born. VividProp pushes films, links and events out; contacts and mandates stay where the agency keeps them.
Next
Start with what exists
The workspace, the roles, the credit ledger and the invitation flow are live. Create the account now and be first in line when this milestone opens — no card is collected.