Event triggers start an automation when something happens outside its schedule. Choose the trigger that matches the source of the work, and make the instructions clear about how to use the incoming information.
Outlook email
- Connect the required Outlook account through Plugins.
- Create or edit an automation and choose Outlook e-mail.
- Select the mailbox and configure the available matching conditions.
- Save the automation and test with a matching message.
If nothing runs, check the mailbox, matching conditions, connection state, and whether the automation is enabled.
Webhooks
Choose Webhook when an Aleria app or external system should send JSON to start the work. After creating the automation, copy its webhook URL from the setup.
Generated Aleria apps use app authorization. An external API-key client sends the Aleria API key in the x-api-key header and a JSON request body. Keep keys in the calling system's secret configuration rather than in public browser code.
Describe how the automation should interpret the payload and what it should do when a required field is missing. Test with representative data and inspect the resulting run before wiring it into a busy external system.
Check retries
Before retrying a failed request, inspect the run history and any external effects. Repeating an event may repeat the work.
Outlook Calendar setup for Teams capture is explained in meeting notes. See run history for inspecting outcomes.