Notification settings help you stay informed about your robots' performance by sending email alerts when tasks fail or encounter issues. You can control both workspace-wide settings and individual robot notifications.
Accessing notification settings
To manage your notification preferences:
Navigate to Workspace Settings in your dashboard.
Under Workspace Members, select the 🔔 to access Notification Settings.
Once selected, you'll see the notification settings for that user.
Global notification settings
Task failure notifications
Configure how you receive alerts about robot task failures:
Notification frequency options:
Instantly: Receive an email immediately when a robot task fails.
Daily: Receive a daily batch email of task failures at 1pm UTC.
Weekly: Receive a weekly batch email of task failures every Tuesday at 1pm UTC.
Monthly: Receive a monthly batch email of task failures on first Tuesday of each month at 1pm UTC.
Never: Never receive batch emails for task failures.
Setting your preference
Locate Get notification about task failures section.
Click the dropdown menu (shows "Daily" by default).
Select your preferred notification frequency.
Your setting saves automatically.
Individual robot notifications
Enable notifications for new robots
Toggle the Enable notifications for new robots setting to automatically receive alerts for any new robots created in your workspace.
Managing existing robot notifications
For each robot in your workspace, you can:
View robot details:
Robot name and source website
Last run date
Creation date
Creator information
Control notifications:
Toggle notifications on/off for each individual robot
Use Disable All to turn off notifications for all robots
Use Enable All to turn on notifications for all robots
Use the search bar to find specific robots quickly
Understanding notification types
Task failure notifications
These alerts notify you when:
A robot encounters an error during execution
A task fails to complete successfully
Technical issues prevent data extraction
Batched vs instant notifications
Instant notifications:
Sent immediately when failures occur
Useful for critical monitoring
Can result in many emails for frequent failures
Batched notifications:
Consolidate multiple failures into single emails
Reduce inbox clutter
Provide summary reports at regular intervals
Include failure trends and patterns
Best practices for notification management
For high-volume extraction
Use Daily or Weekly batched notifications to avoid email overload
Enable notifications only for critical robots
Consider using instant notifications for important monitoring robots
For occasional use
Instantly or Daily notifications work well for smaller operations
Enable notifications for all robots to stay informed
Team environments
Coordinate notification settings across team members
Consider having different team members monitor different robots
Use role-based notification strategies
Troubleshooting notifications
Not receiving notifications
Check your email spam/junk folder
Verify your email address is correct in your Browse AI account
Ensure notifications are enabled for the specific robots
Confirm your notification frequency isn't set to "Never"
Too many notifications
Switch from Instantly to Daily or Weekly batched notifications
Disable notifications for less critical robots
Use Disable All and selectively enable only important robots
Missing robot in notification list
Refresh the page to see newly created robots
Check that you're in the correct workspace
Verify the robot exists and hasn't been deleted
Notification content
What's included in failure notifications
Task failure notifications typically contain:
Robot name and description
Failure time and date
Error details (when available)
Links to robot settings and task history
Suggestions for resolving common issues
Batched notification summaries
Batched notifications include:
Total number of failures in the period
List of affected robots
Failure trends and patterns
Direct links to investigate issues
Managing notifications across workspaces
Workspace-specific settings
Each workspace has its own notification settings
Switching workspaces may require adjusting preferences
Team members can have different notification preferences
Account-level considerations
Your email address applies across all workspaces
Notification preferences are workspace-specific
Consider your total notification volume across all workspaces