Mediagraph Zapier integrationAutomate Mediagraph with Zapier.
Mediagraph Zapier integration: 1 trigger, 3 actions and 2 searches to react to new assets in your Mediagraph library, tag them in bulk, push files in from a link and file them in Storage Folders, without retyping a filename.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mediagraph Zapier integration gets done
The Mediagraph Zapier integration lets Zapier, an automation service, act on your digital asset library while you do something else. It watches Mediagraph for new uploads, and it can write back: tags, Storage Folders and new assets pulled from a link. Six ready-made operations, nothing to build on the Mediagraph side.
A running log of every upload. New Asset Uploaded starts the automation each time a file lands in the library, and the next step writes it wherever your team keeps track: a spreadsheet, a chat channel, a task list. Nobody has to open Mediagraph to know something arrived.
Files that file themselves. Upload Asset takes a file from a link and drops it into the Mediagraph upload pipeline named by its Contribution ID. That ID can come from an earlier step such as Create a Storage Folder, so one Zap can open a folder and fill it.
Tags applied in one pass. Update Asset Details writes keyword tags on one or several assets at once, from a comma separated list. No more opening each file to type the same labels again.
What Zapier does not do here: there is no instant trigger, so new uploads are picked up on a timer, never the moment they happen. There is no delete action either, and nothing that already sits in the library is replayed when you switch a Zap on. If you are weighing other tools for the same job, see our n8n vs Zapier comparison.
Zapier words, in one minute
Eight words come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Here, a new asset uploaded to Mediagraph. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something, like tagging assets or creating a folder.
- Task
- The unit Zapier bills. One action that your Zap completes successfully is one task, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment it happens. Mediagraph only polls.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
- Search step
- A step that looks up something already in an app, such as a Storage Folder, so the steps after it can reuse what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What a Mediagraph Zap really costs
Mediagraph is not one of the apps Zapier keeps for paid plans: it works on the free plan.
- Free plan100 tasks a month, unlimited two-step Zaps
- Trigger checksFree, however often Zapier looks
- Failed actionNot counted against the plan
- Filter or searchMakes the Zap multi-step: paid plan
The trigger never costs a task, and neither does Zapier checking for new uploads, however often it looks. Each action that succeeds counts once, and one that fails is not billed. The free plan gives 100 tasks a month and unlimited Zaps, but each one stops at two steps. Add a filter or a Find a Storage Folder step and the Zap becomes multi-step, which needs a paid plan. Check the grid below for how often your plan looks for new assets.
Connect your Mediagraph account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Mediagraph account, plus read or write access on any folder or asset you do not own yourself but want the Zap to touch.
- 02
Pick Mediagraph
Type Mediagraph in the search box of the dialog, select it, then click Add connection at the bottom of the dialog. A new browser tab opens on the Mediagraph side.
- 03
Sign in and grant access
Sign in to Mediagraph in that tab and allow Zapier to use the account. The connection is then saved once and reused by every step of every Zap that talks to Mediagraph.
Your first Zap: post every new Mediagraph asset to your team chat
GoalEach new asset in Mediagraph becomes a message in your team chat, but only when it matches the condition you choose.
- 01
Build: start with Mediagraph
Create a Zap, pick Mediagraph as the app and New Asset Uploaded as the event, then choose the Mediagraph connection you just added.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent assets of your account, so you map the next steps on a real one rather than a guess.
- 03
Add a filter
Click the plus icon, add Filter, then fill the three boxes: the field to look at, the rule, and the value. Pick a text rule for text and a number rule for numbers. This makes the Zap multi-step.
- 04
Add the chat step
Add your chat tool as the action and map what the trigger returned into the message. Check at the test which asset details actually come through.
- 05
Test, then publish
Run each step once and read what came back. When it looks right, click Publish to switch the Zap on. Only uploads made after that point will start it.
The Mediagraph trigger
1 event starts a Zap when something happens in Mediagraph. Zapier checks for them at the interval your plan allows.
New Asset Uploaded
Polling triggerIn Zapier“Triggers when a new asset is uploaded.”
Starts your Zap whenever a fresh asset shows up in your Mediagraph library, and hands the next steps what Mediagraph returned about it. This is the only way into Mediagraph from the outside, so every Zap that reacts to the library begins here.
Mediagraph actions
Mediagraph gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Update Asset Details
ActionIn Zapier“Updates details for one or more assets.”
Writes keyword tags on one asset or several at once, so a whole batch carries the same labels.
Create a Storage Folder
ActionIn Zapier“Creates a new Storage Folder.”
Opens a new Storage Folder in Mediagraph with the name you give it, typed or mapped from an earlier step.
Upload Asset
ActionIn Zapier“Uploads a new asset.”
Brings a file into Mediagraph from a link, under the filename you set, inside the upload pipeline you point it to.
Mediagraph searches
2 search steps look for data that already exists in Mediagraph, so a later step can use it.
A search step finds something that already exists in Mediagraph and passes it on. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not what you expected.
Find a Storage Folder
SearchFind or createIn Zapier“Finds a Storage Folder.”
Looks up an existing Storage Folder from its slug, the unique identifier you see in the folder's URL, and hands it to the next steps.
Find Storage Folder Assets
SearchIn Zapier“Finds assets in a Storage Folder.”
Pulls the assets stored in a given Storage Folder so later steps can work on them.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that needed it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create. The setting above disappears and Zapier asks for the fields needed to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Mediagraph Zap breaks
Zapier attaches no help article to Mediagraph, and no rate limit specific to the app is documented. What breaks is what breaks on any Zap.
These cases cover the general limits worth knowing. When a run looks wrong, rerun the step test and read what came back, then see our Zapier troubleshooting guide is the next one.
The old assets never show up
A Zap only reacts to what happens after you publish it. Assets already in the library are not replayed, and moving that backlog is a separate job.The Zap keeps restarting itself
A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count.A bulk import goes quiet
When the trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back.An asset does not run twice
On a polling trigger Zapier remembers what it has already seen, so the same asset does not start the Zap a second time.
Need help automating Mediagraph with Zapier?
A person reads every message.
