Using Connect action in Email package
- Updated: 2023/12/11
Using Connect action in Email package
Use the Connect action in the Email package to establish a connection with an email server. This is the first action you must use to automate an email-related task.
Prerequisites
- Outlook/Office 365
- If you use Client credentials flow authentication
mode, then perform the following steps:
- Log in to the Microsoft Azure portal.
- Register an application with the Microsoft identity platform to obtain the client ID and tenant ID. See Register an application.
- Add a Client secret.
- Based on the mail server you connect to, perform the relevant steps:
- IMAP/POP3
Add the POP and IMAP permissions to your AAD application . See Authenticate an IMAP, POP or SMTP connection using OAuth.
- EWS
- Configure for app-only authentication. See Configure for app-only authentication.
- Configure an application access policy and limit the scope of application permissions. See Configure application access policy.
- IMAP/POP3
- If you use the Authorization code with PKCE
authentication mode, then perform the following steps:
- Log in to the Microsoft Azure portal.
- Register an application with the Microsoft identity platform to obtain the client ID and tenant ID. See Register an application.
- When registering the application, set the redirect URI to
http://localhost:9999/callback
. - Add permissions with type delegated for IMAP, POP3, and SMTP and grant the application the required permission for Microsoft Graph to the application.
The videos in the following playlist provides information about configuring and using OAuth 2.0 authentication in the Email Connect action:
Note: If the mailbox is used inside a Loop action, ensure that you register the user who is assigned to perform the automation. For more information , see Manage users and groups assignment to an application. - If you use Client credentials flow authentication
mode, then perform the following steps:
- Gmail
To authorize your application with Gmail using the Authorization code with PKCE authentication method, perform the following steps:
- Configure the OAuth 2.0 settings in the Google Cloud Platform (GCP) and retrieve the necessary credentials to connect Automation 360 with your G Suite applications.
- Ensure you create a project.
See create a project.
- Generate the Client ID and Client secret.
See Setting up OAuth 2.0.
Note:- Select the Web application option.
- Add this authorized redirect URI:
http://localhost:8888/Callback
.
- Complete the steps to set up user consent for the username that you will use to connect to the Automation 360.
Note:- Client Credentials flow does not support Gmail.
- The Client Credentials and Authorization code with PKCE authentication modes do not support Yahoo and MSN mail servers.
Multi-factor authentication for Azure EWS (A-people login required)
This action enables you to provide the email server credentials and details, and associate this information with a session name. Use this same session name for the other Email actions, so you only have to provide the server information once.
Procedure
To establish a connection with an email server, follow these steps: