1Password Events
1Password sign-in attempts via the Events Reporting API.
- Connector id:
onepassword - Category: iam
Configuration
| Field | Label | Type | Required | Default | Notes |
|---|---|---|---|---|---|
api_token | API Token (Bearer) | secret | yes | — | encrypted at rest |
base_url | Events API Base URL | string | no | https://events.1password.com | Override only for 1Password Business accounts on a non-default region. |
api_token is encrypted at rest by the credential vault before the row is written, and decrypted only at poll time. The value is never logged and never returned by the API — a read of the saved connector shows the field as set, not its contents. See credential vault.
Setup
- In the console, go to Connectors → Add connector and pick 1Password Events.
- Fill in the fields above and run Test connection. The test is read-only and does not save anything.
- Save. Polling starts on a jittered schedule within about a minute; the connector row shows
last_synconce the first poll completes.
last_sync stays emptyThe first poll is the honest signal that the credential works. A connector that saves cleanly and never syncs usually means the credential lacks a scope the vendor requires for reads — check the connectors service log for the vendor's own error, which is passed through verbatim rather than summarised.
Vendor-specific setup notes go here: which console page issues the credential, which scopes to grant, rate limits, and anything the schema cannot express. This section is preserved when the page is regenerated.