Back Office BeatSubscribe

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

From the brief of Thursday, October 15, 2026 · No. 6

From the daily brief · Automation

Zapier's Zoom Team Chat connections failed for 14 hours on Oct. 14; check held Zaps

If your Zaps post job alerts or updates into Zoom Team Chat, some runs failed or were held on Oct. 14, and a few connections still need a manual fix.

By Carter Josephson · · 2 min read

What happened

Zapier reported on Oct. 14, 2026, that Zoom Team Chat connections were failing authentication, which blocked new connections and caused Zaps using existing connections to fail or be held; Zapier said other Zoom integrations were not affected. The incident was first posted at 8:21 a.m. and marked resolved at 10:28 p.m. UTC, with Zapier saying existing connections are refreshing automatically but a small number may need to be reconnected manually.

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

This only matters if you have Zaps that send to or read from Zoom Team Chat. Zoom Meetings and other Zoom apps were not affected. The window ran about 14 hours, from 2:21 a.m. to 4:28 p.m. Mountain time, so it covered a full workday in the U.S. Take an 18-person electrical contractor that sends each new web-form job request into a Zoom Team Chat dispatch channel, about 25 a day. If 15 of those landed during the outage, the dispatcher never saw them in chat. The form data still exists, but the alert failed or is sitting in a held run. If one of those was a $600 service call that went to a competitor, the outage cost more than the Zapier plan does in a month. The fix is small: open Zap history, filter for held and errored runs on Oct. 14, replay them or handle them by hand, and confirm the Zoom Team Chat connection shows as working. If you do not use Zoom Team Chat in any Zap, ignore this.

What to do
Try it

This week, have whoever owns your Zapier account filter Zap history for held or errored Zoom Team Chat runs on Oct. 14, replay or manually handle each one, and reconnect any Zoom Team Chat connection that still shows an error.

What it costs
What it costs
Checking Zap history and replaying held runs
0.5 hr (≈ $25 at $50/hr)
Reconnecting a Zoom Team Chat connection that did not refresh
10 min per connection
One missed $600 service-call lead (assumption)
$600
Change to Zapier plan or pricing
$0
Doing nothing
$0 if you do not use Zoom Team Chat in Zaps; otherwise Oct. 14 alerts stay unsent and a broken connection keeps failing silently
Sources
status.zapier.com (primary) · Zapier support: get help

Questions owners ask

Were Zoom Meetings or other Zoom Zaps affected?

No. Zapier said only Zoom Team Chat connections had authentication failures and other Zoom integrations were unaffected.

Do I need to reconnect Zoom Team Chat?

Usually not. Zapier said most connections refresh automatically, but a small number may need a manual reconnect. Check the connection's status in your Zapier account and reconnect it if it shows an error.

Will held Zaps run on their own now that it is fixed?

Do not assume so. Zapier's notice says connections are recovering, not that held runs were replayed. Check Zap history for Oct. 14 and replay or handle each held or errored run yourself.

Three to five of these, every weekday morning.

Related