Delete Attachment

The Delete Attachment action An instruction within a botflow. in a botflow Automated steps that you can design for each bot that will run. deletes an email attachment.

Using the Delete Attachment action, you can:

• Delete regularly scheduled email attachments.
• Filter attachments to collect specific information.

Some examples of using the Delete Attachments action are to:

• Delete regularly distributed information after it is sent.
• Delete account notifications.
• Set up automated email attachment processing.

Add a Delete Attachment action to a botflow

This example provides the steps necessary to add a Delete Attachment action to a botflow.

To add a Delete Attachment action to a botflow:

1. Create a Credential to use your email account authentication from within the botflow.

To create a credential:

1. Click Add Item () on the Botflow Pane.
2. Select Credential.
3. Type a Name for the credential.
4. Type a unique Username.
   Note: 

   • The username cannot match the name of any other credential in the botflow.
   • For email, the username is the email address.
5. If needed, type the value of the Password and confirm it to ensure that the correct value has been submitted.
   Note: 

   • On May 30, 2022, basic access authentication for Gmail was deprecated and less secure apps are no longer supported. If you are using App Passwords to send or get email from a Gmail inbox, those passwords will continue to work. If you want to use full OAuth authentication for additional security and standardization, you can transition to it with Nintex Bot 17.10.0 or later.

   • On December 31, 2022, basic authentication for Microsoft Exchange Online was deprecated. If you want to use full OAuth authentication for additional security and standardization, you can transition to it with Nintex Bot 17.10.0 or later.

6. (Optional) Click + (plus sign) in the Additional Fields table header to add optional fields.
   1. Type a Name for the field.
   2. Type the Value to send to the application.
   3. Click OK.
7. (Optional) Select the Never save protected values with botflow check box.

Note: In compliance with companies that have a policy against saved passwords, when selected, neither the password nor any of the Additional Field values are saved in the botflow. This option is for use in an attended bot situation where the user must first enter the password and/or Additional Field values before botflow runs, either by using the Credential Prompt action or by manually setting those values.

8. (Optional) Type a Note to document special instructions or functionality.
9. Click OK to save the credential.
2. Add an email account to your botflow.

To create an email account:

1. Click Add Item () on the Botflow Pane.
2. Click Email.
• Account
  • Letter: Displays the default connection letter A specific letter used by Nintex RPA LE to communicate with an external application when a Nintex RPA LE action runs..
  • Email: Displays the email account information created in Credentials. If more than one credential is available, select the required credential from the drop-down list.
  • Send Mail As: Type an email display name for the email From field.
  • Authentication: Select an authentication method:

    • None. Users can send, but not receive, emails.

    • OAuth2. Select if you are using full OAuth authentication for Gmail. This does not require a password for login after a token has been received from the provider. In order to receive the token, allow Google to access your Nintex RPA LE account.

    • App Pasword. This requires a SMTP password for login.

    • Basic. This requires a SMTP password for login.

  • Confirm Password: Type the email authentication password.
    Note: 

    • On May 30, 2022, basic access authentication for Gmail was deprecated and less secure apps are no longer supported. If you are using App Passwords to send or get email from a Gmail inbox, those passwords will continue to work. If you want to use full OAuth authentication for additional security and standardization, you can transition to it with Nintex Bot 17.10.0 or later.

    • On December 31, 2022, basic authentication for Microsoft Exchange Online was deprecated. If you want to use full OAuth authentication for additional security and standardization, you can transition to it with Nintex Bot 17.10.0 or later.

  • Purpose: Select to:
    • Send & Receive: Both the Send Email (SMTP) settings and the Receive Email (IMAP) settings must be configured.
    • Send only: Only the Send Email (SMTP) settings must be configured.
    • Receive only: Only Receive Email (IMAP) settings must be configured.
  • Test Connection: Click to validate the email account information. If the test is successful, a test email is sent to the email address provided in the Email field.
    
• Send Email (SMTP)
  • Server: Type the SMTP server name or IP address.
  • Port: Type the required port number.
  • SSL: Select Yes to send email using SSL.
• Receive Email (IMAP)
  • Server: Type the IMAP Server name or IP address.
  • Port: Type the required port number.
  • SSL: Select Yes to receive email using SSL.
Note: 

 

If you are using full OAuth authentication for Gmail, you must enable IMAP access. In the Gmail account Settings, go to Settings > Forwarding and POP/IMAP > IMAP access > Enable IMAP. Nintex Bot uses the following Gmail OAuth authentication server settings:

SMTP server settings

Server: smtp.gmail.com

Port: 587

Authentication: TLS/STARTTLS

 

IMAP server settings

Server: imap.gmail.com

Port: 993

Authentication: SslOnConnect


3. On the Actions list, click Email and then click Delete Attachment from the Attachments list.

The Delete Attachment Action Builder window displays.

There are no Delete Attachment settings.

4. If needed, adjust the Rule settings to modify how Nintex Bot finds the application target.
5. If needed, adjust the Run Error Task settings to fine tune how the action runs.

6. View the action Details settings.
7. If needed, adjust the Run Switch setting to create the action without running it.
8. Optionally, add an action note.
9. Click OK to add the Delete Attachment action to the botflow.

Email Preferences

If you will be using your account to routinely send email, consider using Account Preferences to store your Email Preferences.

1. Click Account from the Nintex RPA LE Menu Bar.
2. Click Preferences in the Account Panel.

The Preferences window displays.

3. Click Email.

The Email configurable fields display.

Account

• Authentication: Defaults to Yes and requires SMTP Password for login.
• Email: Type the email address. This address displays in the email From field.
• Send Mail As: Type an email display name for the email From field.
• Password: Enter the email authentication password.
  Note: 

  • On May 30, 2022, basic access authentication for Gmail was deprecated and less secure apps are no longer supported. If you are using App Passwords to send or get email from a Gmail inbox, those passwords will continue to work. If you want to use full OAuth authentication for additional security and standardization, you can transition to it with Nintex Bot 17.10.0 or later.

  • On December 31, 2022, basic authentication for Microsoft Exchange Online was deprecated. If you want to use full OAuth authentication for additional security and standardization, you can transition to it with Nintex Bot 17.10.0 or later.

• Purpose: Defaults to Send and Receive. Select to Send only or Receive only, if required.

Send Email (SMTP)

• Server: Type the SMTP Server name or IP address.
• Port: Defaults to 25. Type a different port number, if required.
• SSL: Defaults to No. Select Yes to send email using SSL.

Receive Email (IMAP)

• Server: Type the IMAP server name or IP address.
• Port: Defaults to 993. Type a different port number if required.
• SSL: Defaults to Yes. Select No if receiving email using SSL is not required.
Note: 

If you are using full OAuth authentication for Gmail, you must enable IMAP access. In the Gmail account Settings, go to Settings > Forwarding and POP/IMAP > IMAP access > Enable IMAP. Nintex Bot uses the following Gmail OAuth authentication server settings:

SMTP server settings

smtp.gmail.com

Port: 587

Authentication: TLS/STARTTLS

 

IMAP server settings

Server: imap.gmail.com

Port: 993

Authentication: SslOnConnect


4. Click OK to save the changes.

Delete Attachment Action Builder field and button descriptions

Field or button	Description
Rules	Click Rules from the Action Builder Provides access to the tools needed to add and modify actions or instructions within a botflow. Located on the left side of the Nintex Bot window. window to adjust the Connection Letter. Click the Connection Letter to select another email account. Click to select All Email or Current Email. Note: Selecting Current Email requires that the email action be inside of the Loop Email action.
Details	When directed by Nintex Support, click Details from the Preview Panel of the Action Builder. If needed, Nintex Support will supply additional information.
Run error task	Click Run error task. Open the On Error drop-down list and select the required setting: Run error task: A botflow containing an error task automatically runs the error task in the event of an error. If the botflow does not contain an error task, the botflow stops in the event of an error. Stop on error: The botflow stops in the event of an error. Ignore errors: The action is skipped in the event of an error and the botflow attempts to execute the next action. Click X to close the drop-down and save the setting.
Note	(Optional) Type a Note to document any special instructions or functionality.
Run Switch	The Run Switch toggle controls how Nintex Bot runs an action when adding or editing an action in a botflow. Run: To run the action automatically when you click OK, switch the toggle to Run. Don't Run: If you do not want to run the action automatically when you click OK, switch the toggle to Don't Run.
OK/Cancel	Click OK to save the action or click Cancel to discard the action or any changes.