阅读和查看 Automation Anywhere 文档

Automation Anywhere Version 11.3

关闭内容

内容

打开内容

Add email trigger

  • 已更新:2022/11/04
    • 11.3.x
    • 探索
    • Enterprise
    • 工艺流程

Add email trigger

An email trigger runs a TaskBot when an email is received in a particular email account.

Version 11.3.5If you choose the server type as the Exchange Web Services (EWS) using OAuth authentication, the Tenant ID and Client ID fields are mandatory although the interface displays these fields as optional because they can be skipped for Basic Authentication. The recommended practice is to use OAuth authentication for enhanced security.

Configure online EWS for OAuth authentication

Procedure

  1. Navigate to Tools > Trigger Manager.
    The Trigger Manager dialog box appears.
  2. Click Add.
    The Trigger dialog box appears.
  3. Specify the TaskBot you want to run in the Select Task field.
  4. Select Email Message from the Trigger Type list.
  5. For IMAP or POP3 email server:
    1. Select the IMAP or POP3 option and provide the following details:
      • Version 11.3.5.7, Version 11.3.1.13, Version 11.3.4.8 or later:
        • Auth Type: Choose from the following authentication types:
        • Host: Host name of the email server.
        • Port: Port you want to use to connect to the email server.
        • Poll every: Specify the interval in minutes after which time the system checks for new emails on the server.
        • User Name: User name you want to use to connect to the email server.
        • Client ID and Tenant ID: Enter the unique client and tenant IDs generated when you registered the application in the Microsoft Azure portal.
        • Client secret: Enter the client secret that you generated for your app in the app registration portal.
        Note:
        • The email automation created using Version 11.3.5.7 (Basic and OAuth2.0) will not work in the environments where earlier versions of Enterprise 11 (prior to Version 11.3.5.7) clients are used. However, if the bot is not modified in Version 11.3.5.7, it will continue to work in the earlier versions. Any changes to the email command fields will update the internal structure, and the bots will not work in the earlier versions after these changes.
        • As a best practice, use credential variables for the client secret, password, and other related fields to avoid storing sensitive information.

        The above points also apply to Version 11.3.1.13 and Version 11.3.4.8.

      • Prior to Version 11.3.5.7, Version 11.3.1.13, and Version 11.3.4.8:
        • Host: Host name of the email server.
        • Port: Port you want to use to connect to the email server.
        • Poll every: Specify the interval in minutes after which time the system checks for new emails on the server.
        • User Name: User name you want to use to connect to the email server.
        • Password: Password you want to use to connect to the email server.
    2. Select the Server uses secure connection option if the email account uses secured connection.
  6. Version 11.3.4 For Exchange Web Services (EWS):
    1. Select the EWS option and provide the following details:
      • Domain Name: Domain name of the EWS server.
      • Poll every: Specify the interval in minutes after which time the system checks for new emails on the server.
      • User Name: User name you want to use to connect to the email server.
      • Password: Password you want to use to connect to the email server.
      • Version 11.3.5Client ID and Tenant ID: Enter the unique client and tenant IDs generated when you registered the application in the Microsoft Azure portal. These fields are required for OAuth.
      • Exchange Version: Select an option from the list to specify the version of the EWS server you want to use.
      • Exchange Url: Specify the URL of the EWS server.

        You can click the Fetch option to populate the Exchange Url field based on the values you have provided in the User Name and Password fields.

  7. Click Save.
发送反馈