SharingWebhooksHow to
Slack, Teams and email digests
Send a webhook's nightly digest to a Slack or Microsoft Teams channel, or to up to 10 email addresses.
Applies toEditor license
A webhook can post to a Slack or Microsoft Teams channel, or email up to 10 people, so a team hears about changes where it already talks. For people, the nightly digest is usually the right choice: one short message after each nightly update, saying what changed in scope.
Slack#
- In Slack, create an incoming webhook for the channel you want to post to, and copy its URL. It starts
https://hooks.slack.com/services/. - In CapitolMath, start a new webhook from Integration → Webhooks — see Creating a webhook.
- Under Send to, choose Slack channel and paste the URL.
- Under Delivery, choose Nightly digest.
- Select Create webhook, then Send a test event. When it appears in the channel, select Activate.
Only a URL on hooks.slack.com is accepted for a Slack channel.
Microsoft Teams#
- In Teams, set up an incoming webhook or a Workflows flow that posts to the channel, and copy its URL.
- In CapitolMath, start a new webhook, choose Microsoft Teams channel under Send to, and paste the URL.
- Choose the delivery, create the webhook, send a test, and activate it, as for Slack.
A Teams URL is accepted on webhook.office.com, logic.azure.com, powerplatform.com or outlook.office.com.
Email#
- Start a new webhook and choose Email under Send to.
- Enter up to 10 addresses, separated by commas.
- Create the webhook, send a test, and activate it once the test is sent.
Email always sends the nightly digest — one readable message a night, never one per change — whatever the plan.
What the digest says#
Each digest leads with how many changes were found in its scope overnight, then counts them by kind, with a link to open CapitolMath. In Slack it's a message; in Teams, a card with an Open in CapitolMath button; by email, a message whose subject starts "CapitolMath:" and which ends with the webhook's name.
When a night's update covers the webhook's jurisdictions but finds nothing new, the digest still arrives and says Nothing changed in scope overnight. If you expected one and it didn't come, check the webhook's status in Integration → Webhooks.
Your team's tracking#
With the tracking events chosen, a channel hears about your team's work as it happens: AB 1234 for Coastal Housing: our position is now Oppose unless amended (was Neutral), AB 1234: now owned by Maria Lopez (was Steve Park), AB 1234: Maria Lopez added a note. A note's text never leaves CapitolMath, so the message links to the bill instead. By email, and on the digest, they're counted in the next digest. See Our tracking.
Each change, in a channel#
On a plan that includes per-change events, a Slack or Teams webhook can post every change as its own message. The builder's estimate shows how many that would have been over the last 30 days, and warns when it's more than a channel of people will read. A narrower saved view keeps it manageable.