Introducing no match branch for trigger actions

Actions
William Tabi
Eoghan Reid

We introduced a secondary path for trigger actions, no match. This secondary path will trigger when the events do not match the trigger criteria.

This makes managing powerful If/Else or Match/No match flows far more intuitive by removing the need to manually create duplicate inverse trigger actions.

Review the docs to learn more.

William Tabi
Eoghan Reid

More "Actions" updates

Other recent updates

Built by you,
powered by Tines

Already have an account? Log in.

Introducing `no match` branch for trigger actions | What's new at Tines