Resources · Zapier integration

Pics.io Zapier integrationAutomate Pics.io with Zapier.

The Pics.io Zapier integration offers 11 triggers, 1 action and 0 searches. Nearly everything that happens to an asset in your library (a new file, a comment, a rating, a move) can start a Zap at once, and Zapier can also create collections for you.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pics.io Zapier integration is good for

Pics.io is a digital asset library that runs on top of Google Drive: it is where your team stores, tags and reviews images and files. Linking it to Zapier lets the events in that library start a Zap (the automation you build on Zapier: one starting event, then the steps that follow) in your other tools, and lets those tools open new collections in Pics.io.

Three results worth building. Review requests that reach people: Assets Assigned and New Comment turn library activity into a chat or email message for the right person. An approval pipeline: Assets Flag Changed, Assets Raiting Changed or Assets Moved to Collection tell your project tool that a file is ready to go further. Collections that follow your projects: Create Collection opens a new folder in Pics.io whenever a project or client appears in another app.

What Zapier does not do here. There is one action only: a Zap cannot upload an asset, edit its metadata, rate it or move it. There is no search either, so a Zap cannot look up an existing asset or collection by name. Most of the work, therefore, flows out of Pics.io rather than into it.

The upside is timing. All eleven triggers are instant, and that matters most on the free plan. For an overall take on the platform, see our Zapier review; for the editor itself, there is Zapier training.

Vocabulary

Zapier words, in plain terms

The vocabulary this page uses, defined once.

Zap
Your automation on Zapier. An event starts it, then one or more steps run each time that event happens again.
Trigger
The event that starts a Zap. Pics.io offers eleven, from a new asset to a changed rating or a fresh comment.
Action
The step that does the work once the Zap has started. Pics.io has one: it creates a collection in your library.
Task
The unit Zapier bills: one action completed successfully. Your plan includes a fixed number of them every month.
Instant trigger
The app tells Zapier itself the moment the event happens, with no timer, on every plan. All eleven Pics.io triggers work this way.
Polling trigger
A trigger Zapier checks on a timer, at an interval set by your plan, to collect new items. Pics.io has none of these.
Filter
A step that lets the Zap continue only when the incoming data matches your condition, and halts it otherwise.
Multi-step Zap
Anything beyond one trigger and one action. A second action or a filter makes one, and that requires a paid plan.
Cost

What a Pics.io Zap costs

Pics.io is not a premium app on Zapier, so it works on the free plan. You pay in tasks, never for the trigger.

  • Free plan100 tasks a month, unlimited Zaps
  • Zap size on FreeOne trigger and one action
  • Pics.io triggersInstant, never billed
  • Create CollectionOne task each time it succeeds

A Pics.io trigger never costs a task, no matter how busy your library gets. Each action that succeeds costs one, whether it is Create Collection or a step in another app; a failed action is not counted. A Zap that sends a Slack message and then logs a row uses two tasks per event, and needs a paid plan because the free plan stops at two steps. The interval grid below only slows polling triggers, so it does not apply to the eleven instant triggers of Pics.io.

Connect

Connect Pics.io to Zapier in three steps

  1. 01

    Open your connections

    Go to the Apps page of your Zapier account and click + Add connection. A connection is your Pics.io account linked once, then reused by every Zap that works with your library.

  2. 02

    Select Pics.io

    Search for Pics.io in the dialog, pick it and click Add connection. You need a Pics.io account, and access rights on any library you do not own but want the Zap to watch.

  3. 03

    Sign in and approve

    Log in to Pics.io in the tab that opens and grant Zapier access. If you plan to use Create Collection, check that your account can add collections, not just view them.

First Zap

Your first Pics.io Zap: comments that reach the team

GoalEvery new comment left on an asset in Pics.io lands in the team's Slack channel and gets logged in a review sheet.

  1. 01

    Start with Pics.io

    In the Zap editor, choose Pics.io and the event New Comment as the trigger, then select the Pics.io connection you added.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent comments from your account, so you can map the next steps on a real one.

  3. 03

    Post to Slack

    Add Slack as the first action and write a short message for the creative channel, using the comment details the test brought back.

  4. 04

    Log the review

    Add Google Sheets as a second action to keep a line per comment. Two actions make it a multi-step Zap, so a paid plan is required.

  5. 05

    Test and publish

    Test both actions, then check the message and the new row. When they look right, click Publish to switch the Zap on for the whole team.

Triggers

The 11 Pics.io triggers

11 events start a Zap when something happens in Pics.io, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Assets Assigned

Instant trigger

In Zapier“Triggers when asset is assigned to teammate.”

Starts your Zap when an asset in your library is assigned to a teammate. It turns an assignment that would sit unnoticed inside Pics.io into a message the person actually sees.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an art director assigns retouching jobs in Pics.io and wants each retoucher pinged in Slack with the asset in question.
Watch out
assignments made before the Zap was published are not replayed, so existing work stays silent.
2

Assets Added to Collection

Instant trigger

In Zapier“Triggers when asset is added to particular collection.”

Fires when an asset is added to a particular collection. It is the trigger for anything that should react the moment a file joins a set your team curates.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a brand team keeps a press kit collection and wants the PR agency told whenever a new image lands in it.
Watch out
compare it with Assets Moved to Collection and pick the one that matches how your team files assets.
3

Assets Color Changed

Instant trigger

In Zapier“Triggers when asset is color changed.”

Reacts when the color label on an asset changes. Teams that use colors as a quick status code can turn that one click in Pics.io into a step somewhere else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a photo studio marks client picks with a color and wants each pick added to the order sheet.
Watch out
the trigger fires on any change, so add a filter if only one color should count, which makes the Zap multi-step.
4

Assets Flag Changed

Instant trigger

In Zapier“Triggers when asset is flag changed.”

Goes off when the flag on an asset changes. Where your team flags files as approved or rejected, this is the hook that carries the decision out of the library.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketing manager flags final visuals and wants the web team told by email that they can publish.
Watch out
it reports flag changes in general, so check what the test returns before treating every run as an approval.
5

Assets Metadata Changed

Instant trigger

In Zapier“Triggers when asset is metadata changed.”

Fires whenever the metadata of an asset changes in your library. It is the one to use when the information about a file matters more than the file itself.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a catalog manager wants every metadata edit mirrored in the product spreadsheet that the e-commerce team works from.
Watch out
if your Zap writes back into a tool that syncs metadata to Pics.io, it can set itself off again.
6

Assets Moved to Collection

Instant trigger

In Zapier“Triggers when asset is moved to collection.”

Starts the Zap when an asset is moved into a collection. Teams that move files from one stage to the next, from draft to review to final, can use each move as a signal.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency moves approved designs into a delivery collection and wants a task created for the account manager.
Watch out
a move is not an addition; if your team adds assets to several collections instead, use Assets Added to Collection.
7

Assets Raiting Changed

Instant trigger

In Zapier“Triggers when asset is raiting changed.”

Any change to the rating of an asset sets this one off. The name keeps the editor's own spelling, Raiting, which is what you will type in the search box to find it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a social media lead rates candidate photos and wants the top-rated ones listed in the content calendar.
Watch out
lowering a rating fires it too, so a filter on the rating value keeps the Zap focused, at the cost of a paid plan.
8

New Comment

Instant trigger

In Zapier“Triggers when a new comment is added.”

Fires when someone adds a comment in Pics.io. Feedback on visuals often goes unread inside a library; this trigger brings it to where the conversation actually happens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a freelance designer wants client comments on drafts forwarded to their inbox so no remark slips by.
Watch out
a busy review round can mean many comments, and each action they start costs a task.
9

New Asset

Instant trigger

In Zapier“Triggers when a new asset is created.”

Each time a new asset is created in the library, this trigger runs your Zap. It is the broadest entry point: every new file, whoever added it, passes through here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an e-commerce team wants every new product shot announced in the merchandising channel the day it is uploaded.
Watch out
a bulk upload can produce a wave of assets at once, which Zapier's flood protection may hold back.
10

Metadata Processing Completed

Instant trigger

In Zapier“Triggers when metadata processing was successfully completed.”

Fires once Pics.io has successfully finished processing the metadata of an asset. If your next step needs that metadata, starting here rather than on New Asset avoids sending a file whose details are not ready yet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a stock photo team exports each processed image's details to a sheet before pricing it.
Watch out
it only fires when processing succeeds, so a file whose processing fails never reaches the Zap.
11

New Collection

Instant trigger

In Zapier“Triggers when a new collection is created.”

A new collection created in Pics.io is what this trigger listens for. Collections often mirror projects or clients, so a new one is a good moment to set things up elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a production company wants a matching project board created in its task tool for every new shoot collection.
Watch out
collections made by the Create Collection action fire it as well, which can loop if both sit in one Zap chain.
Actions

The Pics.io action

Pics.io gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Collection

Action

In Zapier“Creates a collection.”

Opens a new collection in your Pics.io library, under the parent collection you choose and with the name you give it.

When to use it
a new client signs in your CRM and their asset folder should be ready before the first shoot.
Watch out
both the parent and the name are required, and the new collection will also fire New Collection.
When it breaks

When a Pics.io Zap breaks

Zapier lists no help article for Pics.io, so the cases below come from the operations themselves and from limits every Zap shares.

With eleven instant triggers, the risks are less about delay and more about volume and loops. When the problem is somewhere else, Zapier troubleshooting covers the general method.

  • Collections that create collections

    A Zap that runs Create Collection can fire New Collection. If another Zap listens to that trigger and creates a collection in turn, they feed each other and drain your tasks.

  • No parent, no collection

    Create Collection needs an existing parent collection and a name. If the parent is missing or the name arrives empty from the previous step, nothing gets created.

  • Past activity is not replayed

    A Zap only reacts to what happens after it is switched on. Assets, comments and ratings that existed before stay where they are.

  • Bulk uploads held back

    Uploading or retagging a large batch at once can trigger Zapier's flood protection, which holds the batch instead of running each event.

  • Filters need a paid plan

    Color, flag and rating triggers fire on every change. Narrowing them with a filter makes the Zap multi-step, which the free plan does not run.

  • Busy libraries, busy task count

    Each event that reaches a successful action costs a task. A trigger as broad as New Asset or New Comment can use up the free plan's 100 tasks quickly.
Need help

Need help automating Pics.io with Zapier?

A person reads every message.

FAQ

Pics.io Zapier integration: frequent questions

01Is the Pics.io Zapier integration free?
Yes, on Zapier's side. Pics.io is not a premium app, so its eleven triggers and its action all work on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, but every Zap is capped at two steps: one trigger and one action. As soon as you add a filter, for instance to keep only one flag value, or a second action, the Zap becomes multi-step and needs a paid plan. Your Pics.io subscription is a separate matter.
02How many tasks does a Pics.io Zap use?
One per successful action. The Pics.io trigger never costs anything, however many assets, comments or ratings your team produces. A Zap that posts a Slack message for each new comment uses one task per comment. A Zap that also logs a row uses two. Create Collection counts as one task each time it works. A failed action is not counted, so a missing parent collection does not cost you, though nothing gets created either.
03Are Pics.io triggers real time?
Yes, all of them. The eleven Pics.io triggers are instant: the app tells Zapier the moment the event happens, and the Zap starts right away, whatever your plan. The interval grid that governs polling triggers, 15 minutes on the free plan, does not apply here. That makes Pics.io a comfortable fit for the free plan when reaction time matters, for example notifying a retoucher the moment an asset is assigned to them.
04What does it take to connect Pics.io to Zapier?
A Pics.io account, plus access to any library or collection that belongs to someone else and that you want the Zap to touch. From the Apps page of your Zapier account, add a connection, search for Pics.io, sign in on the tab that opens and grant access. If you plan to use Create Collection, you also need a parent collection already in place, since the action will not run without one, along with a name for the new collection.
05Why does a Pics.io Zap keep creating collections?
Most likely because of a loop. Create Collection makes a new collection, and every new collection fires the New Collection trigger. If one of your Zaps listens to New Collection and another, or the same chain, creates a collection in response, each run starts the next one and burns through your tasks. Keep the trigger and the action in separate, unrelated flows, or add a filter that lets only the collections you expect go through.
06What if the Pics.io operation you need is missing?
Then Zapier does not offer it right now. Pics.io exposes eleven triggers and a single action there, Create Collection, with no search. A Zap cannot upload an asset, change its metadata, rate it, move it or look it up by name. If your process needs one of those steps, it has to happen in Pics.io itself. The Pics.io page on zapier.com shows the current list and is the place to check before planning around a missing operation.
07Zapier, Make or n8n for Pics.io?
Decide on criteria, not on a ranking. On Zapier, Pics.io gives you eleven instant triggers that work on the free plan and one action, billed per successful action, with no search and no way to edit assets. If your flow mostly pushes library events to other tools, count the actions per event and the plan they require. If it needs to change assets inside Pics.io, check what each platform's catalog offers for the app before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations