- Home
- Resources
- Integrations
- Palette
Palette Zapier integrationAutomate Palette with Zapier.
Palette Zapier integration, in plain numbers: 1 action, 0 triggers and 0 searches. Palette never starts anything on its own. Another app hands it a black and white picture, and Palette returns colorized versions, on the free plan too.
Verified Trustpilot reviews · AI, automation & growth agency
What the Palette Zapier integration actually does
Palette is an AI colorization service: you give it a black and white picture, it gives back one colorized take or several. Plugged into Zapier, the no-code tool that chains apps together, it offers exactly one move, Colorize an Image Using Palette. That move always sits behind another app, the one that brings the image in.
Three results people build with that single action. A colorized archive. Old scans pile up in a shared folder, Colorize an Image Using Palette processes each new one, and a later step files the color copy next to the original. Several takes to pick from. The Starting Colorization Filter Index field chooses where Palette starts among its variations: a low value stays sober and dependable, a high one goes brighter but less reliable. You pick a number between 1 and 115 once, and every image follows it. A colorized copy for every upload. A form or a storage app receives a photo, and Palette works on it without anyone opening a browser tab.
Now the honest part. Zapier does not let Palette start a Zap: there is no trigger, so nothing that happens inside Palette can set off a workflow. There is no search either, so a Zap cannot look up a colorization made earlier. And the action does one thing only. Anything else Palette offers stays outside Zapier.
Comparing tools before committing? See Make vs Zapier and n8n vs Zapier.
Zapier words, in one minute
Seven terms come back on this page. Here they are once, in everyday words, so the rest reads without a dictionary.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. Palette has none, so another app plays this role.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you. Colorize an Image Using Palette is one.
- Task
- The unit Zapier bills. One task is one action that finished successfully; the number printed on your plan counts those, nothing else.
- Polling or instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap continue only when what arrived matches the condition you set, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger plus one action. A second action, a filter or a search turns it into one, and it then needs a paid plan.
What a Palette Zap really costs
Palette is not reserved for paid plans: it works on the free plan. The bill is counted in tasks, and only a colorization that goes through counts.
- Free plan100 tasks a month
- Free plan Zap size2 steps: 1 trigger, 1 action
- Palette on the free planYes, not a paid-only app
- Cost of the trigger0 tasks
The trigger never costs a task, and Zapier checking for new files costs nothing either. A failed colorization is not counted. The free plan gives 100 tasks a month and builds two-step Zaps only: one trigger, one action. Add a step that files the colorized result somewhere, or a filter, and the Zap becomes multi-step, which needs a paid plan. The interval below applies to the starting app when its trigger is a polling one.
Connect Palette to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your Palette account linked once, then reused by every Zap that colorizes something.
- 02
Find Palette
Type Palette in the search box of the dialog, select it, then click Add connection. You need an existing Palette account before this point; Zapier does not create one for you.
- 03
Sign in and allow access
Sign in to Palette in the tab that opens and grant Zapier access to the account. If the pictures live in a folder someone else owns, make sure you have read access to it in the app that stores them.
Your first Palette Zap
GoalColorize every scan dropped into a Google Drive folder and store the result in a second folder.
- 01
Pick the starting app
Create a Zap and choose Google Drive with New File in Folder as the trigger. Point it at the folder where the black and white scans arrive.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next step on a real scan rather than a guess.
- 03
Add the Palette action
Add Colorize an Image Using Palette. Map the file into File, give it a Filename, and set Starting Colorization Filter Index; start low if you want safe results.
- 04
File the result
Add Upload File and target a folder other than the watched one, or the Zap fires again on its own output. This third step makes the Zap multi-step, which needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back before going further. When the output looks right, publish the Zap to switch it on.
The Palette action, in detail
Palette gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Colorize an Image Using Palette
ActionIn Zapier“Follow the details below or check out docs.palette.fm for more info.”
Sends a black and white picture to Palette and gets colorized takes in return, ready for the next step of the Zap to store or share.
When a Palette Zap breaks
Zapier attaches no help article to Palette, and no app-specific limit is documented. What breaks is what breaks on every Zap.
Four situations to know before you switch the Zap on. If one of them hits you anyway, Zapier troubleshooting is the place to start.
Old scans are ignored
A Zap only reacts to what happens after it is switched on. The images already sitting in the folder are never picked up; moving that backlog is a separate job.The Zap feeds itself
Drop the colorized result into the very folder the trigger watches and the Zap fires again on its own output, over and over, burning tasks fast.A bulk import gets held back
Copy hundreds of scans at once, after a migration for example, and Zapier's flood protection can hold the batch back instead of colorizing everything.No duplicates on polling
On a polling trigger, Zapier remembers what it has already seen, so the same image does not start the Zap twice. Good news for reruns: no double colorization, no double count.
Need help automating Palette with Zapier?
A person reads every message.



