Resources · Make integration

Plytix Make integrationAutomate Plytix with Make.

Can Make keep your Plytix product catalog in step with the rest of your stack? The Plytix Make integration offers 4 action modules covering products, assets and other catalog objects. This guide shows e-commerce and catalog teams how to connect the account and run a first scenario.

Try the Plytix integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Plytix Make integration do?

The Plytix Make integration links your Plytix account, a product information management (PIM) platform, to Make, a tool where you build automations called scenarios without code. A scenario is a chain of modules, and each module is one brick of work in one app. Here, the Plytix modules act on your catalog: products, product assets and the other objects the app manages.

Product records fed from another tool. When product data lives in a spreadsheet, a form or a supplier file, a scenario can pass each row to the Products module, so the catalog in Plytix is updated from that source instead of being retyped.

Media that follows the product. Once a product is handled, the Assets module lets the same scenario deal with the images and files attached to it, which saves the back and forth between a shared drive and Plytix.

Categories, variants and relationships. The Plytix documentation lists them among what the app manages in Make. The Other module and the Triggers module ship without an official description, so open each one in the editor and read its list of operations before you plan a scenario around it.

What Make does not give you here: Plytix has no trigger module, so nothing in Plytix starts a scenario by itself, and there is no generic Make an API Call module to reach endpoints outside these 4 modules. If you also look at n8n, the n8n vs Make comparison sets out the criteria, and the Make training covers the editor basics used on this page.

Connect

How do you connect Plytix to Make?

  1. 01

    Create an API key in Plytix

    Log in to Plytix, open the API tab in your account settings and click Create API key. Plytix shows an API key and an API password: copy both and keep them somewhere safe, since Make asks for the pair.

  2. 02

    Add a Plytix module in Make

    In your scenario, add any Plytix module and click Create a connection. A connection is your Plytix account linked to Make once, then reused by every Plytix module. The Connection name field is optional but helps when you run several accounts.

  3. 03

    Paste the key and save

    Fill API key and API password with the values copied from Plytix, then click Save. If Make or Plytix asks you to authenticate and confirm access, accept, and the connection appears in the module ready to use.

First scenario

Build your first scenario with Plytix

GoalWhen product data arrives from another app, Make updates the product in Plytix and then handles its assets.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Plytix has no trigger, start with the module of the app that holds your source data, or with a scheduled start.

  2. 02

    Add the Products module

    Click the + on the right of the first module, search for Plytix and pick Products. Select your connection, or click Create a connection if this is your first Plytix module.

  3. 03

    Map the product data

    Fill the fields of Products with data from the first module. Each bundle, meaning one item passed from one module to the next, becomes one product for Plytix to process.

  4. 04

    Chain the Assets module

    Add Assets after Products and map what it needs from the previous modules, so the media work happens right after the product is handled in the same run.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time, then open each module to read the bundles it received. Fix the mapping here before any real data flows through.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, 15 minutes minimum on the Free plan) and switch the scenario on. Each module run on one bundle counts as one operation.

Modules

What can each Plytix module do in Make?

Plytix gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Plytix1

Triggers

ActionIn the docs only

Despite its name, Triggers is listed as an action: it does not start a scenario, it runs once another module has passed it a bundle. No official description exists for it, so its operations only show in the editor.

When to use it
after you have opened it and checked that one of its operations matches the job you want done in Plytix.
Watch out
do not build a scenario expecting it to fire on Plytix events; to start one, use a schedule or another app.
Plytix2

Products

ActionIn the docs only

Products gives the scenario a hand on the core of your catalog: the product records stored in Plytix. It is the module to reach for when data about an item comes from somewhere else and should end up in the PIM.

When to use it
a supplier sheet or an order tool holds product details and you want Plytix updated from it without copy and paste.
Watch out
it acts on one product per bundle, so a source with many rows means one operation per row.
Plytix3

Assets

ActionIn the docs only

Assets lets a scenario work on the product assets kept in Plytix, the images and files that sit next to each item. Pick it rather than Products when the change concerns media, not the product record itself.

When to use it
new visuals land in another tool and should be handled in Plytix in the same scenario that updated the product.
Watch out
on the Free plan, Make handles files up to 5 MB, so large media may need a paid plan.
Plytix4

Other

ActionIn the docs only

Other groups what the app does beyond products and assets. The Plytix documentation says the app also manages categories, variants and product relationships, without stating which module holds each one, so open Other to check.

When to use it
your catalog structure matters as much as the records, for example when a new product has to join a category or be linked to its variants.
Watch out
no official description exists for this module, so test its operations with Run once on a sample item first.
Need help

Need help automating Plytix with Make?

A person reads every message.

FAQ

Plytix and Make: frequent questions

01Is the Plytix Make integration free?
Yes, on the Make side. Plytix is a standard app, available from the Free plan, which allows 2 active scenarios, runs at most every 15 minutes, 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 one minute and remove the cap on active scenarios. You still need your own Plytix account and subscription, which Plytix bills separately under its own pricing.
02What do you need to connect Plytix to Make?
You need a Plytix account and an API key with its API password. Create them in the API tab of your Plytix account settings, then paste both into the Create a connection window of any Plytix module in Make and click Save. Only an Owner or an Admin of the Plytix account can view and manage API keys, so a user with a lighter role will have to ask one of them. The connection is set once and then reused by all 4 Plytix modules.
03Can a Plytix change start a Make scenario in real time?
No. Plytix has no trigger module in Make, scheduled or instant, so an event in Plytix cannot launch a scenario by itself. You start the scenario another way: with the schedule on the first module, every 15 minutes by default, or with a trigger from another app, such as a new row in a spreadsheet or a new form entry. The Plytix modules then run as actions further down the chain, one operation per bundle they process.
04What if a Plytix module is missing in Make?
It depends on what you need. The Plytix app has 4 modules and no Make an API Call module, so you cannot send a custom request to Plytix from Make to reach an operation those modules do not cover. First open Triggers and Other, which carry no official description, since the missing action may sit there. If it does not, route that step through another app of your stack, or ask the team for help designing the scenario.
05Should you use Make or n8n for Plytix?
It depends on the tool your team already uses. On Make, Plytix brings 4 action modules and no trigger, so a scenario always starts from a schedule or another app, and the connection only needs an API key and password. n8n often offers a node for the same app, so check its catalog for Plytix before choosing. Compare what each tool actually exposes for the products, assets and catalog objects you need, rather than picking by habit.
Same platform

Other docs you might need on this stack.

Browse all integrations