Automations

Configure event-triggered roster reviews

Run relevant reviews when verified business data changes.

Desktop · Free / Pro · Owner

Before you begin

Sign in to Eva and select the intended project.
Use fictional records when practising; changes affect the selected business.

Starting screen: /dashboard/roster

1. Choose a responsibility

Action: Choose a responsibility. Select the image to enlarge it.

Open an existing task preview and select Edit roster task, or create a task with a suitable recipe.

Expected result: The task editor displays its recipe and delivery policy.

Confirm it worked: Confirm the intended agent and channel.

Result: Choose a responsibility. Select the image to enlarge it.

2. Enable relevant data changes

Action: Enable relevant data changes. Select the image to enlarge it.

Set Run when relevant data changes when supported by the selected recipe. Review the immediate/digest option shown.

Expected result: The task becomes eligible for its supported verified data-change triggers.

Confirm it worked: This does not turn every project event into a write permission.

Result: Enable relevant data changes. Select the image to enlarge it.

3. Set recipient and action policy

Action: Set recipient and action policy. Select the image to enlarge it.

Review the Channel and Agent selectors and the task’s Email notifications choices. For mailbox automation, also use Inbox’s auto-reply settings.

Expected result: The task has an explicit destination and notification policy.

Confirm it worked: Confirm recipients and avoid unnecessary notifications.

Result: Set recipient and action policy. Select the image to enlarge it.

4. Save and inspect history

Action: Save and inspect history. Select the image to enlarge it.

Click Save task. Later open Open roster history to inspect an admitted review.

Expected result: Saved triggers are used for subsequent relevant changes.

Confirm it worked: Check the recorded trigger/result rather than assuming an old historical event will replay.

Result: Save and inspect history. Select the image to enlarge it.

Troubleshooting and alternatives

Initial sync, historical changes and self-generated loops are suppressed where specified by the automation boundary. Only verified relevant changes admit work.

If no result appears, check Enabled, recipe relevance, active project and dispatcher state. Do not produce repeated live external events just to test a guide.