Overview
Emails can trigger the execution of a playbook.
Emails are received on a unique email address based on the playbook you want to trigger.
Email triggers are active by default on any playbook.
Email content is entirely decoded, including headers, so that you can explore, inject, and process email data in the playbook steps.
Emails sender are checked against an allowlist configured at tenant onboarding.
Guide
An email address is automatically generated for each playbook:
It is based on the identifier of the playbook that you can pick in the URL (it’ll be soon available in playbook properties).
The syntax is:
<playbook_id>@emailhook-<tenant_id>.mindflow.devEx:
7407494d-2da2-4c3f-b979-97df826d173a@emailhook-customer.mindflow.dev
You can send emails to this address and the playbook will be executed for each one.
When emails are received to this email address, the data of the emails are available in the data picker. You can pick any of this data and inject them for further processing.
Known limitations
These are limitations that may be addressed in the future:
Attachments are analyzed but files cannot be extracted and processed.
The email address does not appear in the Playbook inspector at this time.
Read more here.