- Integrations
- /
- Gumlet
Gumlet
Gumlet video hosting and processing
Gumlet is the video-and-image processing platform — automatic transcoding, adaptive bitrate streaming, image optimisation on-the-fly via URL params. Popular with e-learning platforms and content sites that need video infrastructure without managing FFmpeg or HLS encoding themselves. Tiny Command exposes three actions, no triggers (Gumlet emits processing events via webhooks configured per-collection; point at a Tiny Command webhook trigger URL for processed-ready, processing-failed events): Create Video (from URL) (Gumlet ingests from a publicly accessible URL — your S3, a Vimeo source, anywhere — and starts transcoding into the configured profiles), Get Video (status of a specific video; returns the embed URL and source HLS/MP4 URLs when ready), List Videos (paginated history with metadata, processing status, view counts). The connection uses a Gumlet API key from the dashboard. The standard workflow: a Tiny Command workflow uploads or sources a video, Creates Video into Gumlet for transcoding, polls Get Video (or waits for the webhook) until status is "ready", then embeds the Gumlet URL into the destination CMS/LMS/site.
Do anything Gumlet can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Upload Video to Gumlet | Ingests a video from a public URL and starts transcoding into the configured profiles. For "auto-publish video content to a video CDN" workflows. |
| Get Gumlet Video | Returns the video by ID with current processing status. When ready, returns playback URLs (HLS) and metadata. Poll until status=ready or use the configured webhook for push notification. |
| List Gumlet Videos | Paginated video catalog with metadata and view counts. Useful for inventory and for "weekly video performance digest" reporting workflows. |
Pre-built Gumlet workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Gumlet once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Gumlet field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Gumlet integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Gumlet to Tiny Command?
What Gumlet triggers does Tiny Command support?
What Gumlet actions can I run from a workflow?
Is the Gumlet integration real-time?
Do I need to write code to use Gumlet with Tiny Command?
How much does the Gumlet integration cost?
More other apps people connect.
Same category as Gumlet, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Gumlet.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.