Event Hooks Feature Request

Following some recent discussion on the Perchology Slack channel. I’ve been encouraged to re-submit some requests for Event Hooks. They have been mentioned in the forum previously but perhaps not in the feature request channel.

1. An event hook that fires when a Runway backup task has completed.

At present Runway backup “fails silently” in that if you don’t actively go and look at the results you don’t know you have got problems. This hook will allow app developers to implement notification functionality (email, Pushover, PageDuty, etc).

1. An event hook that fires when a form has been processed.

A typical use would be to add tasks/contacts/etc to CRM systems and alike. Although Forms can be submitted to multiple apps this is effectively a parallel operation and what is needed is a sequence so that only form submissions that have passed spam checking etc are processed further. I guess there is a question about this hook being before or after email. My preference is before but it’s not a show stopper either way.

1. An event hook that fires when a user login been completed

The most important use of this would be to allow second factor authentication which is becoming more important and common. Would also be useful for audit purposes and for providing information on login about recent changes.