Shotstack Workflow Automation with Human Approval
Run Shotstack on autopilot. Keep the veto.
24 actions
Shotstack renders, template changes, and asset deletions run inside your workflows; Rills queues each action for approval before it executes.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential media action from Shotstack arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue (3)
Transfer 12 assets from completed renders to the client-facing bucket?
12 assets from render batch #1042
All renders completed with status: success
Client bucket 'final-assets' has no conflicting files
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Clear runs stop waiting on you.
Every run is scored against your review step. The ones that clearly match your judgment run above your threshold without a tap; the borderline ones still come to the queue. Autonomy is earned run by run, never switched on for good.
About Shotstack automation
Your Shotstack renders finish, assets get moved, and templates get touched before you ever see the results. A single misstep in a delete or transfer can break a campaign that's already shipping.
When Shotstack runs unsupervised
Without a human check, Shotstack automation fires off consequences you only discover later, when the damage is already in front of customers.
- Delete Template: wipes the production template during a rush job, leaving a blank generation pipeline.
- Transfer Asset: moves the wrong asset version to a client-facing bucket, serving a corrupted render.
- Delete Ingested Media: removes source files before the final render is approved, making a redo impossible.
- Get Render Callback: ignores a failure callback, letting a broken flow go unreported until the client complains.
- Update Template: applies a half-baked change that breaks a campaign's video generation mid-flight.
What Rills does inside Shotstack
Rills watches your asset pipeline and proposes the Shotstack automation actions that matter: template updates, asset transfers, media deletion, and render status checks. It surfaces the action, you swipe to approve from your phone, and nothing customer-visible moves without your call.
The template still gets updated; you just see it before it goes live.
Why Shotstack has no triggers and how Rills fills the gap
Shotstack doesn't emit events when renders finish, sources change, or templates need attention. Rills fills that gap by polling, watching upstream signals, and scheduling checks so you never miss a moment that needs a decision.
- Poll Get Render Status to detect completed renders and propose asset transfers.
- Watch for upstream changes from your CMS or ecommerce platform to trigger template updates before the next batch.
- Scheduled scans list templates with low usage or old versions, proposing deletion only after you approve.
- Periodic render callback checks surface failures and propose alerting or re-render actions.
What Rills can do in Shotstack
6 of 24 actions across reads, writes, and updates.
- 01
Create Template
Tool to create a new template for video editing.
- 02
Get Asset
Tool to fetch details of a hosted asset by its unique identifier.
- 03
Get Render Status
Tool to retrieve the current status and details of a Shotstack render job by render ID.
- 04
Get Upload URL
Tool to request a signed URL for direct file upload to Shotstack.
- 05
List Templates
Tool to list all Shotstack templates for the account.
- 06
Render Video
Starts the rendering process for a video project based on a predefined timeline and output settings, producing the final video file ready for download or sharing.
Common questions about Shotstack automation
How do I automate Shotstack template cleanup without accidentally deleting the wrong one?
Rills lets AI propose which old templates to delete based on usage, but you get a mobile notification to approve each one before it's gone. You review the list, swipe to approve the safe ones, and reject anything that looks off. No template vanishes without your call.
Can I get a mobile approval before transferring Shotstack assets to my S3 bucket?
Yes. Rills can detect finished renders, then propose transferring the asset to your storage. But you'll see a push notification with the asset name and render details. You approve the transfer from your phone before it moves. If something looks wrong, you reject it. The transfer never fires without your swipe.
How do I automate getting render status updates from Shotstack without missing a failed render?
Rills can check render statuses on a schedule and flag any that failed or took too long. Instead of dumping a list in Slack, it proposes an action: maybe alert you, or retry if safe. You review the proposal on your phone and approve the next step. That way, a broken render never gets ignored until a client complains.
How is Rills different from Zapier for Shotstack automation?
Zapier's automation fires immediately, with no human check. If a rule triggers a template deletion or asset transfer, it's done, right or wrong. Rills inserts a mandatory approval step you handle from your phone. AI proposes the action, but you decide. It's the difference between a script that might delete tomorrow's campaign and a teammate who always asks first.
Why use Rills instead of Make for Shotstack workflows?
Make runs your scenario automatically, which is fine until it deletes the template you were about to reuse. Rills builds the same logic but adds a mobile approval gate. The AI learns your patterns and confidence scoring suggests which actions you can let through unsupervised, but you set the threshold. You keep the veto without babysitting a dashboard.
Does Rills support Shotstack webhooks for render completion?
Rills can ingest Shotstack's render callback data and turn it into a proposed action. For example, when a render finishes, Rills might propose transferring the asset or updating a database. But before anything ships, you get a notification. You approve the transfer from your phone. The webhook isn't just a trigger; it's a draft you review.
Can Rills schedule Shotstack actions like deleting old media weekly?
You can set Rills to periodically check for old ingested media or unused templates. It will propose a cleanup list, but nothing gets deleted automatically. You receive a mobile approval request with the items. You pick which to delete and which to keep. The schedule runs the check, not the execution. You always hold the final say.
How much does Rills cost for Shotstack automation?
The approval queue and all workflow logic are free. You only pay when Rills performs a real action: an AI call to decide what to do, or an external API call to delete a template, transfer an asset, or fetch a status. If you just review proposals and reject them, it costs nothing. You're not charged for thinking twice.