Using Connect action in Email package
- 最終更新日2024/07/22
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.
前提条件
- 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:
注: メールボックスが [ループ] action内で使用される場合、オートメーションを実行するために割り当てられているユーザーを確実に登録してください。詳細については、「Manage users and groups assignment to an application」を参照してください。 - If you use Client credentials flow authentication
mode, then perform the following steps:
- Gmail
- If you use the Authorization code with PKCE
authentication mode, then 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 Google Workspace applications.
- Ensure you create a project.
See create a project.
- Generate the Client ID and Client secret. See Setting up OAuth 2.0.注:
- 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.
- If you use Control Room
managed authentication mode, then perform the following
steps:重要: Email package currently supports the Control Room managed Oauth option for the OAuth connections based on Authorization Code Flow only.
- Configure the OAuth 2.0 settings in the Google Cloud Platform (GCP) and retrieve the necessary credentials to connect Automation 360 with your Google Workspace applications.
- Ensure you create a project.
See create a project.
- Generate the Client ID and Client secret. See Setting up OAuth 2.0.注:
- Select the Web application option.
- To add the authorized redirect URI, perform the following steps:
- Log in to the Control Room as an administrator or any user with Manage connections and View connections permissions and navigate to .
- Click Create connection tab and select Custom option from the Provider type field.
- Copy the Callback URL and navigate back to the Client application page in Google Cloud Console.
- Click + ADD URI button under Authorized Redirect URIs and paste the URI in the URIs field.
- Click Create.
To learn how to create an OAuth connection in the Control Room, see OAuth 接続の作成.
- Complete the steps to set up user consent for the username that you will use to connect to the Automation 360.
- If you use the Authorization code with PKCE
authentication mode, then perform the following steps:
- 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.
手順
To establish a connection with an email server, follow these steps: