Using BeatAPI in Zapier

The public BeatAPI app in Zapier now uses promoted version 1.1.0. Its public action list includes:

Action	Result
Create Music Video Task	Creates one asynchronous task from public image and audio URLs; returns a task ID.
Find Task	Reads the current status and output for an existing task ID.
Generate Text, Generate Image, Generate Video	Calls a selected BeatAPI model. Image and video creation may return an asynchronous task ID.
Get Social Data	Calls a selected Social Data action; may spend credits.
Search Capabilities, Inspect Capability	Finds a capability and reads its current contract before execution.
Run Capability, Get Capability Result	Starts a supported capability or retrieves a stored result.

Build a Zap

Add BeatAPI → Create Music Video Task and connect a dedicated BeatAPI API key.
Map the required public HTTPS image and audio URLs and your creative prompt.
Test the action and store its task ID in the next step.
Use Delay by Zapier before BeatAPI → Find Task. Repeat with a bounded schedule or a later Zap until the task succeeds or fails.
Use the hosted output only after the task succeeds. Keep failed and timed-out runs available for reconciliation.

For text, image, video, or Social Data, select the corresponding BeatAPI action and test its fields in the Zap editor. For dynamic capabilities, pass the Search reference unchanged to Inspect; use Run only when Inspect reports that execution is supported. Other capabilities can use Zapier’s HTTP/Webhooks tools against the BeatAPI API reference, subject to your plan. On September 26, 2026, Search, Inspect, and a short Generate Text call succeeded through Zapier’s remote invocation of promoted v1.1.0. Other model and field mappings still need separate execution checks.

Keep the API key in the Zapier connection. A successful Create step confirms task acceptance, not finished media; read the task status before downstream delivery or publication.