Connecting Accounts

14 January 2026•4 min read

For your agents to work on external platforms—whether that's posting on LinkedIn, checking emails in Gmail, or browsing Twitter—they need access to the relevant accounts. O-mega manages these credentials securely, giving your agents the ability to operate on your behalf across the web while keeping your login information protected.

When you connect an account to an agent, you're essentially giving that agent permission to use those credentials during browser sessions. The agent can then log in, navigate, and take actions on that platform as if they were you or the account holder.

Supported Account Types

O-mega supports accounts across a wide range of platforms. This includes the major social networks, email providers, professional services, and many niche platforms your agents might need to access.

Supported platforms include:

Email - Gmail, Outlook, and custom email accounts
Social Media - LinkedIn, Twitter, Facebook, Instagram, TikTok
Professional - GitHub, Slack, Discord
Other - Reddit, Medium, Product Hunt, and many more

New platforms are added regularly, so check the account type dropdown when adding an account to see the full current list.

Adding an Account

Connecting an account to your agent is straightforward. You provide the credentials, and O-mega handles the secure storage and makes them available during browser sessions.

To add an account:

Open the agent you want to configure
Navigate to the agent's Info section
Scroll to the Accounts area
Click "Add Account"
Select the account type (e.g., LinkedIn)
Enter the required credentials (typically email, username, and password)
Save your changes

Once saved, your agent can use these credentials whenever it needs to access that platform during a browser session. You don't need to provide credentials again for future tasks on that platform.

Account Fields

Each account type has fields relevant to that platform. While the specific requirements vary, most accounts share a common set of information.

Typical account fields include:

Account Name - A display label to help you identify the account (e.g., "Work LinkedIn" vs "Personal LinkedIn")
Email - The email address associated with the account
Username - The platform username or handle
Password - The account password (encrypted and stored securely)
Profile URL - A direct link to the profile page
Additional Fields - Any other platform-specific information needed for login or identification

Not all fields are required for every account type. The form will indicate which fields are necessary for the platform you've selected.

Website Usage Scoping

For additional security and control, you can specify where each account can be used. This prevents your credentials from being used on unexpected websites.

Scoping options include:

All - The account can be used on any website (this is the default behavior)
Include - The account will only be used on specific domains you specify
Exclude - The account will be used everywhere except the domains you specify

For example, you might scope a LinkedIn account to only be used on linkedin.com and related domains, ensuring those credentials never get entered on a phishing site or unrelated platform.

Primary Email for Account Creation

Sometimes your agent needs to sign up for new services or create accounts on platforms during its work. When this happens, the agent needs an email address to use for the registration.

You can designate one of your connected email accounts as the "Use for account creation" email. When your agent encounters a signup form on a new platform, it will use this email address as the default for creating the new account.

This keeps new account creation organized and predictable—you always know which inbox will receive confirmation emails and notifications from services your agent signs up for.

Security

Account security is treated with utmost importance. All credentials are encrypted before storage, and passwords are never exposed in logs, responses, or any visible interface.

Only your agent can access the credentials during active browser sessions—and only when actually needed for authentication on the relevant platform. The credentials are not accessible through the API or any other channel.

You can remove an account connection at any time, which immediately revokes your agent's ability to use those credentials.