The Email Scraper in AIForged is designed to check mailboxes for new emails at scheduled intervals. When new emails are detected, the scraper downloads them into the platform for processing. Attachments are then automatically extracted using the built-in attachment utility, streamlining document intake and workflow automation.
With the latest updates, AIForged Email Scraper now supports device code flow authentication for Microsoft 365, providing a secure and user-friendly way to connect to modern mailboxes.
Supported Platforms
Gmail
Connect to Gmail accounts using IMAP with app-specific passwords.
Microsoft 365
Authenticate using device code flow for secure integration with Microsoft 365 mailboxes.
Other Email Providers
Any email provider can be used, provided the correct IMAP settings are applied.
AIForged now supports prompt-less code flow for Microsoft 365 mailbox integration, removing the need for any manual user interaction after setup.
How it works:
Simply provide your Azure AD Tenant ID and Client ID (from your registered Azure application) in the Email Scraper settings.
Setup:
Register an application in your Azure AD tenant.
Note the Tenant ID and Client ID from the registration.
Enter these values in the Email Scraper configuration.
Operation:
The Email Scraper will authenticate and retrieve a device token automatically during its first scheduled run. From the second scheduled run onward, it will begin retrieving emailsโno user prompts or approvals required.
This is the recommended and most secure way to connect Microsoft 365 mailboxes, as no passwords are stored and no user interaction is needed after setup.
Setup Guide
Follow these steps to create and configure an Email Scraping service in AIForged:
Add an Email Scraper Service
Add an email scraper service to your agent, either manually or via the service flow configurator.
Open Service Settings
Apply the following settings, depending on your email provider:
Microsoft 365 (Recommended)
Service Type: IMAP
Server: outlook.office365.com
Port: 993
Username: The email address to be scraped
Password: Not required when using prompt-less code flow
Prompt-less Code Flow: Yes (enable this option)
Tenant ID: Your Azure AD tenant ID
Client ID: Your Azure app registration client ID
Remove XOAUTH2: No
Folder: The mailbox folder to monitor (e.g., Inbox)
Processed Folder: The folder where processed emails will be moved
Gmail
Service Type: IMAP
Server: imap.gmail.com
Port: 993
Username: The email address to be scraped
Password: App-specific password (required by Google for third-party IMAP access)
Remove XOAUTH2: Yes
Folder: The mailbox folder to monitor (e.g., Inbox)
Processed Folder: The folder where processed emails will be moved
Other Providers
Service Type: IMAP
Server: Provider-specific IMAP server address
Port: Typically 993
Username: The email address to be scraped
Password: Email account password or app-specific password
Remove XOAUTH2: As required by your provider
Folder: The mailbox folder to monitor
Processed Folder: The folder where processed emails will be moved 3. Enable Auto Execution
Make sure to turn on the "Auto Execution" option so the scraper runs at scheduled intervals. *
Additional Tips
For the highest security, use device code flow with Microsoft 365 and avoid storing plain-text credentials.
Use app-specific passwords for Gmail, as Google requires this for third-party IMAP access.
Set up different scrapers for different folders or mailboxes to keep processing organized.