- How to automatically send an envelope to sign through Signeasy every time an email is received in Outlook
- 1. Set the Outlook trigger as “Email received”
- 2. Add the "Send envelope to sign" step in Signeasy
- 3. Activate your playbook
- Learn more about integrating with Outlook Mail and Signeasy
- Related blog posts
- More how-to guides featuring Outlook Mail and Signeasy
How to automatically send an envelope to sign through Signeasy every time an email is received in Outlook
Set the Outlook trigger as “Email received”
Once you have finished creating your playbook, the next step would be to begin with the first action. A playbook always starts with a trigger, which is responsible for detecting changes in your connected applications and responding accordingly.
Add the Outlook trigger to initiate your playbook's actions every time an email is received. Click "Add trigger" in your playbook and choose "Email received" from the dropdown menu under Outlook. This will allow your playbook to automatically identify newly received emails and trigger necessary actions.
If you still need to connect your Outlook account to Relay.app yet, a prompt will guide you through the process.
Add the "Send envelope to sign" step in Signeasy
Integrate the Signeasy automation into your playbook to ensure the prompt sending of envelopes to sign using Signeasy every time an email is received in Outlook.
Click the "Add step" button, then locate the "Send envelope to sign" automation for Signeasy and input the mandatory and relevant details.
If your Signeasy account still needs to be connected to Relay.app, you will be prompted to complete that connection. Make sure to allow the necessary permissions for Relay.app to sync with your Signeasy account.
Activate your playbook
Activating your playbook is the last step in the process. Once you turn it on, it will automatically send an envelope to sign through Signeasy every time an email is received in Outlook without requiring manual intervention.
To activate your playbook, click the toggle button at the header. Before activating, we recommend performing a test run of your playbook to ensure all the steps work seamlessly together.