Resources · Make integration

pixx.io Make integrationAutomate pixx.io with Make.

Can your asset library feed itself while you work elsewhere? The pixx.io Make integration gives you 18 modules, 14 actions and 4 searches, for files, DirectLinks, collections and users. This page walks you from the connection to your first working scenario.

Try the pixx.io integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the pixx.io Make integration automate?

The pixx.io Make integration links your pixx.io account to Make so that files, DirectLinks, collections and users can be handled inside a scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain: here, an action that changes something in pixx.io, or a search that returns a list.

Assets that file themselves. An attachment reaches your inbox or a form collects a logo: Upload File sends it to pixx.io, and Create DirectLink can produce a link to it right after, ready to paste into the next app.

Accounts that follow your team. A new designer joins, Create User opens their access; someone leaves, List Users helps you find the account and Delete User closes it. Update User covers the moves in between.

Metadata kept in step. When a product changes in your catalog, Update Files carries the change onto the matching files, and Get File reads what pixx.io already holds before you touch anything.

What Make does not offer here: pixx.io has no trigger module, so a scenario starts from another app or from Make's schedule, and there is no Make an API Call module for anything the 18 modules miss. The Make documentation for pixx.io also warns that it is AI-generated from the vendor's docs, so check important details with pixx.io.

Many apps also have an n8n node; if you are weighing both tools, read n8n vs Make. For the plans behind each scenario, see Make pricing, and if you would rather learn the editor properly, Make training starts from zero.

Connect

How do you connect pixx.io to Make?

  1. 01

    Copy your pixx.io API key

    In pixx.io, open Settings, then Management, then API Keys, and copy the key shown on screen. Make will ask for it in a moment, so keep it at hand.

  2. 02

    Add a pixx.io module in Make

    In your scenario, click the + and search for pixx.io, pick any module and click Create a connection. The connection is your pixx.io account linked to Make once, then reused by every pixx.io module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the credentials you copied from pixx.io, or follow the instructions Make shows on screen, then confirm. From now on the module can read your account and propose what it finds there.

First scenario

Your first scenario: send incoming files to pixx.io and get a link

GoalWhen a file arrives in another app, Make uploads it to pixx.io and creates a DirectLink for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since pixx.io has no trigger, this first module comes from the app where your files arrive.

  2. 02

    Add Upload File

    Click the + on the right of that first module, search for pixx.io and choose Upload File. Pick your connection, then map the file coming from the previous module into its fields.

  3. 03

    Chain Create DirectLink

    Add Create DirectLink after Upload File and map the uploaded file from the step before. The link it returns can travel on to a message, a spreadsheet or a project card.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open each module's bubble to read the bundles it received, the items passed from one module to the next, and check that the file really reached pixx.io.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, a minimum of 15 minutes on the Free plan) and switch the scenario on. It now runs without you.

Modules

What each pixx.io module does in Make

pixx.io gives you 18 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

pixx.io2

Create User

ActionIn the docs only

With Create User, a newcomer gets a pixx.io account as soon as the scenario reaches this module, which saves a detour through the pixx.io admin screens every time the team grows.

When to use it
a hire is recorded in your HR tool or a signup form, and access to the asset library should follow.
Watch out
Run once really creates the account, so test with a dummy address and remove it afterward with Delete User.
pixx.io4

Delete Files

ActionIn the docs only

Clearing files out of pixx.io without opening it is the job of Delete Files. It fits cleanup that depends on an event recorded somewhere else.

When to use it
a product is withdrawn from your online store and its pictures should leave the library as well.
Watch out
treat the deletion as final and try the scenario on a throwaway file with Run once before pointing it at real assets.
pixx.io5

Delete User

ActionIn the docs only

Offboarding gets one step shorter with Delete User, which closes a pixx.io account as part of a scenario instead of a manual task someone forgets.

When to use it
a departure is logged in your HR tool or a spreadsheet, and the person's access to your assets has to end with it.
Watch out
treat it as final; identify the account with Get User or List Users first and check the bundle during Run once.
pixx.io6

Download / Convert File

ActionIn the docs only

Download / Convert File takes a file out of pixx.io and hands it to the next module as data, for instance to attach it to an email or store it in cloud storage. The name also announces a conversion, whose options the doc does not describe.

When to use it
a partner requests an asset and it should reach them through another app.
Watch out
the Free plan handles files up to 5 MB, so heavy originals may need a paid plan.
pixx.io7

Get Collection

ActionIn the docs only

Get Collection reads one pixx.io collection and passes its details down the scenario, so information already stored in pixx.io can be reused instead of retyped.

When to use it
you know exactly which collection you need, for example because its reference sits in a project record in another tool.
Watch out
it targets a single collection; when you need to browse them, List Collections is the module to pick.
pixx.io9

Get File

ActionIn the docs only

Get File reads a single pixx.io file so its information can fill the next modules, for example a record in a CRM or a row in a spreadsheet.

When to use it
an earlier module already told you which file matters, and you want its details before updating or sharing it.
Watch out
if what you need is the file itself, to attach or store elsewhere, Download / Convert File is the better match.
pixx.io10

Get User

ActionIn the docs only

Get User pulls one pixx.io user into the scenario so the following modules can check or reuse that person's details.

When to use it
just before Update User or Delete User, to confirm that the change lands on the right account.
Watch out
it expects one precise user; when you need several people or don't know who exactly, List Users returns the whole list as separate bundles.
pixx.io11

List Collections

SearchIn the docs only

List Collections returns the collections of your pixx.io account, zero, one or many. Each one becomes a bundle, a separate item flowing to the next module, so whatever follows runs once per collection.

When to use it
you want an overview of your collections in a report or a spreadsheet.
Watch out
each extra bundle means more operations in the modules after it, since Make counts every module run on your plan.
pixx.io13

List Files

SearchIn the docs only

For bulk work on your library, List Files is the starting point: it brings several pixx.io files into the scenario at once, each file as its own bundle.

When to use it
you want to update or export a batch of files rather than one.
Watch out
the modules placed after it run once per file, and each of those runs is an operation counted on your Make plan, so a large library adds up quickly.
pixx.io14

List Users

SearchIn the docs only

List Users brings back the people who hold a pixx.io account, one bundle per person, which gives you the roster without any manual export.

When to use it
comparing pixx.io accounts with your HR list to spot the ones nobody uses anymore.
Watch out
the list can hold zero, one or many users; test it with Run once before you chain Delete User behind it.
pixx.io16

Update Files

ActionIn the docs only

Update Files writes new information onto pixx.io files from your scenario, so what you maintain in another tool reaches your asset library too.

When to use it
a product name or a project status changes in your catalog or CRM, and the matching files should say the same.
Watch out
the doc lists no editable properties; check them in the module, and run it on a test file first.
pixx.io17

Update User

ActionIn the docs only

Update User keeps a pixx.io account in line with changes recorded elsewhere, without anyone editing it by hand in pixx.io.

When to use it
someone switches team or changes name in your HR tool, and pixx.io should show the same information.
Watch out
find the account first with Get User or List Users, otherwise the update may land on the wrong person.
pixx.io18

Upload File

ActionIn the docs only

Upload File places a file in pixx.io from any earlier module: an email attachment, a form upload, a file sitting in cloud storage.

When to use it
assets arrive outside pixx.io and should end up in one place, without anyone downloading and uploading them again.
Watch out
the Free plan caps files at 5 MB and data transfer at 512 MB, so heavy media call for a paid plan.
Need help

Need help automating pixx.io with Make?

A person reads every message.

FAQ

pixx.io and Make: common questions

01Is the pixx.io Make integration free?
Yes, on the Make side. pixx.io is a standard app, available from the Free plan, like the 3,000+ standard apps Make offers on every plan. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits. You still need your own active pixx.io account.
02What do you need to connect pixx.io to Make?
An active pixx.io account and an API key. You find the key in pixx.io under Settings, then Management, then API Keys, and copy it. In Make, add any pixx.io module, click Create a connection, give it a name if you like and paste the key. The connection is stored once and reused by all 18 pixx.io modules, so you never paste the key twice. If your account shows no API key, check your subscription on the pixx.io pricing page.
03Can pixx.io trigger a Make scenario in real time?
No. pixx.io has no trigger module in Make, neither scheduled nor instant, so a change inside pixx.io cannot start a scenario on its own. You have two ways to begin. Start from another app's trigger, a new email or a new form entry, and then call pixx.io modules. Or let Make's schedule start the scenario, every 15 minutes by default, with a search such as List Files or List Users as the first module.
04What if a pixx.io module is missing in Make?
It depends on what you need. The integration has 18 modules, 14 actions and 4 searches, and no Make an API Call module, so you cannot reach the rest of the pixx.io API from Make with this app. Check first whether a search like List Files plus an update module covers the case. The Make doc for pixx.io is AI-generated, so confirm important details with pixx.io. For anything beyond that, the team at Hack'celeration can help you find another route.
05Make or n8n for pixx.io?
It depends on your criteria, and the answer starts with what exists. On Make, pixx.io offers 18 modules, no trigger and no universal API module, and it is usable from the Free plan. Many apps also have an n8n node, so check whether pixx.io has one before comparing. After that, pick the tool where your other automations already live, because a scenario that touches pixx.io usually also touches your email, storage or HR tool.
Same platform

Other docs you might need on this stack.

Browse all integrations