What’s New

1.8.0.0

We added a new option of action for when an alert is triggered: Slack. Now it’s possible to send notifications to previously registered channels — and it works for both Platform Events and Runtime Alerts.
The Credentials screen is now called Integrations. In addition to the registration of authentication info to be used in webhooks, the screen now contains the SLACK tab, where you can integrate Flexible Actions to Slack workspaces. It’s from these integrated workspaces that the notification channels are selected.
The field to insert additional custom messages has moved to a different location. Before, it was part of the EVENT stage when creating an alert and now it’s under ACTIONS. With this change, it’s now possible to customise a message for each action registered — e-mail, Slack and/or Webhook. See more about creating alerts from API Platform events here and from monitoring APIs here.
When creating an alert to monitor HTTP response status, you can now include a code family (e.g., 5xx).
Regarding alerts from API Platform events, the label "AppToken" was changed to "App" (with no modifications in how the alerts work — the object app may be monitored regarding creation, update and deletion). See more about the objects monitored here.
To make notification times clearer, the cards on the Triggered Alerts screen now specify the time zone (GMT).

We added a new option of action for when an alert is triggered: Webhooks. With them, you can send an HTTP POST request to a previously registered endpoint — and it works for both Platform Events and Runtime Alerts. This option adds to email notifications, which were already present.
- To assist the webhooks registration process, we added a new page to Flexible Actions main menu: Credentials. On it, you can register authentication information (client ID/secret) to be included in notification requests.

We implemented a wizard to make the journey of creating a new alert clearer and easier, both for Platform Events and Runtime Alerts.
- The second stage of the creation process, called Actions, was designed to support future deliveries of multiple options of actions when alerts are triggered.
We now support Cron Expressions to schedule parameter checks on Runtime Alerts.

Now you can clone an alert (on Platform Events and Runtime Alerts). This means it’s now faster to create new alerts that are similar to one that is already configured.
It’s now possible to silence notifications temporarily.
Comparing API performance with past periods is now simple and more customisable. You can delimit any time range between 1 minute and 24 hours and compare it to the last 24 hours, the same period a day before and the same period the week before.

Thanks for your feedback!

EDIT