Short answer: Drop the "Gumlet → Upload Video to Gumlet" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Collection ID collection_id | string | Required | — |
Source URL input_url | string | Required | A fully qualified URL (https://...) for the source url. |
Title title | string | Optional | — |
Output Format format | options | Optional | — |
{"collection_id": "{{trigger.collection_id}}","input_url": "https://my-cdn.example.com/video.mp4","title": "{{trigger.title}}","format": "{{trigger.format}}"}
{"status": "queued","asset_id": "abc-123","playback_url": null}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.