Skip to main content
You can post a board’s activity to your team’s Google Chat space or Slack channel. Email notifications go to each person, but these go to one shared place, which makes it easy for the team to follow what’s happening. You can set a destination per board, for the whole team (every board), or both. Who can do this: Owner, Manager

​
What gets posted

You choose what to send for each service. Everything is on at first. Each post includes the board name and a link to the card. Activity on template cards isn’t sent. Posts follow the board’s settings, not each person’s notification settings.
Everyone in the space or channel can read the posts, even if they aren’t ZARMS members. Before posting to a place with people outside your company, check that it’s fine for them to see card names.

​
Get an incoming webhook URL

First, create an incoming webhook where you want to post, and copy its URL.
1

Open the space

In Google Chat, open the space you want to post to.
2

Add a webhook

Click the space name, choose Apps & integrations, then Add webhooks. Enter a name (for example, ZARMS) and save.
3

Copy the URL

Copy the webhook’s URL (it starts with https://chat.googleapis.com/v1/spaces/).
If you can’t add a webhook to the space, check with your Google Workspace admin. For details, see Google’s guide.

​
Set it on the board

1

Open the board settings

On the board screen, click the board name or description at the top to open Board settings.
2

Open the Notifications tab

Select the Notifications tab. Only Owners and Managers see this tab.
3

Paste the URL

In Notify Google Chat and Slack, paste the URL into Incoming webhook URL for the service you use.
4

Choose what to send and save

Under What to send, turn off anything you don’t need, then press that service’s Save. This section takes effect right away, without waiting for Save changes in Board settings.
5

Check it with a test

Press Send test. A post saying “This is a test from ZARMS.” arrives. If it does, you’re done.
You can set one Google Chat and one Slack destination per board. After you save a URL, only part of it is shown. To change it, enter the new one in New URL (only to change it).

​
Post activity from every board to one place

A team-wide destination receives activity from every board, including boards created later.
1

Open team settings

In the admin console, open the Team settings tab and go to Chat notifications (Google Chat, Slack).
2

Paste the URL and save

Under Team-wide notifications, paste the URL into Incoming webhook URL for the service you use, choose What to send, and press Save.
3

Check it with a test

Press Send test. A post saying “This is a test from ZARMS.” arrives.
If both a team-wide and a board destination are set, that board’s activity is posted to both. If both point to the same space or channel, the same post arrives twice. When a team-wide destination exists, the Notifications tab in Board settings says so.

​
Stop posting

In the section where you set it (the Notifications tab in Board settings, or Team-wide notifications in team settings), press Remove for that service. The saved URL is deleted and cannot be restored. To post again, paste a URL again.

​
Turn off chat notifications for the team

In team settings, under Chat notifications (Google Chat, Slack), clear Allow incoming webhooks for Google Chat and Slack notifications and save. Chat notifications stop for the whole team.
  • No one can add a board or team-wide destination, and tests can’t be sent.
  • Saved destinations stop receiving posts.
  • Saved URLs are kept. Turn the setting back on and posts resume.
If your company doesn’t use chat notifications, turning this off prevents posts from going to a space shared with outside people by mistake.

​
Troubleshooting

  • The section doesn’t appear: Only Owners and Managers can set it. It doesn’t appear for other roles. It can’t be set on My Board.
  • You see “Chat notifications are turned off in team settings”: Chat notifications are turned off for the team. To use them, turn the setting in “Turn off chat notifications for the team” above back on.
  • You see an error saying it isn’t an incoming webhook URL: Paste the URL exactly as you copied it from the service, without trimming anything. Only URLs in the forms above can be saved.
  • The test fails: Check that the webhook wasn’t removed from the space or channel. Create a new URL and enter it again.
  • Posts stopped arriving: If the section shows “Could not send” with a reason, posts aren’t getting through. ZARMS retries temporary failures later. If it keeps happening, create a new URL.
Last modified on November 4, 2026