Resources · Zapier integration

Pictory Zapier integrationAutomate Pictory with Zapier.

The Pictory Zapier integration gives you 9 actions, 0 triggers and 0 searches. Pictory never starts a Zap on its own: another app fires it, then Pictory builds a storyboard, a summary, a template or a final render from what that app hands over.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pictory Zapier integration actually does

Connecting Pictory to Zapier means another tool sends Pictory the raw material (an article link, a slide deck, a block of text, a video link) and Pictory turns it into a video project without anyone opening its editor. Zapier is the go-between: it watches the first app, then calls Pictory for you.

Three concrete results come out of it. A content team that publishes articles gets a draft video for each post, through Create Storyboard From Blog Post. A sales or training team gets a narrated version of its decks, through Create Storyboard Preview From PPT, which can even reuse the speaker notes as subtitles. And anyone sitting on long recordings gets a short cut of them, through Create Video Summary, fed with a link to the video and the language spoken in it.

The storyboard actions build the plan of the video. Turning that plan into a finished file is a separate step: Render Storyboard Preview takes the job of a storyboard, and Render Project renders a saved project. Two Pictory actions in a row make a multi-step Zap, so that chain needs a paid plan (more on that in the cost section).

Now the limits. Pictory has no trigger on Zapier: no Zap can start because a video finished or a project changed in Pictory. It has no search either, so a Zap cannot look up an existing project or template by name; it needs the ID handed to it by an earlier step or typed in. Anything you want to react to has to happen in another app first.

If you are weighing tools, the same app also has a Pictory Make integration page, and the Make vs Zapier comparison sits next to it.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here is what each one means, in plain terms.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Pictory offers none on Zapier, so another app always plays this part here.
Action
What the Zap does once it has started. On this page, it is the step where Pictory builds a storyboard, a summary or a render.
Task
The unit Zapier bills: one action that completes successfully. The monthly count on your plan is a count of those.
Polling vs instant trigger
A polling trigger is checked on a timer that depends on your plan. An instant trigger is reported by the app itself, with no wait.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your Pictory account linked to Zapier once, then reused by every Pictory step in every Zap you build afterwards.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What Pictory on Zapier really costs

Pictory is not a premium app, so it works from the free plan. The bill is counted in tasks, and only on actions that go through.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger checks0 tasks
  • Failed actionNot counted

The trigger costs nothing, however often Zapier checks the other app. Each Pictory action that succeeds counts as one task; a failed one is not counted. A few apps and actions take more than one task, so keep an eye on the count after your first runs. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one Pictory action. Storyboard plus render, or a filter in front, makes a multi-step Zap, which needs a paid plan.

Connect

Connect your Pictory account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to the Apps page and click + Add connection. You need a Pictory account first, plus access to any project you do not own and want the Zap to touch.

  2. 02

    Pick Pictory and add it

    Type Pictory in the search box of the dialog, select it, then click Add connection. Zapier then opens a new tab where Pictory asks you to sign in with your usual account.

  3. 03

    Sign in and grant access

    Log in to Pictory in that tab and allow Zapier to reach the account. The connection is then saved once and offered again in every Pictory step you add later.

First Zap

Your first Zap: from a row of article links to a rendered video

GoalEvery new article link added to a sheet becomes a Pictory storyboard, then a rendered preview.

  1. 01

    Build: choose what starts it

    Create a Zap and pick the app that holds your article links, with the event that starts the Zap. Pictory cannot sit here, since it has no trigger.

  2. 02

    Test the trigger on real data

    Run the test: Zapier brings back the three most recent items of the connected account. Pick one with a real article link, so the mapping uses true values.

  3. 03

    Add the storyboard action

    Add Pictory with Create Storyboard From Blog Post. Map the article link, fill in Video Name (required) and decide on voiceover and background music.

  4. 04

    Chain the render

    Add a second Pictory step, Render Storyboard Preview, and map into Job Id the job returned by the storyboard step. This second action makes the Zap multi-step.

  5. 05

    Test each step, then publish

    Run each Pictory step once and read what came back before going on. When both results look right, click Publish to switch the Zap on.

Actions

The 9 Pictory actions, one by one

Pictory gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Template From Project File

Action

In Zapier“Use this action to upload a pictory webapp project to create a template.”

Uploads a project file made in the Pictory web app and turns it into a reusable template. You only need the Pictory Project File, which is required.

When to use it
a designer finalises one branded project, and the Zap converts it into a template the whole team can feed later.
Watch out
the file has to come from an earlier step, so the app that starts the Zap must carry that file.
2

Create Storyboard From Blog Post

Action

In Zapier“Create a video storyboard using an article URL. Includes audio, and styling configuration.”

Give it the link to an article and Pictory drafts a video storyboard from the text, with audio and styling settings included. Name the project in Video Name, then switch voiceover, background music and subtitles on or off.

When to use it
a blog that wants a short video version of each new post without anyone doing it by hand.
Watch out
leave Save Project off and the project is not kept for later edits.
3

Create Storyboard Preview From PPT

Action

In Zapier“Create a video storyboard using PPT deck. Includes audio, and styling configuration.”

Works from a slide deck rather than an article. One setting stands out: Use Speaker Notes pulls the notes under each slide and uses them as scene subtitles.

When to use it
a training or sales team that keeps its talking points in the notes of its decks and wants them on screen.
Watch out
without notes in the deck, that option has nothing to pull, and the scenes come out without your script.
4

Create Storyboard Preview From Template

Action

In Zapier“Generates a video based on the given template and variables.”

Starts from one of your Pictory templates and fills it with the variables the Zap sends. Two fields are required: Template, the ID of the template, and Video Name, capped at 150 characters.

When to use it
recurring videos with a fixed layout, where only the wording changes from one run to the next.
Watch out
a name longer than 150 characters is refused, so trim long titles coming from the first app.
5

Create Storyboard Preview From Text

Action

In Zapier“Create a video storyboard using raw text. Includes audio, and styling configuration.”

Takes raw text and cuts it into scenes. You choose how: a new scene on each line break, a new scene at each end of sentence (period, question mark, exclamation point), or both.

When to use it
scripts written in a form or a document, where every line is meant to be one shot.
Watch out
text with no line breaks, and the sentence cut switched off, gives Pictory nothing to split on.
6

Create Storyboard Preview From Video

Action

In Zapier“Create a video storyboard using a video URL as input. Includes audio, and styling configuration.”

Repurposes an existing video: you pass a link in Video Url and Pictory rebuilds a storyboard around it. Audio Language, the language spoken in the source, is required too.

When to use it
a webinar or interview recording that should come back as a new edit for social media.
Watch out
Audio Language describes the source, not the video you want out, so map the language actually spoken in each recording instead of a fixed default.
7

Create Video Summary

Action

In Zapier“Create a video summary using a video URL as input. Includes audio, and styling configuration.”

Shrinks a long video into a summary video. It asks for the same three required inputs as the repurposing action: Video Name, Video Url and Audio Language.

When to use it
long recordings nobody rewatches in full, such as a recorded meeting or a talk.
Watch out
unlike the storyboard actions, this one has no voiceover or music switches, only the option to hide subtitles.
8

Render Project

Action

In Zapier“Initiates the rendering process for a project, generating the final video output based on the current project configuration and content. Note: This action uses webhooks for efficient status updates and will automatically complete when rendering finishes.”

Launches the rendering of a saved project and produces the final video from its current content. The step waits and completes on its own when rendering finishes. Its only required field is Project ID.

When to use it
a project someone has reviewed in Pictory, and the Zap only has to produce the final file.
Watch out
the ID must point to a real project in the connected account, or the step fails.
9

Render Storyboard Preview

Action

In Zapier“Render video from storyboard job output”

The natural follow-up of every storyboard action: it renders the video from the output of a storyboard job. Map into Job Id the job returned by the step before it.

When to use it
right after a storyboard step, when nobody needs to review the plan before the video exists.
Watch out
storyboard plus render is two actions, so two tasks per run and a paid plan.
When it breaks

When the Pictory Zap breaks

Zapier attaches no help article to Pictory, and no limit specific to the app has been recorded. What breaks is what breaks on any Zap, applied to video work.

The cases below are the ones to check first. If a run fails without a clear reason, the Zapier troubleshooting page is the next stop.

  • Old articles never become videos

    A Zap only reacts to what happens after you switch it on. Links already sitting in your sheet are not picked up; converting that backlog is a separate job.

  • The Zap keeps restarting itself

    If a later step writes back into the very sheet or list your trigger watches, the Zap sets itself off again and again and eats your task count fast.

  • A bulk import stalls the Zap

    When the first app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • The same item is not processed twice

    On a polling trigger, Zapier remembers what it has already seen. So the same row never sends its link to Pictory twice.
Need help

Need help automating Pictory with Zapier?

A person reads every message.

FAQ

Pictory Zapier integration: frequent questions

01Is the Pictory Zapier integration free?
Yes, on the Zapier side. Pictory is not a premium app, so it runs on the free plan, which gives 100 tasks a month and Zaps of two steps. That is enough for one trigger in another app and one Pictory action, for example a storyboard from an article. It stops there: adding the render as a second action, or a filter in front, makes a multi-step Zap that needs a paid plan. Your Pictory subscription is a separate matter, and this page gives no price for either side because those grids change too often.
02How many tasks does a Pictory Zap use?
One task per Pictory action that completes. The trigger in the other app costs nothing, and neither do the checks Zapier runs on it. A Zap that creates a storyboard and then renders it uses two tasks per run, because each successful action counts on its own. An action that fails is not counted against the plan. A few apps and actions take more than one task when they complete, so read the count after the first live runs rather than assuming. On the free plan, that leaves 100 single-action runs a month.
03Does it run in real time?
It depends on the app that starts the Zap, because Pictory has no trigger of its own. If that app offers an instant trigger, it tells Zapier about the event itself and nothing waits. If its trigger is a polling one, Zapier checks on a timer set by your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. Once the Pictory step runs, Render Project waits for the render to finish and completes on its own, so the step can take a while.
04What do you need to connect Pictory to Zapier?
A Pictory account and a Zapier account, nothing else. From the Apps page in Zapier, click + Add connection, search for Pictory, click Add connection, sign in to Pictory in the tab that opens and grant access. If the Zap must work on projects or templates that belong to someone else, the connected account needs read or write access to them. The connection is made once and reused by every Pictory step afterwards, in every Zap.
05Why does Render Storyboard Preview ask for a Job Id?
Because it renders the output of a storyboard job, not a project. The storyboard actions (from a blog post, a PPT, a template, text or a video) start that job, and the render step needs its identifier in the Job Id field. In practice, place the render right after the storyboard step and map the job returned by it. Typing a fixed value does not work across runs. Keep in mind the pair is two actions, so it needs a paid plan and costs two tasks per run.
06What if the Pictory action you need does not exist?
Check the list first: the 9 visible actions cover storyboards from five sources, a video summary, a template from a project file and two kinds of render. There is no trigger and no search, so nothing on Zapier reacts to an event inside Pictory or finds an existing project by name. If the missing piece is a lookup, carry the ID from an earlier step or store it in the app that starts the Zap. If it is a reaction to something in Pictory, Zapier cannot offer it for this app today.
07Zapier, Make or n8n for Pictory?
Judge by criteria rather than by brand. On Zapier, Pictory works on the free plan for a two-step Zap, and every chain longer than that, such as storyboard then render, needs a paid plan and costs one task per action. Pictory offers 9 actions there and no trigger, so the starting event always lives in another app. Compare that with how many runs you expect each month, whether you need the render chained, and which of your other tools each platform already connects.
Same platform

Other docs you might need on this stack.

Browse all integrations