Microsoft Teams, Discord and Google Chat: Getting SCREENish Alerts
SCREENish posts the same alerts into Microsoft Teams, Discord and Google Chat as it does into Slack: someone started or stopped tracking, an activity review opened, a face check failed, the team changed, and a summary of yesterday every morning. In each case you fetch an incoming webhook URL from the chat tool and paste it into API & Integrations > Connections: webhooks and chat.
Microsoft Teams
- In Teams, open the channel's … menu and use the Workflows app with the template Post to a channel when a webhook request is received. Name it, pick the team and channel, and copy the URL the workflow gives you.
- Channels that still offer the older Incoming Webhook connector (Connectors > Incoming Webhook > Configure) work too; copy the URL it shows.
- In SCREENish choose Microsoft Teams (incoming webhook / workflow URL), label the connection, paste the URL, tick the events, press Add connection and then Test. The message arrives as a card in the channel.
Discord
- Open the channel's Edit Channel > Integrations > Webhooks > New Webhook, give it a name and an avatar if you like, and press Copy Webhook URL. It starts with
https://discord.com/api/webhooks/. - In SCREENish choose Discord (webhook URL), label it, paste the URL, tick the events, press Add connection and then Test.
Google Chat
- Open the space, use its name menu > Apps & integrations > Webhooks > Add webhook, name it and copy the URL. Incoming webhooks are a Google Workspace feature; a personal Google account does not offer them.
- In SCREENish choose Google Chat (incoming webhook URL), label it, paste the URL, tick the events, press Add connection and then Test.
The same rules in all three
- Only public
httpsdestinations are accepted, and the URL is a secret: anyone holding it can post into that channel. - Pick the events deliberately. The daily summary and activity reviews suit most teams; every 10-minute entry produces hundreds of messages a day on a team of ten.
- Deliveries shows every message SCREENish tried to send and the chat tool's answer. Failures are retried after 1, 5 and 30 minutes, then 2 and 6 hours, and abandoned after five attempts; a destination that keeps refusing is paused automatically with the reason on its row.
- Pause, Resume and Remove work as they do for any connection.
- The messages carry hours, activity counts, member and project names and verdicts — never screenshots, application names, window titles, biometric data or pay rates. Everyone who can read the channel can read all of it.
The step-by-step walkthrough with the full event list is in Slack: Getting SCREENish Alerts in a Channel; everything there applies here too.