Back Office BeatSubscribe

Published by J9 Systems. What's new in business tech, and what it means for yours.

From the brief of Monday, October 12, 2026 · No. 3

From the daily brief · Automation

Google flags Zapier file storage as dangerous; Forms and Tables links blocked Oct. 9

If customers or staff open files from Zapier Forms or Tables, Chrome may show them a red 'dangerous site' page until Google clears the flag.

By Carter Josephson · · 2 min read

What happened

On Oct. 9, 2026, Zapier reported that file links on its storage domain, zapier-dev-files.s3.amazonaws.com, may be blocked or show a security warning because Google Safe Browsing has flagged the domain as a dangerous site. Zapier says Forms and Tables users are most affected and Zaps continue to run, and as of its 21:20 UTC update it was waiting for Google to confirm the issue is fixed.

What it means for a 10-to-50-person business

Most owners can ignore this. If your Zaps only move data between apps and nobody clicks a Zapier-hosted file link, nothing changes. It matters if you collect uploads through Zapier Forms or store files in Zapier Tables.

Example: a 14-person plumbing shop uses a Zapier Form for quote requests, and customers attach photos of the leak. A Zap emails the dispatcher a link to each photo. On Oct. 9 those links open to a red Chrome warning. Assume 20 requests a day and 3 minutes per request to text the customer for the photo again. That is 1 hour a day, about $35 at $35/hr. The Zap still runs and the submission is still recorded.

The bigger risk faces customers. If a Zap emails customers links to Zapier-hosted files, such as an estimate PDF, they see a 'dangerous site' warning on an email with your name on it. Zapier says server-side file access is not affected in the same way. A Zap step that copies the file to Google Drive, or attaches it directly, is a likely workaround. Do not train staff to click past the warning.

What to do
Ask your vendor

Today, open one file link from each Zap that uses Zapier Forms or Tables in Chrome and subscribe to the incident on status.zapier.com; if links still show the warning on Monday, Oct. 12, open a ticket at zapier.com/app/get-help and route files through Google Drive until it is fixed.

What it costs
What it costs
Dispatcher workaround, 20 links/day × 3 min at $35/hr
≈ $35/day
Add a 'copy file to Google Drive' step, 1 hr setup at $50/hr
≈ $50 one-time
Extra Zap step, 20 runs/day × 22 workdays
≈ 440 more tasks/mo; check your plan's task limit
Doing nothing
$0 if Google clears the flag within a day; ≈ $35 per working day it stays flagged
Sources
status.zapier.com (primary) · Google Safe Browsing site status checker

Questions owners ask

Are my Zaps broken?

No. Zapier says Zaps continue to run. The problem is opening Zapier-hosted files in a browser that enforces Google Safe Browsing, such as Chrome.

Does this mean my data was exposed?

Zapier's status page does not say why Google flagged the domain and does not report any data exposure. It says its Security team is working with Google to remove the flag.

Should staff click through the warning to get the file?

We would not make it a habit. Teaching staff to ignore browser security warnings makes them easier targets for real phishing. Copy the file to Google Drive with a Zap step, or wait for Zapier's fix.

Three to five of these, every weekday morning.

Related