Learn how to automate adding a shrinking border progress bar to videos using Zapier by connecting to specialized video APIs, running custom FFmpeg scripts in serverless functions, or integrating with enterprise-grade media pipelines.

How to Automate That Shrinking Border Progress Bar on Your Videos (The Zapier Problem)

I still remember the alert storm. It was 2 AM, and our social media automation pipeline, `social-media-gen-prod-01`, was throwing a fit. A simple workflow—take a video from a shared drive, slap a watermark on it, and post it—was failing spectacularly. Why? The marketing team uploaded a `.mov` file with some weird alpha channel instead of the usual `.mp4`. Our simple FFmpeg script, which we thought was bulletproof, choked on it. That night taught me a valuable lesson: video automation is a minefield of edge cases, and what seems simple, like adding a progress bar, is often where the real demons live. Someone on Reddit was struggling with this exact problem using Zapier, and it hit close to home. You think it’s a simple “step,” but you quickly realize Zapier is a conductor, not an instrument. It can’t *edit* the video itself.

The “Why”: Zapier is Glue, Not a Factory

Let’s get this straight. Zapier is brilliant at connecting APIs. It’s the universal translator for the web. When a new row appears in your Google Sheet, it can tell Slack to post a message. Simple. But when you ask it to “add a border to a video,” you’re not just passing data. You’re asking it to perform a complex, stateful, and computationally intensive task. It needs to:

• Download the video file.
• Analyze the file to get its duration, frame rate, and resolution.
• For every single frame, calculate the correct size and position of the border.
• Re-encode the entire video with the new overlay graphics.
• Upload the new video somewhere.

That’s not a job for a simple webhook. That’s a job for a specialized video processing service. Zapier’s role is to hand the video off to that service and wait for it to finish. So, the question isn’t “How can Zapier do this?” but rather “What service can I plug into Zapier to get this done?”

The Solutions: From Quick & Dirty to Production-Ready

Depending on your budget, timeline, and how much you enjoy tinkering, there are a few ways to tackle this. I’ve used all three in different contexts.

Solution 1: The Quick Fix (The Third-Party API)

This is the path of least resistance and the most “Zapier-native” way to think. You find a service whose entire business is modifying media via an API and you plug it into your Zap. Services like Creatomate, Bannerbear, or Plainly are built for this. Your Zap looks less like a single action and more like a conversation.

The Workflow:

1. Trigger: New Video File in Google Drive / Dropbox.
2. Action: Webhooks by Zapier – POST. Send the public URL of the video to your chosen video API’s endpoint (e.g., `api.creatomate.com/v1/renders`).
3. The Payload: The body of your POST request will be JSON telling the service what to do. It’s like filling out an order form.

{
  "template_id": "your-progress-bar-template-id",
  "modifications": {
    "main_video": "URL_FROM_STEP_1_TRIGGER"
  }
}

The magic happens inside their platform, where you’ve already designed a template with a dynamic border that shrinks based on video duration. The API handles all the heavy lifting of rendering. Your Zap then either waits for a webhook response from the service or polls for the result every few minutes before grabbing the final video URL to post elsewhere.

Pro Tip: This is the fastest way to get a result. You’re paying for convenience and avoiding the headache of managing your own rendering infrastructure. Perfect for marketing teams and low-code enthusiasts. The downside? It can get pricey if you’re processing thousands of videos.

Solution 2: The ‘In-House’ Fix (The Serverless Function with FFmpeg)

Okay, you don’t want to pay a subscription, and you’re not afraid to get your hands a little dirty. This is my personal favorite for custom jobs. You write your own video processing logic using the undisputed king of video manipulation, FFmpeg, and host it on a serverless platform like AWS Lambda or Google Cloud Functions.

Zapier’s job is to trigger this function. It calls an API Gateway endpoint, passing the video URL. The Lambda function then spins up, downloads the file, runs the FFmpeg command, and uploads the result to an S3 bucket.

The core of this solution is the FFmpeg command itself, which is a work of art and frustration. To create a shrinking border, you’d use the `drawbox` video filter with some clever expressions.

ffmpeg -i input.mp4 -vf "drawbox=x=0:y=0:w=iw:h=10:color=red:t=fill, drawbox=x=0:y=ih-10:w=iw:h=10:color=red:t=fill, drawbox=x=0:y=0:w=10:h='if(gte(t,T/2), (T-t)*ih/(T/2), ih)':color=red:t=fill, drawbox=x=iw-10:y=0:w=10:h='if(lt(t,T/2), (T/2-t)*ih/(T/2), 0)':color=red:t=fill" -c:a copy output.mp4

Warning: The FFmpeg command above is a conceptual example for a complex effect. Getting the expressions just right for a smooth four-sided shrinking border is non-trivial and requires a lot of trial and error. You’re trading money for time and complexity here. You own the code, but you also own the bugs at 2 AM.

Solution 3: The ‘Nuclear’ Option (The Enterprise Media Pipeline)

This is for when you’re running a serious operation. We’re talking high volume, strict SLAs, and multiple output formats. Here, you use an industrial-strength service like AWS Elemental MediaConvert. This isn’t just an API; it’s an entire managed video transcoding pipeline.

In this scenario, Zapier’s role becomes incredibly simple, almost laughably so. The workflow is:

1. Trigger: New video file appears.
2. Action: Zapier’s only job is to copy that file into a specific S3 bucket, let’s call it `s3://video-ingest-prod-queue`.

That’s it. The S3 bucket is configured to automatically trigger a MediaConvert job based on a pre-defined template. That template has all the logic for your shrinking border, watermarks, format conversions, and everything else. The output is then placed in another S3 bucket, `s3://video-processed-prod-final`, which can trigger other downstream events.

This approach completely decouples your orchestration (Zapier) from your processing (AWS). It’s incredibly robust and scalable, but the setup is complex and requires deep knowledge of the cloud provider’s ecosystem. It’s overkill for 95% of use cases, but for that other 5%, it’s the only way to fly.

Comparison and My Two Cents

So which one should you choose? As always, it depends.

My advice? Start with Solution 1. Time is money. See if you can get the result you need quickly with an API service. If your volume grows to the point where the per-video cost becomes a serious line item in your budget, then invest the engineering time to build out Solution 2. It’s the sweet spot of control and cost for most small to medium-sized projects. And unless you’re building the next YouTube, you probably don’t need to even think about Solution 3.

Remember, the goal is to solve the business problem. Don’t build a nuclear reactor when all you need is a battery.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions