The CloudRadial AutomationAI 1Password Business extension lets a workflow or agent work with 1Password vaults and items through your own 1Password Connect server: list vaults and items, look up a credential or a one-time password, and, with approval, create, update, replace, or delete an item. It is useful for handing off client credentials during onboarding and cleaning them up during offboarding. This article covers what the extension can do, the Connect server and secrets it needs, which tools require approval, how it handles secret values, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Setting Up 1Password Connect
- Providing the Credentials to Your Runner
- Reads and Approval-Gated Changes
- How the Extension Handles Secret Values
- Skills
- Tips for Working With 1Password Data
What the Extension Covers
The extension calls the 1Password Connect REST API and provides 13 tools across these areas:
| Area | What you can automate |
| Connectivity | Check that your Connect server is reachable |
| Vaults | List the vaults the Connect token can see, with their item counts, and read one vault's details |
| Item lookup | List the items in a vault, find items by exact title or by tag, read one item in full with its fields, and read an item's current one-time password (TOTP) |
| Item files | List the files attached to an item and download a file's content |
| Item changes | Create an item, such as a login, password, API credential, or secure note, optionally with a generated password; update individual fields; replace an item in full; and permanently delete an item |
The extension works with existing vaults and their items. It does not create vaults or manage 1Password team members. Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow.
Setting Up 1Password Connect
The extension does not connect to 1Password directly. It calls a 1Password Connect server that you run in your own environment, for example in Docker or Kubernetes, and authenticates with a Connect access token.
- On 1Password.com, go to Developer > Directory, select Other under Infrastructure Secrets Management, and select Create a Connect server. You can also use the
op connect server createcommand in the 1Password CLI. Creating a Connect server requires membership in a group with permission to manage Secrets Automation. - Give the Connect server access to only the vaults the automation needs. Connect cannot access your built-in Personal, Private, or Employee vault, or your default Shared vault.
- Save the
1password-credentials.jsoncredentials file and the access token that 1Password issues. To issue another token later, go to Developer > Connect servers, choose the server, and select New Token, or use theop connect token createcommand. A token's vault list cannot be changed after it is created; to change it, revoke the token and issue a new one. - Deploy the Connect server with the credentials file in Docker, using Docker Compose, or in Kubernetes, using 1Password's Helm chart. For the full procedure, see 1Password's Get started with a 1Password Connect server.
The extension can see and change only the vaults the token can access. Your runner must be able to reach the Connect server's URL. By default, the Connect REST API listens on port 8080 on the host where it runs, so publish it at an address the runner can reach.
Providing the Credentials to Your Runner
Store two secrets in your runner's Key Vault with these exact names:
| Secret | Value |
OnePassword-ConnectUrl |
The base URL of your Connect server, host only with no path, for example https://my-connect.example.com. The extension adds the API path itself. |
OnePassword-ConnectToken |
The Connect access token, a long JWT-style string |
For how to add secrets, see Accessing and updating your runner's Key Vault. If you run a separate Connect server per client, see Managing companies and per-company credentials.
Reads and Approval-Gated Changes
Of the 13 tools, five run without approval. The other eight pause the run for approval: the four tools that change items, and four read tools that can return secret values. The request appears as an Action Required item in the Inbox until someone approves it. See Handling Action Required items in the Inbox.
| Tool behavior | Tools |
| Approval-gated changes | Create an item; update an item's fields; replace an item; delete an item |
| Approval-gated reads | Read one item in full; read an item's one-time password; list an item's files; download a file's content |
| Read-only | Check the Connect server; list vaults; read one vault; list items; find items by title |
Deleting an item is permanent, and replacing an item removes every field and section not included in the replacement, so review those requests carefully before you approve them.
How the Extension Handles Secret Values
The Connect API returns item secrets in cleartext, so some reads expose credentials:
- Listing items and finding items by title return summaries only, such as the id, title, category, tags, and URLs, with no field values
- Reading an item in full returns its password, concealed, and one-time password fields
- Reading a one-time password returns secret material. The agent is instructed to report only the current code.
- Listing an item's files can include small file contents, and downloading a file returns its raw content, which may be a key, certificate, or other secret
Agents are instructed to treat every returned field value as a secret, to surface only what you asked for, and never to repeat or log full credentials. Approve a secret read only when the run needs that value.
Skills
The extension ships four skills that guide an agent through common 1Password tasks:
| Skill | Use it to |
| Provision a Vault Item for Onboarding | Hand off a credential to a client: confirm the target vault, then create a login, password, or API credential item in it, optionally with a generated password. Creating the item is approval-gated. |
| Look Up a Credential | Retrieve a stored credential, find an item by title, or read a one-time password. The responses contain secret values, and the full-item and one-time password reads are approval-gated. |
| Manage Items | Update a field, replace an item, or delete an item during cleanup or offboarding. Every change is approval-gated. |
| Audit Vaults & Items | List the vaults the token can see, count or browse the items in a vault, or check the Connect server's health. Read-only. |
To give an agent these skills, see Creating custom agents and using them in workflows.
Tips for Working With 1Password Data
- Refer to vaults and items by name. The agent lists vaults to find the vault id, then finds the item by its exact title, rather than guessing ids.
- To change one field, such as rotating a single password, ask for a field update rather than a replace. A field update leaves the item's other fields alone.
- When you create an item, you can ask 1Password to generate a strong password instead of supplying one
- If every call fails, run the Connect server check first. It confirms that
OnePassword-ConnectUrlis reachable from the runner.
If you are still having trouble, we’re here to help! Submit a ticket here for assistance, and don’t forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.