cloud-event 1.1.2

Subscribe to Cloud Events webhook subscriptions (such as from Azure EventGrid) and report them to a chat room.


Subscribe to events in your cloud infrastructure such as deployment slot failover!

It's helpful to know when important events happen in your cloud infrastructure. The cloud-event skill can help. It allows you to subscribe to cloud events and report them into chat. It is capable of supporting events in all cloud providers, but currently only has built in support for Azure App Service events.

For example, suppose you use Blue Green deployments using Slots in Azure. You can subscribe to slot swaps to know when your deployments succeed or fail.

Subscribing to events is pretty easy. I posted a video walkthrough on YouTube or you can follow the instructions below.

  1. First, install and save the skill!
  2. Then, attach the skill to a chat channel. For example, in our #ops room I ran the command: @abbot attach cloud-event.
  3. When you attach the skill, it'll give you a URL to grab the HTTP Trigger URL. You'll need this in a moment.
  4. Go to Azure Event Grid Subscriptions in the Azure Portal and create a new subscription.
    1. For the "Event Schema" choose "Cloud Event Schema 1.0".
    2. For the "Topic Types" choose "App Services."
    3. For "Endpoint Type" choose "Web Hook" and supply the HTTP Trigger URL for the skill you created when you attached the skill.

And that's it! Now when the events you subscribed to occur, you'll get a notification in chat.

This skill supports the Cloud Events WebHook Spec v1.0. for subscribing to cloud events so it can be adapted to any cloud hosting provider. Over time I plan to add support for all kinds of events.


Run @abbot attach cloud-event in the chat room that should receive these events, then supply the trigger URL as the webhook URL to the event source.

The following commands work in chat:

* @abbot cloud-event list - List all the trigger URLs used as webhooks.
* @abbot cloud-event list {triggerUrl} - lists the allowed origins for the specified trigger URL. Instead of the URL, you can specify the number of the trigger URL in the list ex. @abbot list 2.
* @abbot cloud-event remove {triggerUrl} - removes all allowed origins for that trigger URL. No webhook requests at that URL will be accepted. You can specify the number of the trigger to remove as well: @abbot remove 2.
* @abbot cloud-event remove {triggerUrl} {origin} - removes the specific allowed origin for the trigger URL. You can specify the order of the trigger instead of the trigger URL. Ex. @abbot cloud-event remove 2 removes from the allowed origin for the second trigger.


Version History

Version Installs Created Author Release Notes
1.1.2 0 5/4/2021
Phil Haack
  • Remove the custom trigger logging. Abbot now has first-class support for trigger logging!
1.0.2 0 3/4/2021
Phil Haack

No code changes. Updated a couple of comments to clarify why the code does some odd things.

1.0.1 0 3/4/2021
Phil Haack

Fixed a bug when listing the list of triggers with active web hook subscriptions.

1.0.0 1 3/4/2021
Phil Haack

✨ This is the initial version of the cloud-event skill. It supports AppService SlotSwap and AppUpdated events. More events to come in the future.


  • by Serious Business
  • last updated by
  • 1 total install
  • MIT License
Log In or Create Account You need an account to install this package with Abbot. Signing in with Slack or Discord will create an account if you don't have one already.