Webhooks and email
Post into a chat from other tools, and have a bot told when things happen.
Incoming webhooks and email addresses post into one chat. Outgoing webhooks tell a bot when something happens in its chats.
Incoming webhooks
Create one under Chat settings → Developers. You get an address once. Treat it like a password: anyone holding it can post to that chat.
Most tools that send webhooks can post to it. To send to it from your own software, see incoming webhooks in the API reference.
Webhooks post even where only leaders can post, since a leader set them up. That makes them a good fit for announcement chats. In a repeating chat, a webhook posts to the date that’s open, and between dates its messages are refused.
Email addresses
Create one under the same section. Anything sent to that address becomes a message showing the subject, the sender and the text. Files come along as attachments, up to 10 per email. Images placed inline, such as logos in signatures, are left out.
The address is hard to guess, but it’s only as private as the people you give it to. Email senders can also be forged, so:
- A sender the receiving mail service can’t verify (DMARC didn’t pass) is labeled
(sender not verified)on the message. - Only accept email from limits an address to listed addresses or
@domains. Listed senders must also pass verification, and anything else is dropped.
At most 60 emails an hour are accepted per address. Long emails are shortened to fit in a message. In a repeating chat, email goes to the date that’s open, and between dates it’s dropped.
Outgoing webhooks
Add an address to a bot and choose its events. You get a signing secret once. The bot only hears about chats it’s in, and never about its own actions. Every event, what it carries and how to check its signature are in the API reference.
Addresses must use https and lead somewhere public. Private networks, loopback and cloud
metadata addresses are refused, both when the address is saved and each time something is sent.
An event that isn’t answered in time is retried for about three hours. After 15 events in a row fail for good, the address is paused until an admin turns it back on, and your church’s admins get an email saying so.
Recent activity shows what happened to each event, for 14 days. It never includes message content, because admins can read it and an event can come from an invite-only chat they can’t see.