profileId and a profile group with
profileGroupId. Older fields and endpoints call a profile group an agent profile pool.
A profile carries:
- attached secrets (usernames and passwords with optional TOTP seeds, API keys, cards, custom secrets)
- an email inbox
- starting cookies
Sticky IP
To give each login its own address, set Addresses to One per login (sticky) on the environment. That needs no profile setting. A login keeps one saved sign-in for environments that give it its own address, and one for the rest. Clear profile state in the profile’s menu clears both, so on Anchor a login with a sticky IP also gets a new one on its next run. A profile that already has the switch on keeps one address when the environment uses the managed proxy, until the switch is removed. Any other network sets the address itself. You can turn it off in the profile’s Signing section, which clears the profile’s saved browser state. Through the API, thestickyIP field on a profile is deprecated too. Set
settings.addresses: one_per_login on the custom environment instead.
In the platform
Open Logins in the sidebar. It has four tabs.
Click Create a login profile to add one. The form walks through Details, Secrets
and Email inbox. Click Ask someone for a login to send a request instead.
Click a profile to open its drawer. It has four sections:
Click Edit in the drawer header to turn every section into its form, then save once.
Starting cookies apply to runs on a browser environment without settings of its own, and
to every run on a Linux or Windows environment. A browser environment with settings supplies
the cookies, even when its list is empty.
Choosing a profile for a run
An execution uses at most one profile. The workflow’s environment decides which profiles may run. The trigger picks one of them.
The list belongs to the environment. Every workflow on the same environment shares it. The run form
lists only the allowed rows. See Profile rows and
How a run is routed.
On the API, pass the profile ID (
profileId):
profileGroupId) instead to let Asteroid choose a profile from a profile group.
See Call a workflow from your code for the full execute call.
Profile configuration
Inbox email prefix
Inbox email prefix
Every profile gets an inbox at
{prefix}@agentmail.asteroid.ai. The default prefix is the profile’s UUID. Set a prefix to get a readable address. Set it as Inbox address when you create or edit the profile. See Email inbox.Credentials and 2FA
A profile does not store secret values itself. It attaches secrets from the organization’s Secrets tab. The profile then exposes##ITEM_KEY.FIELD## placeholders. A profile cannot
attach two secrets that share a key.
On the API, attach secrets (vaultItemIds) on create or update. On MCP, create them with
secrets_create and attach them with profile_update. Profile credentials* fields are
deprecated.
The same secret can attach to many profiles. See Secrets & 2FA for
secret kinds, placeholders, and TOTP seeds.
Profile groups
A profile group holds interchangeable logins for one portal, with the same permissions. You point a run at the group, and Asteroid picks a profile from it. Profile groups solve four problems:- Credential conflicts: stop two executions using one account at the same time.
- Rate limits: spread requests across several accounts.
- Availability: fall back to another profile when one is busy.
- Manual selection: remove the choice from every execute call.
Selection strategies
A profile group uses one of two strategies. The drawer shows it as Picks.
Least recently used rotates fairly. With profiles A, B and C, an execution after B picks whichever of A or C idled longest.
Most recently used concentrates work on fewer profiles. It keeps browser state and authenticated sessions warm.
Concurrent use
allowConcurrentUse decides whether a busy profile can be picked again. The drawer shows it as
Shared use.
Group constraints
Mutual exclusivity
Mutual exclusivity
An execute call takes
profileId or profileGroupId, never both.Organization scope
Organization scope
- Every profile in a group belongs to the same organization.
- A group name is unique within an organization.
- A profile from another organization cannot join the group.
Availability
Availability
- A group needs at least one profile before an execution can use it.
- Remove the last profile and no new execution can use the group.
Group size
Group size
Match the group size to your parallelism. Five simultaneous runs need at least five profiles. Add one or two spare profiles for peak load.
Call a workflow
Pass a profile or a profile group on the execute call
Secrets & 2FA
How Asteroid stores and uses secrets
Email inbox
The email inbox each profile owns
Environments
Where the workflow runs, and its browser settings
Security
How Asteroid protects stored credentials

