I’m trying to understand how the connections to GMail work, under the hood. In the GSuite package, the activity Get Email List has the connections already set up. How did they get there?
I do have some connections set up in Orchestrator Integration Service, is that where they come from? I don’t see GMail set up there, however. Or is there another way, that I’ve probably forgotten, that tells Studio where my Gmail can be found?
I’m trying to write a definitive guide for beginners on all this. It seems that the way to access GMail has changed over the years, because there’s a lot of outdated documentation and tutorials hanging around. One tutorial said to use app password, another said that’s the older way of doing it. One tutorial said to have 2-step verification turned off, another said it must be turned on. I realize something must be set in google to allow access, but what? If someone could point me to the latest and greatest, I’d really appreciate it.
Also, is there a difference between attended and unattended? Is there something to prevent an unattended bot from accessing GMail? Or must access always be in attended mode, so that the User must give permission each time to access the account? How do enterprise-level processes handle this?
Is the GSuite package the right one to use? There seems to be several activities in different packages, and it’s all so confusing. Are there any pros/cons to using IMAP instead?
I’m trying to understand exactly how it works, and what is the most current way to do it, so that I can explain it all to beginners.
So many questions in a single post I will try answering whatever I can
You are right, it came from Integration Service’s Connection you set up. Same connection will be available in Studio Web, UiPath Apps as well to use and automate.
We have Google Classic activities which works on Client Id and Secrete to connect with GSuite.
Follow this how to do it guide:
Here you will get latest documentation on this non integration Services way of Gmail automation.
There is no difference and it works in both the modes, attended and unattended. With both Classic and Integration Services approach, setting up the connection is one time activity.
If going with Classic approach, go with these activities
If using Integration Services, use these activities
Are there any pros/cons to using IMAP instead of GSuite activities?
Forum_Chatbot:
Based on resources from the UiPath community and documentation, here are some pros and cons of using IMAP versus GSuite activities:
IMAP
Pros:
Compatibility: IMAP is a standard protocol, so it can be used with any email provider that supports it, not just GSuite.
Functionality: Basic email functionalities, like retrieving and moving messages, are well-supported.
Simplicity: For straightforward email operations, IMAP can be easier to set up without needing extensive permissions or configurations[^1].
Cons:
Limited Integration: IMAP activities may not offer deep integration with other GSuite-specific functionalities like Drive, Sheets, etc.
Complex Attachments Handling: Some users have reported issues with handling attachments using IMAP, which work more reliably with specialized activities provided by GSuite[^2].
Security Requirements: Additional security configurations might be needed to allow IMAP access, such as allowing less secure apps or unlocking Captcha[^3].
GSuite Activities
Pros:
Deep Integration: Provides extensive capabilities tailored for Google services such as Google Drive, Sheets, and Calendar, beyond just email.
Enhanced Functionalities: Easier handling of attachments and other email-related operations in a GSuite environment[^4].
Application Scope: The GSuite Application Scope handles connection management efficiently, making it easier to manage and switch between different GSuite services[^5].
Cons:
Dependency: Tightly coupled with GSuite; if you’re using multiple email providers, this approach could be less flexible[^6].
Setup Complexity: Requires GSuite-specific configurations and permissions, which might be complex for some users[^7].
Rate Limitations: GSuite APIs can be subject to rate limiting, potentially restricting high-volume operations[^8].
Summary
Your choice between IMAP and GSuite activities should depend on your specific needs. If you need straightforward email handling across multiple providers, IMAP might be the right choice. If you require more integration with GSuite services and better handling of specific operations like attachments, GSuite activities would be more advantageous.
I will try answering whatever I can 