- Home
- Resources
- Integrations
- PlayFilm
PlayFilm Zapier integrationAutomate PlayFilm with Zapier.
The PlayFilm Zapier integration comes down to 1 trigger and 1 action: catch each form filled in at the end of an interactive video, then confirm it. Here is what both do, what they cost you, and where a first Zap usually goes wrong.
Verified Trustpilot reviews · AI, automation & growth agency
What the PlayFilm Zapier integration is for
PlayFilm lets marketers build interactive video tests that end on a contact form, so viewers turn into qualified leads. The Zapier integration takes each of those forms the moment it is sent and passes it to your other tools, then lets you confirm the submission back in PlayFilm.
Three things people build with it. A lead in the CRM without copy-paste: New Form Submission starts the Zap and the next step creates the contact in your sales tool. A sales alert while the lead is warm: the same trigger posts the new contact to your team chat, and since the trigger is instant there is no waiting for a scheduled check. A confirmed record: Confirm Contact Submission tells PlayFilm that a given submission was received correctly, using the ID the trigger handed over.
What Zapier does not do here is just as clear. One trigger, one action, nothing else: no way to create a video, change a project, read statistics or look up an older contact. The trigger also watches a single project, so several campaigns mean several Zaps. And forms sent before the Zap was switched on stay where they are.
Still choosing a tool? The Make vs Zapier and n8n vs Zapier comparisons are a click away.
Zapier vocabulary in one minute
Eight words from the editor, in plain English. Each comes back further down.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. With the Zap on, Zapier waits for it. Here, someone filling in a PlayFilm form.
- Action
- What the Zap does once started: the step that writes, sends or confirms something for you, in PlayFilm or elsewhere.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's count is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. PlayFilm does not use one.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for a check. PlayFilm's trigger is one.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a PlayFilm Zap really costs
PlayFilm is not a premium app, so it runs on the free plan. You pay in tasks, and only successful actions count.
- TriggerFree, never counted
- Action that works1 task each
- Action that failsNot counted
- Free plan100 tasks a month, two-step Zaps only
New Form Submission never costs a task, however many forms come in. Each Confirm Contact Submission that works costs one, and one that fails costs nothing. Watch the free plan's shape: two steps, one trigger and one action. Trigger plus confirmation fits. Trigger, confirmation and a CRM step is a multi-step Zap, so it needs a paid plan and costs two tasks per lead. Since the trigger is instant, the polling grid below does not apply to it.
Connect PlayFilm to Zapier in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A connection is your PlayFilm account linked once, then reused by every step that needs it.
- 02
Pick PlayFilm
Search for PlayFilm in the dialog that appears, select it, and click Add connection. You need an existing PlayFilm account, with your projects in it, before going further.
- 03
Sign in and grant access
Log in to PlayFilm in the tab that opens and allow Zapier in. If the projects you want to watch belong to a colleague, make sure your account can read them.
Your first PlayFilm Zap
GoalSend every lead from a PlayFilm video to your CRM and confirm the submission in PlayFilm.
- 01
Start on New Form Submission
Build: choose PlayFilm as the app that starts the Zap, New Form Submission as the event, then your connection and the Project whose video should feed the Zap.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent submissions of that project, so you map the next steps on a real lead rather than an empty sample.
- 03
Confirm the submission
Add Confirm Contact Submission as the action and drop the submission's ID from the trigger into the Submission Id field.
- 04
Add the CRM step and test
Add your CRM as a second action and map the contact details. This makes the Zap multi-step, so it needs a paid plan. Test each step once and read what came back.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new lead costs you two tasks: the confirmation and the CRM contact.
The PlayFilm trigger
1 event starts a Zap when something happens in PlayFilm, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Form Submission
Instant triggerIn Zapier“Triggers when a form from a specific project has been submitted.”
Starts your Zap whenever a viewer sends the form inside one of your PlayFilm projects. The lead's details travel to the next steps, ready to land in a CRM, a spreadsheet or a sales channel.
The PlayFilm action
PlayFilm gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Confirm Contact Submission
ActionIn Zapier“Calls to an endpoint to confirm the correct lead submission.”
Sends PlayFilm a confirmation that a given lead submission is the right one and reached you correctly. It needs the Submission Id, which is required.
When a PlayFilm Zap breaks
Zapier ties no help article to PlayFilm. What goes wrong here is what goes wrong on any instant app, applied to video leads.
Four cases to keep in mind before you publish. If one bites, the Zapier troubleshooting page is the next stop.
Older leads never arrive
A Zap only reacts to forms sent after it is switched on. Leads collected before stay in PlayFilm, and moving them is a separate job.The wrong project is watched
The trigger listens to the one Project you picked. Launch a new video in another project and its leads never reach the Zap until you build another one.A sudden wave gets held back
If a campaign brings a huge batch of submissions at once, Zapier's flood protection can hold them back instead of running them all.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches starts itself again and again, and burns through your tasks fast. Keep outputs elsewhere.
Need help automating PlayFilm with Zapier?
A person reads every message.



