Does Martini support webhooks and export?
Short answer
Martini supports webhook callbacks for async jobs (long-running video generations) and direct file export from each output node. Webhooks are configured per project; exports are click-to-download for individual files or batch ZIP for full project assets. NLE export produces project files for Premiere or DaVinci Resolve.
Webhooks for async jobs
Long-running generations — most video models, lip-sync, and large-batch image runs — are processed asynchronously. Martini submits the job to the upstream provider, returns immediately, and tracks the job in the async_jobs table. When the job completes (or fails), Martini fires a webhook to a URL you configure on the project. The payload includes the job ID, project ID, output asset URLs, status, and any error details.
Configure the webhook URL in project settings. The endpoint must respond with a 2xx status within a few seconds, otherwise the webhook is retried with exponential backoff. Make your handler idempotent — duplicate deliveries can happen during retries, so use the job ID as a deduplication key. Webhook events fire on completed and failed states by default; output and started events are available via filter.
Per-node file export
Every output node has a download button that exports the file in the model's native format — PNG or WebP for images, MP4 for video, WAV or MP3 for audio. Click the button to save the file directly to your device. Image and video exports include the original resolution; audio exports retain the original sample rate.
Right-click on a node output to access additional export formats where supported — for example, transparent PNG for images that have alpha, or MOV with ProRes for video where the source supports it. The available formats reflect what the model actually produced; Martini does not transcode silently.
Batch ZIP export
For project-wide deliverables, use Project, Export All. The action packages every output asset in the project into a single ZIP, with a folder structure mirroring the canvas. File names include the node label and a timestamp so you can match assets back to the canvas. The ZIP is generated server-side and delivered as a download link in the notifications panel — large projects may take a minute to package.
Batch export is the cleanest path for client deliverables. Combine it with the link-only project share so the client can review on the canvas and you can hand over the assets in one drop. The export includes only successful outputs; failed and pending generations are excluded.
NLE export
For multi-shot video projects, NLE export produces a project file you can open in Adobe Premiere Pro, DaVinci Resolve, or Final Cut Pro. The export includes every video clip as a separate track, in the canvas order, with timing and source references preserved. NLE export is plan-gated — see the model card or pricing page for the included tiers.
NLE export bridges Martini and a traditional editor when the brief requires color grading, sound design, or fine timing adjustments that go beyond the canvas. Use Martini for generation and NLE for post — the export hand-off is a one-click step from the Project menu.
Examples
- Webhook fires when a Veo 3 video job completes — handler downloads the output and stores it in your CMS.
- Click the download icon on an image node to save the PNG directly.
- Project, Export All produces a ZIP with every output asset for client delivery.
- NLE export opens directly in Premiere with the canvas order and timing preserved.
- Webhook retries with backoff on a 5xx response — handler must be idempotent.
Edge cases
- Webhook payloads do not include the original prompt by default; enable include_prompt in project settings if you need it.
- Batch ZIP export packages only successful outputs; pending and failed jobs are excluded.
- NLE export availability depends on the source models supporting the formats Premiere and Resolve can ingest.
- Asset URLs in webhook payloads are time-limited signed URLs — download or store them promptly.
What to do next
- Configure a webhook URL in project settings if you are automating downstream workflows.
- Use Export All from the Project menu for client deliverables instead of one-by-one downloads.
- Make webhook handlers idempotent and verify job IDs to deduplicate retries.
- See the enterprise-access article for higher rate limits and custom webhook configurations.
Related help articles
Related features
Still need help? Contact support.