Administrators can now create, update, and delete triggered actions by navigating to: Settings > Developer tools > Triggered actions. They can also enable and disable triggered actions, or change the properties of the trigger or action elements to make changes in the business logic of the automation.
In previous releases, we enabled administrators to view the triggered actions that were deployed in their team and allowed them to access execution logs. We’ve expanded this functionality to allow administrators to create new triggered actions and to modify existing ones.
Of particular value to administrators is the ability to enable or disable a triggered action to start or stop automations, without the need to use developer tools or APIs. This is useful if you’re managing an integration with an external system or attempting to debug an issue with an automation.
The ability to use this functionality is controlled by the view and modify webhooks and triggered actions permissions, or can be used by any user with the Administrator role.