Plainly Zapier integrationAutomate Plainly with Zapier.
Plainly Zapier integration: 1 action, no trigger. Submit Render launches a video render in Plainly whenever something happens in another app, a new row, a new order, a new form answer. Here is how it works, what it costs in tasks and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Plainly Zapier integration actually does
The Plainly Zapier integration lets another app order a video from Plainly, without code. Plainly builds many versions of a video from one After Effects project; Zapier decides when a new version is needed and sends the request through the only operation on offer, Submit Render.
Three outcomes come up again and again, all built on that single action. First, a video per row: a marketing team fills a spreadsheet with names, offers or cities, and each new row starts a render of the matching version. Second, a video per customer event: a new order or a signed contract in your sales tool sends Submit Render a personalised thank-you clip. Third, a video per form answer: someone fills a form, and the answers become the variables of their own video.
In every case, the start comes from another app. Plainly has no trigger on Zapier, so the first step of the Zap is always someone else's event, and its speed depends on that app, not on Plainly.
What Zapier does not do here: there is no trigger to react to a finished render, no search to find an earlier one, and no action to manage templates or projects. The integration sends render requests, and that is all. Anything that should happen after the video is ready has to be handled on the Plainly side.
If you are still weighing Zapier as a platform, start with the Zapier review.
Zapier vocabulary in one minute
Six words are enough to read the rest of this page. Here they are, plainly.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Plainly, it always comes from another app, such as a new row in a sheet.
- Action
- What the Zap does once it has started: the step that writes, sends or orders something for you, here a video render.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully; the count on your plan counts only those.
- Polling vs instant
- A polling trigger is checked by Zapier at a fixed interval. An instant trigger is reported by its app the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
What a Plainly Zap really costs
Plainly is not reserved for paid Zapier plans: it works on the free plan.
- Free plan100 tasks a month
- Steps on the free plan2 (one trigger, one action)
- One render request1 task
- Plainly triggers0
The trigger of the other app costs nothing, and neither do Zapier's checks for new data. Each Submit Render that goes through is one task; a request that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: a trigger and one action. That is exactly the shape of a basic Plainly Zap. Add a filter to render only some rows, or a second action, and the Zap becomes multi-step, which needs a paid plan. How fast the Zap starts depends on the other app's trigger: if it polls, the grid on the right applies. What Plainly bills for the render itself is outside Zapier.
Connect Plainly to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your Plainly account linked once to Zapier, then reused by every Plainly step you add later.
- 02
Pick Plainly
Type Plainly in the search box of the dialog, select it in the results, then click Add connection. A new tab opens on the Plainly side for the sign-in.
- 03
Sign in and grant access
Log in to Plainly in that tab and allow Zapier to use the account. You need a Plainly account, plus access to any project you do not own yourself and want the Zap to render.
Your first Plainly Zap, step by step
GoalEach new row of a Google Sheets file that meets your condition launches a Plainly render of the matching video version.
- 01
Build: pick the trigger
Create a Zap and choose Google Sheets with New Spreadsheet Row as the event that starts it. Connect the account and pick the file and sheet.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent rows of that sheet, so you map the next steps on real values instead of placeholders.
- 03
Add the filter
Add a Filter step from the plus icon. Pick the column to look at, the rule and the value, so half-filled rows never reach Plainly. A filter makes the Zap multi-step: it needs a paid plan.
- 04
Add Submit Render
Add Plainly as the action app, choose Submit Render, select your Plainly connection, then map the row's columns into the render settings.
- 05
Test the action
Run the action once and read what came back. Check in Plainly that the render request arrived with the values you expected before going further.
- 06
Publish
Click Publish to switch the Zap on. From then on, each new row that passes the filter costs one task; rows the filter stops cost nothing.
Plainly action
Plainly gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Submit Render
ActionIn Zapier“Submits a new Render.”
Sends Plainly a request to render a new video, using data mapped from the earlier steps. A few switches shape the result: Instant download makes the link download the file instead of opening a preview, and Upload project files collects the modified project files and uploads them.
When a Plainly Zap breaks
Zapier links no help article to Plainly, so the known failure points are the ones every Zap shares. With a single action and no trigger, four of them matter here.
Most problems come from the trigger app or from how the Zap is built, not from Plainly itself. Read these cases before you publish, and keep the Zapier troubleshooting page close.
The backlog never renders
The Zap only reacts to events after it is switched on. Rows, orders or answers that already existed are never sent to Plainly; moving them is a separate job.A bulk import floods the Zap
Paste a big batch of rows at once and the trigger can return a huge set of items. Zapier's flood protection may hold it back instead of rendering everything.Each render is a task
One successful Submit Render costs one task. A busy sheet can use up the 100 monthly tasks of the free plan faster than expected.Silent failures
With On failure and On invalid off, Plainly's notice only goes out for renders that work. A failed or invalid one sends nothing, so switch both on when someone needs to know.
Need help automating Plainly with Zapier?
A person reads every message.
