If your studio already keeps clients somewhere else, Knotflix can take them from there rather than asking you to type them twice. One endpoint, one key, and your clients — with their vendors — arrive on their own.
Getting a key
Keys live in Settings, in the Clients section. Create one and the key is shown once, at that moment, and never again — copy it into your CRM before you close the panel. If you lose it, revoke it and make another; there is nothing to recover.
There is one active key per studio. Creating a new one revokes the old one immediately, so anything still using it stops working the moment you generate a replacement.
The key identifies your studio, not a person. It keeps working when a teammate leaves.
Revoke it any time from the same panel. Nothing you have already synced is removed — revoking stops future writes, it does not undo past ones.
What your CRM sends
A single request per client, to POST /api/clients, with the key as a Bearer token in the Authorization header. Send the client’s name, and optionally an email, phone, notes, a stable id from your own system, and the vendors attached to that wedding.
Send your own client id if you have one. Knotflix matches on it first, which means a client who changes their email address in your CRM updates the record they already have here instead of becoming a second one.
Vendors arrive as a list on the client — name, your own role for each, and whatever contact details you hold. Knotflix maps your roles onto its own categories and keeps yours alongside, so nothing is lost if the two vocabularies drift.
Re-syncing a client replaces that client’s synced vendor list rather than adding to it. Send the whole list every time and duplicates are impossible; send a partial list and you will remove what you left out.
Vendors you typed into Knotflix by hand are never touched by a sync. Only the ones that came from your CRM are replaced.
What the sync will not do
Worth knowing before you wire it up, because two of these are choices rather than gaps.
It does not create projects. A synced client is a contact, ready to autofill when you create the wedding — the wedding itself is still yours to make.
It does not email anybody. Vendor addresses from a CRM are staged where nothing can send to them, precisely because they are contacts your team collected rather than addresses anyone opted into. Crediting a vendor on a gallery is the deliberate act that can send.
It does not validate your data into silence. A malformed address or a business name typed into a website field is stored as you sent it and shown to you as something to fix, rather than being quietly dropped — an empty field is a field nobody ever goes back to.
Common questions
Where do I find my API key?
Settings, in the Clients section. The key itself is shown once when you create it — after that Knotflix stores only a hash and cannot show it to you again.
Can I have two keys, one per integration?
Not today. There is one active key per studio, and creating a new one revokes the previous one immediately.
Will syncing overwrite a client I edited in Knotflix?
It updates the fields your CRM sends and leaves the rest alone. Vendors are the exception worth knowing: a sync replaces the vendors that came from your CRM, but never the ones you added by hand.
Does the sync email my vendors?
No. Addresses arriving from a CRM are stored for your reference only. A vendor is emailed when you credit them on a gallery with an address attached, which is a separate and deliberate step.
Is this on both plans?
CRM sync is part of the Studio plan, alongside the client directory and the Mac app.
Create a key in Settings
Knotflix is run by a working studio — reply to any Knotflix email and a filmmaker answers.