Gmail package updates

Review the updates in released versions of the Gmail package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.

Versions summary

The following table lists the versions of Gmail package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.

Version Release date Release type Bot Agent version Control Room build
1.0.2 8 June 2026 Package-only; post Automation 360 v.40 release 22.240.34 or later 45892 or later
Note:
  • To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:

    https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar

  • For Gmail package, the naming convention is: bot-command-gmail-<version.number>.jar

    For example, bot-command-gmail-1.0.0.jar

For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room.

1.0.2

  • Compatible Bot Agent version: 22.240.34 or later
  • Compatible Control Room version: 45892 or later
Whats new
Introducing the Gmail package
This release introduces the Gmail package that enables you to automate various tasks in your Gmail mailbox. This package has the following actions:
Introducing the Check if label exists condition

Check if label exists condition is now available in the If package that you can use to verify specific labels in your Gmail mailbox.

If package | Check if label exists
Limitations

When you use the Save email action within Gmail iterator and the target file is open, the action does not encounter an error if the Overwrite option is selected. As a result, the action might not complete as expected, and no error is surfaced to indicate the conflict.

Workaround: Ensure that the target file is closed before running automations that use the Save email action with the Overwrite option enabled.
When you use the Save email action within Gmail iterator to save an email in which the subject contains a period (.) character, the action displays an error and the email is not saved.

Workaround: Before saving, modify the email subject or specify a custom file name that does not include a period.

When you use the Move email action within Gmail iterator with a valid source label and a non-existent destination label, the action completes without any error to indicate that the destination label is invalid.

Workaround: Before running the Move email action, verify that the destination label exists in the Gmail account.
In the Move email action, the help text for the Source labels field does not indicate that semicolons are also supported as a separator between multiple labels.

Workaround: When specifying multiple source labels, you can use either a comma (,) or a semicolon (;) as the separator.
When you use a filter condition in the Gmail package, emails that should match the filter are not processed, and their status is not updated.

Workaround: Use the full or exact value of the field in the filter condition instead of a partial sub-string.
When you use an action to change the status of an email within Gmail iterator, the status of the email does not update in the Gmail account.

Workaround: Perform the status change outside the Gmail iterator by retrieving the relevant email identifiers within the loop and then apply the status change in a separate action after the loop completes.
When you use the Reply action with an invalid recipient email address, the action fails with a session-related error message that does not accurately reflect the cause of the failure.

Workaround: Validate recipient email addresses before passing them to the Reply action.
In the Reply action, if you specify a non-existent file as an attachment, the action fails with a session-related error message that does not accurately reflect the cause of the failure.

Workaround: Verify that the attachment file exists before passing it to the Reply action.
When you use the Reply action within a Gmail iterator and provide multiple labels as input, the action does not send the reply to the recipient list.

Workaround: Use a single label per iteration when configuring the Reply action within a Gmail iterator.