Many modern apps and services provide webhooks1 for real-time “push notifications” about events. These notifications are usually simple HTTP POSTs2 with either request parameters or JSON/XML payloads that are sent to a URL you provide. This is in contrast to the less efficient “pull” approach, where a service is constantly polled at regular intervals to check for new changes.
With Cerb’s webhooks plugin you can build powerful automation behaviors in response to webhooks, entirely from your web browser, and without writing custom code or plugins. Each webhook listener is given a unique URL that is assigned to a specific bot behavior. With that URL in hand, you can simply paste it into the appropriate field in whatever service you’re integrating with. By default, these URLs don’t require authentication, but you can enforce any authentication method you need within the bot behavior.
Here are some common webhook integrations:
- Amazon CloudWatch
- Send alerts to a Slack room when any metric or log conditions are met. For instance: HTTP 5XX errors, consecutive failed password attempts, SSH sessions, etc.
- Send invoice and payment notifications to a Slack room.
- Send issue and commit notifications to a Slack room.
- Send @mentions to a Cerb bot.
- Send notifications about new/resolved issues to a Slack room.
- Send notifications about bounced or dropped messages to a Slack room along with a permalink to the ticket. The bot can also adds a sticky note to the affected messages with the specific error message; and, when appropriate, the recipient is marked as defunct.
- Correspond with a Cerb bot through mobile text messages.
- Zapier3 helps integrate hundreds of apps and services. You can use their existing ‘webhook’ action to create new webhooks that ping Cerb bots for thousands of different events. For instance, “when an RSS feed changes”, “when a new file is added to Dropbox”, “when your brand is mentioned on Twitter”, “when a new event is added to your Google Calendar”, etc.