Skip to main content

Actions

Who can use this feature?

The main Product Owners along with the members having Admin Roles access granted.

Actions refer to the process or the result of doing something. In Engage, an action responds to a signal, which is raised when something happens, such as a donation being processed or an account or contact preference being updated. Admin users can add actions according to the user preferences.

Click on Admin in the header menu, Communication and then Actions from the side menu. On the Communication Actions screen, click the + Add Action option, and:

  1. Input the name of the action and add any notes, if required.
  2. Select the entity, the action is related to.
  3. Under Select Signals, choose the signals the action responds to.
  4. Set a Delay if the action should wait before it runs. Leave it empty to run the action straight away.
  5. Mention any conditions of the action for complex filtering.
  6. Choose any PDF document, email or SMS to be generated when the action takes place and click Save.
tip

You can also search for any action in the list via the search bar on top.

All actions appear in the form of a list.

ParametersDescription
NameName of action.
SignalsThe signals the action responds to.
DelayHow long the action waits after a signal before it runs.
Updated AtDate and time the action was updated.
DispatchesAny document (PDF, email or SMS) dispatched when the action takes place.
NotesAny notes added.

Delaying an action​

By default an action runs as soon as one of its signals is raised. Set a Delay if you would rather it waited, for example to send a reminder a day later. A delay can be anything from one hour to 30 days.

When the wait is over, Engage looks at things as they are at that moment, not as they were when the signal was raised:

  • If the action has been deleted or deactivated, or no longer uses that signal, nothing is sent.
  • The action's conditions are checked against the record as it is now. If they no longer apply, nothing is sent.
  • The message uses the action's current templates.

If the same signal is raised again for the same record while the action is waiting, only one message is sent.

Changing an action's delay applies from then on. Messages that are already waiting keep the delay they started with.