Skip to main content
The audit log is an account-level record of who did what, and when. It lists configuration changes, member and role changes, sign-ins, key and token events, and job runs in your account, newest first. Use it to collect compliance evidence or to investigate an incident. Integrate.io records events only after the audit log is turned on for your account. Nothing from before that moment is recorded or backfilled. Integrate.io keeps events for 90 days and deletes older events nightly.
The audit log is an opt-in account feature. If the page shows “To enable audit logs on your account, contact your account manager or support.”, contact your account manager or Support to turn it on.

Who can view the audit log

You can view and export the audit log when you have one of these roles:
  • Owner or Admin on the account.
  • A custom role that includes the View and export the audit log permission (viewAuditLog). See Custom Roles.
Members without the permission see “You do not have permission to view the audit log. Contact your account administrator.” The permission covers every package group and connection in the account, whatever else the member’s role is limited to.

Viewing the audit log

1
On the left menu, open Settings.
2
Under Account, click Audit Log.
Right after the feature is turned on, the page shows “No activity yet. Events are recorded from” followed by the date recording started. The table has these columns: The table shows 50 events at a time. Click Load more to see older events.

Event details

Click a row to expand it. The details have up to three parts:
  • Changes: a table of Field, From, and To values for the fields that changed. When a record is deleted, its last values appear under Deleted values.
  • Details: extra information for the event, such as the old and new role in a role change.
  • Request: the event name, IP address, client (for example, “Chrome on macOS”), and request ID. Events from the same request share a request ID.
Integrate.io never records secret values:
  • Fields that hold secrets show [FILTERED].
  • Changes to a connection’s host, port, database, or password show [CHANGED] without the old or new value.
  • For account and global variables and secrets, only the key names are recorded.

Filtering events

Use the filter bar above the table, then click Apply. Click Reset to clear every filter. The preset time ranges are rolling windows measured from when you click Apply. Custom dates are read in your profile’s time zone. The filters are saved in the page URL. Reload the page or share the link to open the same filtered view.

Exporting to CSV

Click Export CSV at the top right of the page. The file contains the events that match the current filters, up to 10,000 rows. If more than 10,000 events match, the export fails with an error. Narrow the date range and export again. Integrate.io records each export in the audit log.

What the audit log records

Events are grouped into these categories in the Event filter:

Who appears in the User column

  • DASHBOARD: a member working in the Integrate.io dashboard.
  • API KEY: a request made with an API key.
  • MCP: an AI agent working through the Integrate.io MCP server.
  • SYSTEM: an action Integrate.io performed with no user behind it.
When Integrate.io staff change something in your account, the event shows Integrate.io Support as the user. Staff sign-ins, sign-outs, and page views are not recorded in customer accounts, and neither are changes staff make to their own profile (password, MFA, or API key).

Sign-ins and invited members

Sign-ins and other personal events (password and MFA changes) appear in every account the user belongs to and has joined. A member added by invitation joins the account when they first open it. Accepting the invitation, or first launching Integrate.io from it, also counts as joining, but only when it is their only pending invitation. Until then, that account does not receive their personal events.

Not recorded yet

The audit log does not yet record:
  • Member role changes and removals made through the legacy members interface.
  • Clusters terminated from the legacy interface or by Integrate.io staff tools.
  • Sign-ins through partner add-on SSO.

Reading the audit log through the API

The audit log is also available through the Integrate.io API. Requests need an API key for a user who can view the audit log, and they return 404 when the feature is off for the account.
The endpoint accepts since and until (an ISO 8601 timestamp or a date), event (an exact event name, a category.* pattern, or a comma-separated list), actor_type, actor_id, target_type, and target_id. Results are newest first and paginated with a Link header. GET /audit_events/export returns the same results as CSV, with the same 10,000-row limit.

FAQ

Why is the audit log empty for dates before it was turned on? Integrate.io starts recording when the feature is turned on for the account. Earlier activity is not backfilled. Why don’t I see a member’s sign-ins? The member has not joined the account yet. Their sign-ins appear after they first open the account. Accepting the invitation, or first launching Integrate.io from it, also counts, but only when it is their only pending invitation. Why does a connection change show [CHANGED] instead of the new value? Connection host, port, database, and password values are never stored in the audit log. The row shows that the field changed without showing the values. How long are events kept? 90 days. Integrate.io deletes older events nightly. Export the log to CSV regularly if you need a longer history. Can a custom role view the audit log? Yes. Edit the role and tick View and export the audit log under Audit Log. The Reader, Editor, and Operator presets do not include it.

Custom Roles

Setting Account Member Roles

Managing Account Members

Log Drains

Last modified on November 17, 2026