Log in with saved credentials
Save a username and password once as a credential, and the Log in with credentials step fills them into a site's sign-in form at runtime. The password is never kept in the automation itself, and because the step references the saved credential, changing a password later means editing the credential, not rebuilding the automation.
This works for any site that has a username and password login. The same credential can also store a two-factor authentication secret, so a single setup covers both ordinary logins and logins that require 2FA.
For other login methods, see Google Sheet steps, sessions, 2FA, password managers, or keeping login data on your network.
Save your login credentials
Open Login credentials from the dashboard sidebar (below External API keys). Credentials are saved once and referenced by the automation steps, so changing a password later means editing the credential, not rebuilding the automation.
You can save credentials with one of two providers:
- Axiom stores the credentials encrypted in Axiom's own database. They are never returned to your browser.
- 1Password keeps the credentials in your own 1Password vault, and Axiom fetches them at runtime. Axiom only stores the vault reference and an access token, never the username, password, or 2FA secret. See the 1Password integration page for more.
You can save as many credentials as you like, including several for the same site. They're told apart by their label in the credential picker.
Axiom (built-in) credentials
| Field | Required | Notes |
|---|---|---|
| Provider | Yes | Select Axiom. |
| Reference | Yes | A human-readable name, e.g. "GitHub (work)". |
| Username / email | No | Optional — some credentials may be 2FA-only. |
| Password | No | Optional. |
| 2FA secret | No | Only needed for sites that use two-factor authentication. Accepts a bare base32 secret (e.g. JBSWY3DPEHPK3PXP) or a full otpauth:// URI. See Log in with 2FA for where to find it. Only shown while you're adding the credential — if you don't save it elsewhere, you'll need to re-enrol to set it again. |
1Password credentials
| Field | Required | Notes |
|---|---|---|
| Provider | Yes | Select 1Password. |
| Reference | Yes | A human-readable name, e.g. "GitHub (work)". |
| Item reference | Yes | The op:// URI for the item, e.g. op://Axiom/GitHub. |
| Service account token | Yes when adding | A 1Password service account token with read access to the vault. Leave blank when editing to keep the existing token. |
For how to create the vault, the service account token, and the item reference, see the 1Password integration page.
Manage saved credentials
Where you are using built-in axiom credentials, the list shows which fields are stored (Username stored, Password stored, 2FA stored) without revealing the values. For third party providers, these are stored remotely and not shown. You can:
- Add a new credential.
- Edit a credential. The form opens with the label and provider filled in, but sensitive fields are blank. Leave a sensitive field blank to keep its stored value, or fill it in to overwrite it. The credential keeps the same ID, so every automation that uses it continues to work.
- Delete a credential. This permanently removes it.
Sign in with the Log in with credentials step
To sign in, add the Log in with credentials step after navigating to the login page:
- 1 Go to page (the login page)
- 2 Log in with credentials
- 3 Click element (submit, if needed)
To build it:
- Add a Go to page step and set its URL to the sign-in page.
- Add a Log in with credentials step. Choose your saved credential, then select the username and password fields on the page. Leave a field empty if the credential doesn't store that value.
- Add a Click element step for the submit button. Some sites submit as soon as the password is entered, so this step may not be needed.
The step fetches the username and password securely at runtime and types them in, so nothing sensitive is stored in the automation. To avoid signing in on every run, you can also share your session or store cookies.
Sites that also require 2FA
If the site asks for a verification code after the password, you don't need a different login method. Add the 2FA secret to the same credential and one extra step generates the code automatically. See Log in with 2FA, which builds directly on this method.