Zoom Team Chat

Zoom Team Chat isn't supported in Xyte yet. A Zoom Team Chat integration would post Xyte incident notifications to a Zoom Team Chat channel.

What you can do

1. Ask us for it. Email [email protected] and tell us you need Zoom Team Chat. Or, in the Organization portal, open Connections → Integrations, find Zoom Chat and click Contact us.
2. Try the Webhook option tab. Until a built-in integration exists, you can send Xyte incidents to Zoom Team Chat with Incidents Webhooks. The Webhook option tab has the steps.

📘

Based on the vendor's documentation. These steps follow Zoom's Incoming Webhook chatbot article. Zoom Team Chat isn't a built-in Xyte integration, and settings on the Zoom Team Chat side can differ between accounts and versions.

You can use Incidents Webhooks with Zoom's Incoming Webhook chat app to post a message in a Zoom channel whenever an incident is created, updated or closed.

• Messages, not tickets — each Xyte event posts a new message in the channel. Nothing syncs back from Zoom to Xyte.
• What you need — a Zoom account where the Incoming Webhook app can be added from the Zoom App Marketplace, a Team Chat channel to post in, and access to Settings → Integrations → Webhooks in the Xyte Organization portal.

Step 1 — Connect the Incoming Webhook app in Zoom

1. Add the Incoming Webhook app from the Zoom App Marketplace. Your Zoom admin may need to approve it.

2. In Team Chat, open the channel that should receive Xyte incidents and send:

   Text

   /inc connect xyte

3. The app replies in a 1:1 chat with an endpoint and a verification token. Copy both.

Use /inc connect as shown. A signature-based connection (/inc connect -s) needs signed requests that Xyte can't send.

📘

Keep the token secret

Anyone with the endpoint and verification token can post in this channel. Treat the token like a password.

Step 2 — Set up Incidents Webhooks in Xyte

In the Xyte Organization portal, go to Settings → Integrations → Webhooks → Incidents Webhooks.

Endpoints

1. Set Create incident URL, Update incident URL and Close incident URL to the endpoint from Step 1, with ?format=fields added at the end:

   Text

   <your endpoint>?format=fields

2. Turn on Add custom header to requests and enter:

   • Field name: Authorization
   • Field value: the verification token from Step 1, on its own (no Bearer prefix).

3. Make sure Send payload as string is off.

4. Click Update.

🚧

Turn off "Send payload as string"

The fields format expects a JSON object. With Send payload as string on, Zoom can't read the fields and the message isn't posted.

Templates

1. Open the Create template step.

2. Paste this template:

   JSON

   {
     "Event": "{change}",
     "Incident": "{title}",
     "Description": "{description}",
     "Device": "{device}",
     "Location": "{location}",
     "Priority": "{priority}",
     "Link": "{xyte_link}"
   }

3. Click Save template.

4. Paste the same template in Update template and Close template, and click Save template in each.

Each key becomes a field name in the Zoom message. {change} becomes create, update or close, so the channel shows what happened. {priority} is a number from 1 (Critical) to 5 (Planning). For the full list of placeholders you can use, see Webhooks.

Step 3 — Test and enable

1. In the Create template step, click Test create. A message should appear in the Zoom channel.
2. Open the Enable step and click Activate.

From now on, each Xyte incident event posts a message in the channel.

Limitations

• One message per event. Updates and closes post new messages; they don't edit the first one.
• One channel per connection. To post in another channel, run /inc connect there and set up a separate destination.
• No sync back to Xyte. Replies in Zoom don't reach Xyte.

Learn more

• Webhooks — every Incidents Webhooks setting, the available placeholders and what happens when a request fails.
• Zoom's Incoming Webhook chatbot — connections, tokens and message formats.

Troubleshooting

• No message in the channel — check that the URL ends with ?format=fields and that Send payload as string is off.
• 401 or other errors — Incidents Webhooks shows the error below the wizard. Click Show full error to see Zoom's response, then check that the header value is the verification token alone, with no Bearer prefix.
• Messages stopped after reconnecting — running /inc connect again issues a new token. Update the header value in Endpoints and click Update.