Resources · Zapier integration

Morphed Zapier integrationAutomate Morphed with Zapier.

The Morphed Zapier integration gives you 2 triggers, 2 actions and 1 search. Both triggers are instant, Morphed runs on the free plan, and each generation step asks for a model, a prompt and a Unique Request ID. Here is what every operation does and where it trips.

Beta app Zapier still marks this integration as beta.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Morphed Zapier integration actually does

Morphed is an AI creative platform that brings several image and video models under one roof. The integration ties it to Zapier, so a Zap (the automation you build on Zapier: one trigger, then one or more actions that run each time it fires) can order images or videos from other tools, and react when a generation ends.

Three results worth building. First, visuals filed where your team works: Generation Completed starts a Zap when a render is done, and Find Generation fetches its outputs for your cloud storage. Second, failures nobody misses: Generation Failed posts to your team chat, so a broken render gets a second try instead of silence. Third, images ordered from a list: each new row of a spreadsheet, with its prompt, feeds Generate Image, and the picture comes back through the first Zap.

What Zapier does not do here matters as much. Neither action picks a model for you: Model and Prompt are required on every call. There is no find-or-create, and Find Generation only looks up a generation by its ID, never by prompt or date. Morphed is also marked as beta on Zapier, which is worth knowing before you build on it. And a Zap never goes back to generations that ended before it was switched on.

To get your bearings first, see our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this page. Each is explained once, here, then used as is.

Zap
The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or generates something for you.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
Instant trigger
A trigger the app reports itself: Morphed calls Zapier when the event happens, so nothing waits for a scheduled check.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What it really costs

Morphed is not a premium app, so it works from the free plan. Zapier bills in tasks, and only successful actions count.

  • Free plan100 tasks a month, unlimited two-step Zaps
  • TriggerNever billed
  • Successful action1 task each
  • Premium appNo

The trigger never costs a task. Each action that succeeds counts once: a Zap with two actions uses two tasks per run, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps of two steps each. A search or a filter makes the Zap multi-step, which needs a paid plan. Zapier publishes the polling grid below for its plans, but it does not apply to Morphed's two triggers, which are both instant.

Connect

Connect Morphed to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page and click + Add connection. A connection is your Morphed account linked once, then reused by every step that touches Morphed.

  2. 02

    Pick Morphed

    Search for Morphed in the dialog, select it, then click Add connection. You need an account on Morphed, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and allow access

    A tab opens on Morphed. Sign in with the account your Zaps should generate with, then grant Zapier access. The connection is ready for your first trigger or action.

First Zap

Your first Zap: finished renders saved to your storage

GoalEvery Morphed generation that completes is looked up, and its output lands in a folder of your cloud storage.

  1. 01

    Pick the Morphed trigger

    Build a new Zap, choose Morphed and the event Generation Completed, then select your connection. This trigger is instant: the editor shows a lightning bolt.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so pick a real generation to build the rest of the Zap on.

  3. 03

    Add Find Generation

    Add the search Find Generation and map Generation to the ID that came with the trigger. A search makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the storage action

    Pick your cloud storage and its upload action. Map the file to the output Find Generation returned, then choose the target folder.

  5. 05

    Test, then publish

    Test each step once and open the file that arrived in the folder. If it is the right render, publish the Zap to switch it on.

Triggers

The 2 Morphed triggers

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

1

Generation Completed

Instant trigger

In Zapier“Triggers when a generation is completed.”

Starts your Zap when one of your Morphed generations finishes, image or video alike. It is the natural follow-up to a generation action, because it tells the rest of your tools that the result is ready.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
finished visuals should be filed, shared with a client folder or announced to the team without anyone watching Morphed.
Watch out
as a general precaution, a Zap that writes where its own trigger watches can set itself off again, so check the design before you publish.
2

Generation Failed

Instant trigger

In Zapier“Triggers when a generation fails.”

Runs your Zap when a Morphed generation does not go through, so the failure becomes a visible event instead of a missing file.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone needs to hear about a failed render, through a chat message, an email or a line in a log sheet, to fix the prompt or the model.
Watch out
what the trigger says about the cause is not documented outside the editor; run the test and read the sample before you map it into a message.
Actions

The 2 Morphed actions

Morphed gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Generate Image

Action

In Zapier“Generates or edits an image.”

Creates a new image, or edits one, with the model and the prompt you give it.

When to use it
product visuals or illustrations should be produced from rows, forms or briefs stored in another tool.
Watch out
Unique Request ID is required; map a stable, unique value from the trigger, so a retry reuses it without a duplicate image or a second charge.
2

Generate Video

Action

In Zapier“Generates a video from text, images, or references.”

Produces a video from a text prompt, from images, or from references you pass in.

When to use it
a still that just came out of Morphed, or a script in a doc, should become a short clip.
Watch out
Generate Audio only works when the chosen model supports native audio, and Unique Request ID is required here too.
Searches

The Morphed search

1 search step looks for data that already exists in Morphed, so a later step can use it.

A search step looks something up in Morphed and hands it to the steps that follow. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the lookup does not go as planned.

1

Find Generation

Search

In Zapier“Finds a generation by ID and returns its outputs.”

Looks up one generation by its ID and returns its outputs, so a later step can use the actual file.

When to use it
right after Generation Completed, to fetch what was produced before uploading or sharing it.
Watch out
the Generation field is required and takes an ID, so map it from an earlier step rather than typing a name.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns a search into a find-or-create. Find Generation has no find-or-create variant on Zapier.
  3. 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 it breaks

When a Morphed Zap breaks

Zapier attaches no help article to Morphed, so the known failure points are the general ones of any Zap, plus the required fields of each generation.

Read these three cases before you publish. If a Zap still stops, the next stop is our Zapier troubleshooting page.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Generations that ended earlier are not picked up; moving that backlog is a separate job.

  • A Zap that restarts itself

    A Zap that writes into the very place its trigger watches can set itself off again and again, and burn through your task count fast.

  • A large batch held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.
Need help

Need help automating Morphed with Zapier?

A person reads every message.

FAQ

Morphed Zapier integration: questions

01Is the Morphed Zapier integration free?
Yes, for two-step Zaps. Morphed is not a premium app, so it works on Zapier's free plan, which gives 100 tasks a month and an unlimited number of Zaps. Each one is limited to a trigger and an action, for example Generation Failed then a chat message. The storage Zap on this page adds Find Generation in the middle; a search makes it multi-step, so it needs a paid plan, as would a filter or a second action.
02How many tasks does a Morphed Zap use?
One task per action that succeeds, and the trigger is free. A Zap that generates one image per spreadsheet row uses one task per row; a Zap with three actions eats three times what a one-action Zap does. An action that fails is not counted against your plan. So the number to estimate is how many generations reach the Zap, multiplied by its actions; checking for events costs nothing. Filters help keep it low.
03Do Morphed triggers fire in real time?
Yes. Generation Completed and Generation Failed are both instant: Morphed tells Zapier when a generation ends, and the Zap starts right away. The polling interval of your plan does not apply to them, which matters most on the free plan. In the editor, a Zap built on either one shows a lightning bolt. The type is decided by Morphed and cannot be changed from the editor. Nothing waits for a scheduled check.
04What does it take to connect a Morphed account?
An account on Morphed, plus read or write access on anything you do not own yourself and want the Zap to touch. From the Apps page of Zapier you add a connection, pick Morphed, sign in in the tab that opens and grant access. Each generation step then asks for a Model, a Prompt and a Unique Request ID, so have those values ready before you build. The connection is made once per account and reused by every step.
05What is the Unique Request ID for?
It protects you from duplicates. Both Generate Image and Generate Video require it. Map a stable, unique value from the trigger step, such as the ID of the row or the record that started the Zap. If the step is retried, Morphed sees the same key and does not create a second generation or charge twice. A value that changes on every run, or the same fixed text for every run, defeats that purpose.
06What if the Morphed operation you need is not there?
Open the Morphed page on Zapier: it shows the current list of triggers, actions and searches, which is what the editor offers. Today that means generating images and videos, reacting to a generation that ends or fails, and finding a generation by ID. Anything beyond that, such as listing past generations, cannot be built with this integration, so check whether another automation tool covers it. The page on Zapier stays the reference.
07Zapier, Make or n8n for Morphed?
Use criteria, not a ranking. First, coverage: check whether Morphed is in the other tool's catalog; on Zapier it is, with instant triggers on every plan. Second, the shape of your flows: a Zap with a search or a second action means a paid plan on Zapier. Third, volume, since Zapier counts one task per successful action. Last, who will maintain it, as a team used to Zapier adds Morphed with nothing new to learn.
Same platform

Other docs you might need on this stack.

Browse all integrations