Atlassian Organization Audit connector setup
Polls audit log events from the Atlassian Organizations REST API (GET /orgs/{orgId}/events-stream).
What you need first
| Requirement | Details |
|---|---|
| Atlassian access | Organization administrator |
| Organization ID | UUID for your Atlassian organization |
| API key | Cloud Admin API key with access to audit events |
1. Create an API key and copy your organization ID
- Sign in to Atlassian Administration.
- Go to Settings → API keys (or API access depending on your admin UI).
- Click Create API key.
- Name the key (e.g.
Perpetual Atlassian Audit). - Assign the
read:events:adminscope (required for the events stream endpoint). - Complete two-factor authentication if prompted.
- Copy the API key and Organization ID. Atlassian shows the secret only once — store both securely.
To find your organization ID later: Settings → Organization settings (or the API key creation flow displays it).
2. Perpetual credential
- Log in to Perpetual. Open Settings from the user/org control at the bottom left of the sidebar (click your name → Settings), then go to Credentials → New Credential.
- Choose Text.
- Fill in:
| Field | Value |
|---|---|
| Name | Unique identifier using letters, digits, and underscores only (e.g. atlassian_org_audit). |
| Allowed URL patterns | *.atlassian.com |
| Value | API key from step 1 (used as a Bearer token) |
- Save the credential.
3. Create the Atlassian Organization Audit connector
-
Go to Datasets → Connectors → Create Connector.
-
Select Atlassian Organization Audit.
-
Connector name: unique identifier (letters, numbers, underscores).
-
Configure:
- Atlassian API access: select the credential from step 2.
- Poll interval (minutes): default
5. - Organization ID: the org UUID from step 1.
-
Optionally check Deploy, then save.
First run backfills roughly the last 24 hours of audit events, then advances the stream cursor on subsequent polls.
Operational notes
- Key rotation: Create a new API key, update the Perpetual credential, verify runs succeed, then revoke the old key.
- Rate limits: The connector retries
429and5xxresponses with backoff; very large backfills may span multiple runs.