In this release, we are adding a large number of improvements and new features to hooks, our automations engine.
Send mail improvements
The send mail action now supports multiple recipients as well as CC and BCC recipients
Hook record triggers
Entity event triggers in hooks have been enhanced and now support selecting individual records as well. Hooks can thus now target individual records and also only be executed when a record is updated or selected.
Publishable hook actions
Hook actions can now be activated and deactivated, making changes to hooks easier and allowing for easier debugging and analysis of hook execution
Batch persistence settings
Instead of always keeping the batch logs of an executed hooks, batch persistence can now be configured such that only successful or failed hook executions are kept in the logs. Additionally, the stop action can now also delete a batch log manually.
Trigger hook action
With the new trigger hook action, other hooks can be triggered from within a hook execution. This allows for complex hook structure with reusable child hooks to be created and supports de-duplication of code.
Synchronous hooks
By default, all hooks are executed in the background for performance reasons. We have now added synchronous hooks that are executed directly when they are triggered, allowing the executor to directly get the result of the hook. This is supported for both hooks triggered from web events as well as for hooks triggered by other hooks.
HTTP response action
We have added a new HTTP response action. When used together with synchronous hooks and web event triggers, this allows for a customized response to be sent. Using this mechanism, it's possible to create fully customized APIs utilizing all of the power of the hooks automations engine.
Delete record action
A new action was added that supports deleting records directly from hooks, eliminating the necessity to use API calls from within a hook
Entity and ID sources
The Update Record and the new Delete Record actions have been improved to now also support directly specifying an entity and record ID, so that records can be modified or deleted directly, removing the requirement to fetch a record first using the Retrieve Records action.
Hook categories
Categories have been added to hooks. This allows hooks to be categorized and filtered using the new categories. Additionally, the new categories view can be used to directly show hooks by category in a hierarchical manner.
Web event trigger improvements
Hooks triggered by a web event will now also receive the user that triggered the event when they are logged in, allowing user-specific frontend hooks to be implemented.
Loops improvements
Loops in hooks now also support data from SiteData to directly be selected and act as source for a loop. Any JSON data containing an array in SiteData is supported. Additionally, loop elements as entity records can now also be added directly using the loop helper, removing the requirement to fetch the records first using a Retrieve Records action.
Duplicate hook
We have added an often requested feature for duplicating a hook including all of the contained actions directly in the admin panel
Merge files action
A new action was added that allows merging multiple files together to a new output file. This way, larger output CSV files or similar can be generated easily.
Custom entities in hooks
Any custom entities created by users are now also supported in hooks. This includes the hooks entity events, but also the actions for retrieving, creating, updating and deleting records.
Custom Pre-Event properties
For hooks triggered on entity events, the event is already executed once the hook is run. This means the data of a deleted record was no longer available. With pre-event properties, it is now possible to define for Update and Delete events, which data should be passed to the event before the action is executed. This way, access to old or deleted data is still possible from within a hook.