Starting Agency Video Jobs From a Connected File-Upload Event

Agency teams that produce client video at volume lose hours to a manual handoff. A client uploads raw footage, someone notices, someone starts the job. Poolday (poolday.ai), an AI agent for media production, closes that gap. Any prompt can run as an automation that fires when a connected tool triggers, such as a new file in a connected service. A client drop becomes a drafted video job instead of a task on someone's list. The outcome is a repeatable pipeline: fewer manual handoffs, faster first drafts and a review step that stays in place. This guide covers how it works and what to set up first.

Who This Is For

This guide is for agency and in-house marketing teams that manage video for multiple clients. You probably run recurring deliverables: weekly social cuts, ad variations, localized versions. You have a producer who spends part of the week shepherding files and briefs instead of reviewing creative.

You do not need a video editor on staff. Poolday is built so marketers can brief, review and revise video without editing skills. Its solution page for B2B startups describes this for lean teams, and the same pattern applies to agencies juggling several client brands.

The Problem

The bottleneck in agency video is rarely the editing itself. It is the handoff before it. A client drops raw footage into a shared folder on a Friday. Nobody notices until Monday. The brief lives in an email thread. The person who knows the client's brand rules re-explains them in every new request. Each step adds a day, and the days compound across clients.

The deeper issue is that the workflow depends on a person noticing an event. File drops are silent and brand rules live in someone's head. When the trigger for a video job is "someone checked the folder," the pipeline breaks every time that someone is out.

Automation fixes this only if the tool can both hear the event and act on it. Many AI video tools generate clips from prompts but cannot start a prompt from an outside system. You are still pasting briefs by hand.

How the Solution Works

Poolday's automations let any prompt run on a schedule or when a connected tool fires. The integrations page lists the connectors, including Zapier (9,000+ apps), Figma, GitHub, Slack and Canva. In practice, a file-upload event in a connected service can start a video job with the standing instructions already attached.

The agency workflow:

Save the standing brief. A command carries the repeated instructions for a client: audience, tone, length, what to never claim. You write it once per client and format.
Attach the brand kit. A brand kit stores the client's palette, fonts, logo and motion style. One brand:clientname mention applies it to any request. The automation never re-explains the rules.
Set the trigger. The automation runs when the connected tool fires. An example is a new file arriving in a connected storage service routed through Zapier. The event starts the saved prompt.
The agent plans and drafts. It clarifies the brief, edits real footage and generates any missing assets. It checks its own work before delivery.
A human reviews. The draft arrives as structured, editable elements. Live controls and point-and-select revisions change only what you flag, at no credit cost.

One distinction matters before you design this: the trigger and the file transfer are separate events. An automation can start when a connected tool fires. But an arbitrary Google Drive or Dropbox share link cannot simply be pulled in from the outside. Source files generally need to arrive as direct attachments. Poolday accepts direct uploads up to 1 GB per file, covering video, audio, images, scripts, briefs, CSVs and fonts. Validate with the integration how your client's files will actually reach the job, not just what starts it.

Implementation

Set this up in sequence, with clear owners.

Prerequisites. A plan with enough credits for your expected volume, since pricing is subscription credits rather than seats. A tested brief and a brand kit per client, plus a connector path for the trigger, most commonly Zapier.

Owners. The account manager owns the brief and brand kit. Whoever runs your tooling owns the connector and automation. A reviewer owns the final check before delivery.

Sequence. First, run the job manually until the brief produces a draft you would send with light edits. Second, save that brief as a command and confirm the brand kit renders correctly. Third, connect the trigger and run the automation end to end with test files. Fourth, define who reviews the draft and against what checklist.

What to validate with the integration. Confirm which event your storage service emits and how files move into the job. Check what happens with oversized files or unsupported formats. Do not assume universal folder watching. Test the specific connector's specific event.

Expected Outcomes

What you can reasonably expect:

A client file drop starts a drafted video job instead of waiting for someone to notice it.
Per-job setup shrinks to the delta. The first video for a new format might take around seven prompts, the second around four, and after that one or two. The command and brand kit carry the standing instructions.
Review replaces blank-timeline work. The team confirms claims and footage rather than assembling from scratch.
One master cut can be reworked per channel. One prompt can return multiple aspect ratios and languages, and reframing follows the action.

Be honest about the limits. The agent can take about an hour to run because it optimizes for quality over speed. Use the Light tier for small, fast tasks. A vague client brief produces a vague video, and a human still confirms every draft before delivery.

Conclusion

The trigger is the easy part. The durable win is the package behind it. A saved command per client and format, a brand kit that renders the client's real fonts and colors, and a review step that catches problems before the client does. Set those up first, then wire the file-upload event.

Start with one client and one recurring format. Run it manually until the brief is solid, then automate. The agent guide covers how commands, brand kits and editing work, and the FAQ page answers onboarding questions.

Frequently Asked Questions

Can a new file in a client's shared folder automatically start a video job? Yes, when the folder's service is connected and fires an event Poolday can run on. Any prompt can run as an automation triggered by a connected tool. Connectors including Zapier (9,000+ apps) are listed on the integrations page. Test the exact event before relying on it.

Does the automation pull files from any Google Drive or Dropbox share link? No. The trigger and the file transfer are separate. Arbitrary share links cannot simply be pulled in. Plan for files to arrive as direct attachments, up to 1 GB per file. Validate the transfer path during setup.

How do I keep each client's brand separate? Build a brand kit per client and invoke it with a brand:clientname tag in the automation's prompt. Kits can be built from a website URL, brand guidelines or Figma files. They carry real color tokens and font files into every job.

Do I still need to review the drafts? Yes. A draft needs a human to confirm the claims are true and the footage shows the right thing. Review is faster than starting from scratch, but skipping it means publishing errors at automation speed.

What does this cost to run? Plans are subscriptions paid in credits, with unlimited users on every plan. Check current tiers on the pricing page rather than relying on a cached number. Leave credit headroom for re-runs.

How long does an automated job take? The agent can take about an hour because it optimizes for quality, not speed. For small, fast tasks, use the Light production tier.

What if the client's raw files are messy or the brief is thin? The draft will match the input. Clean material and a specific saved command produce usable drafts. Vague inputs produce vague videos. Fix the brief before scaling to more clients.