Skip to main content
When an incident needs voices, WHAWIT creates the conference room for you. The Meeting action on any open incident creates a Zoom meeting or a Google Meet space on your own organization’s account, attaches the join link to the incident, and sends the link to the teammates you pick — no calendar invite, no account lookup, no copy-pasting a URL into the channel.

​
Requirements

  • A Zoom or Google Meet integration connected to the organization (setup below).
  • Meetings are created from incidents by any signed-in member who can reach the integration — there is no separate role for it.
  • Invitees must be members of the WHAWIT organization. They do not need a Zoom or Google account: WHAWIT itself emails them the join link.

​
Connect Zoom

Zoom connects with Server-to-Server OAuth credentials from your own Zoom account — no marketplace install.
1

Create the Zoom app

In the Zoom App Marketplace, build a Server-to-Server OAuth app on your account and grant it the meeting-creation scope. Copy the Account ID, Client ID and Client Secret from App Credentials.
2

Configure it in WHAWIT

In app.whawit.ai, open Integrations, find Zoom under Available Integrations — “Spin up a Zoom bridge from one or more incidents and invite the responders.” — and press Configure. Paste the three credentials.
3

Test and save

Press Test Connection — WHAWIT asks Zoom for a token with your credentials and reports exactly what Zoom answered. Save when it passes.
The credentials are stored in a secret manager, never in WHAWIT’s database. Access tokens are minted per meeting and never stored at all.

​
Connect Google Meet

Google Meet connects with OAuth — you sign in once with the Google account meetings should be created on.
1

Start the connection

In Integrations, find Google Meet and press Connect. A dialog explains what the integration enables; press Connect with Google.
2

Authorize on Google

You are redirected to Google’s authorization page. Pick the account meetings should be created on and approve the “create meetings” access WHAWIT asks for.
3

Done

You land back on the Integrations page with the connection confirmed. The integration is named after the account — Google Meet ([email protected]) — so it is clear whose account hosts the rooms.
The OAuth tokens live in a secret manager and are refreshed automatically. If a refresh ever fails — for example the Google account revoked the grant — the meeting creation says so plainly; reconnecting the integration fixes it.
If the Connect button is disabled with “OAuth is not configured on this instance”, the WHAWIT instance itself has no Google OAuth application set up — ask your WHAWIT administrator.

​
Create a bridge from an incident

1

Press Meeting

On an open incident — from its detail page action bar or its row in the incident list — press Meeting. To attach one bridge to several incidents at once, select the rows and press Meeting in the bulk action bar.
2

Pick the room and the people

The Create meeting dialog asks for the Provider (each connected Zoom and Google Meet integration is listed), an optional Topic — it defaults to the incident summary — and Invite teammates, a picker over the organization’s members.
3

Join

Creation is immediate: the dialog shows the join link with Copy join link and Join meeting buttons, and a toast offers Join as well.
What happens around it:
  • Invitees get an email from WHAWIT — Incident bridge: <topic> — with who started the bridge and the join link.
  • The incident’s Slack thread gets a reply — 📞 Bridge started by [email protected]: <topic> — with a Join meeting button, if the incident has a live Slack card.
  • The link is attached to the incident under External links, labeled Zoom or Google Meet, and the attachment lands on the incident timeline. With a multi-incident bridge, every selected incident gets the link.

​
Room behavior, by provider

Both providers are deliberately configured for zero-friction entry during an incident: no waiting room on Zoom, open access on Meet. Treat the join link like the incident itself — anyone holding it can enter the room.

​
Details worth knowing

  • The Meeting action is offered on non-terminal incidents; a resolved or closed incident does not offer it.
  • A multi-incident bridge requires all selected incidents to belong to the same organization.
  • If the provider cannot create the room — credentials revoked, provider outage — nothing is attached and the dialog reports the provider’s answer. WHAWIT never half-creates a bridge.
  • There is no automatic meeting creation: a bridge exists only when someone presses Meeting.
  • WHAWIT does not use Zoom invitees or Google Calendar events — invitations are WHAWIT emails, so responders without provider accounts are first-class.

​
Next

Slack

Where the bridge announcement lands, in the incident’s thread.

Escalation policies

Who gets paged in the first place, level by level.