Zapier with Muapi

Use the Muapi app in Zapier to run a media generation action or trigger a Zap when a generation completes. The connection uses a Muapi API key.

Connect Muapi

Create an API key in your Muapi dashboard. Keep it private; anyone with the key can use your account.
In Zapier, add a Muapi step and create a connection with that API key.
Test the connection. If the test fails, verify the key and that your Muapi account has available credits.

Run a generation action

Add the Muapi generation action, select an enabled model, and fill in the fields shown for it. Zapier's model list and input fields come from Muapi's enabled model catalog and can change over time. Check the model's Playground page or Models for its current inputs and price.

Generation runs asynchronously. The action returns a request ID and task status; use the completed-generation trigger to continue a Zap when outputs are ready. Include a status check in your Zap so failed generations do not flow through as successful media.

Trigger on completed generations

Use Muapi's Completed Generation trigger. Zapier registers a webhook for new completion events. A polling trigger is also available as a fallback and for loading sample data while configuring a Zap.

The trigger provides the request ID, model, status, outputs, creation time, and execution time. Map the output URLs into later Zap steps. If the task failed, inspect its status before using the outputs.

Troubleshooting

Authentication fails: create a fresh Muapi API key and reconnect the Muapi account in Zapier.
A model or field is missing: confirm the model is enabled and review its current schema in the Playground.
The trigger has no recent sample: run a generation with the same Muapi account, then reload trigger samples.
The Zap runs before media is ready: use the completed-generation trigger rather than treating the initial generation request as a finished output.

See Quick Start for the generation lifecycle, Credits for billing, and Webhooks for general callback behavior.