{"article":{"id":6514515710107,"url":"https://celigosuccess.zendesk.com/api/v2/help_center/en-us/articles/6514515710107.json","html_url":"https://docs.celigo.com/hc/en-us/articles/6514515710107-View-or-download-your-audit-logs","author_id":417756103851,"comments_disabled":false,"draft":false,"promoted":false,"position":8,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":24220435887003,"created_at":"2022-06-10T14:51:08Z","updated_at":"2026-10-27T20:41:25Z","name":"View or download your audit logs","title":"View or download your audit logs","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-27T20:41:25Z","user_segment_id":null,"permission_group_id":728112,"content_tag_ids":[],"label_names":["Audit Logs","audit log dashboard","audit log","audit log tab","audit logs","where to find audit logs","audit log parameters","download audit logs","help logs","logs","where are audit logs","how to use audit logs","audit","audit data"],"body":"
\n

Audit logs maintain a record of specific activities in your flows, including the fields that were changed, the type of change, and who's responsible for the change. You can view your audit logs at a flow or integration level.

\n

Important: In audit logs, pageProcessors and pageGenerators represent imports and exports, respectively. This is a system naming convention only and does not affect your integrations or flows.

\n
\"8630457702683-All_audit_logs.png\"
\n

Audit logs

\n

These logs show high-level data for all your logs. To narrow down the information to integration audit logs, use Select resource type, user, and source.

\n
\n

\nDownload audit logs

\n

integrator.io keeps audit logs for a minimum of a year. For example, you can view audit logs from the same date one year ago through today. If you download logs to a CSV file or use the audit API endpoint , you can download up to 20,000 records simultaneously. If, for example, you've generated 30,000 records in the last 24 hours, you can download the records in parts by adjusting the Custom date/time range. You can also filter the logs by resource type , user, source, or action and then download the filtered list of records.

\n

To retain audit logs for a longer period, you can upgrade your subscription plan.

\n
\n
\n
\n

\nPractical uses for audit logs

\n

Use your audit logs to troubleshoot flow errors and pinpoint changes that created issues with your integration or flow. You can also determine who changed account permissions. For example, if someone changed an import field and caused an error, you can use audit logs to review the changes. Then, use Integration Lifecycle Management to revert your changes.

\n
\n
\n
\n

\nParameters

\n

Audit logs record every action or change you've made to your flow or integration. The logs record nine (9) parameters for each change:

\n
\nTime
\n

You can configure your account profile to display timestamps in any date/time format. If you've set your account to relative time, the timestamp is displayed as the length of time between the started date and time and the current date and time (1 day ago, 3 hours ago).

\n
\nUser
\n

The user responsible for the changes. In cases where the account is shared by multiple people with the same password, the only username is something similar to \"Account Owner\" or your company name.

\n

Tip: If you're an account owner or administrator you can invite new users (or remove old users) to your account.

\n
\nSource
\n

The Source field in audit logs records which client or surface was used to make the change. Possible values are:

\n\n

The source is determined server-side from the request signal. It cannot be set or overridden by the client.

\n

Note: Audit log entries created before Ora, CLI, and MCP source values were introduced show API for activity performed through those clients. Historical entries are not updated retroactively.

\n
\nResource type
\n

Shows you the resource that was updated. The following resources are monitored for changes:

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Resource TypeDescription
APILogs your API-level updates.
IntegrationLogs your integration-level updates. This includes name changes.
FlowLogs your flow-level updates. In integration-level audit logs, this is displayed as an update to the flow, with a specific field name (pageProcessors/Imports or pageGenerators/Exports) and changes available to view.
ExportLogs your export-level updates. This includes name, operation, and other export settings changes.
ImportLogs your import-level updates. This includes name, operation, and other import settings changes.
ConnectionLogs your connection-level updates. This includes name and authentication changes.
Lookup cachesLogs changes to name, description, and any downloads or cloning of lookup caches.
StackLogs your changes to a stack.
Async helperIf certain data is unavailable, an async helper has the app's API ping integrator.io when the info is available. The flow will be paused until the data is received. This logs all modifications to your async helpers.
File definitionsLogs all modifications to the rules that define how integrator.io should parse or generate EDI or fixed-width files.
RevisionLogs all your version management revisions, including clones, pulls, merges, and snapshots.
ScriptsLogs all modifications to your scripts.
NotificationLogs all notifications when a resource is created or deleted.
\n

There are also account-specific resources, including user status changes, deletions by each user and IP address, agent and agent group changes, and single sign-on logs.

\n

To find these resources, select your profile in the upper right, and then select Account > Audit log.

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Account-specific Resource typeDescription
UserLogs account, permission, IP address, notification, and updates by user. It also logs sign-ins and account switches that a network policy denies, as signinDenied events.
AgentLogs modifications to your secure on-premise or cloud tunnels to integrator.io.
Agent groupLogs when an agent group is created, changed, or deleted, including changes to the agents in the group.
SSO clientLogs all changes to your single sign-on configurations. integrator.io does not display your client secret. Multiple layers of protection are in place, including AES 256 encryption, to keep your client secret safe. When editing this form later, you must enter this value again.
API tokensLogs all API token modifications. integrator.io does not display your API tokens. Multiple layers of protection are in place, including AES 256 encryption, to keep your API token safe. When editing this form later, you must enter this value again.
Network policyLogs the creation, editing, and deletion of network policies.
APIsLogs all modifications to build APIs using API builder and JavaScript APIs.
\n
\nResource name
\n

The name or identifier of your updated resource. Resources with IDs instead of names have been deleted, which is why they're only available by the ID they were given when they were created.

\n
\nAction
\n

The action that was taken. Actions include:

\n\n

The most common action is Update, while Create and Delete are reserved for creating/deleting a flow or another significant event. The Sign in and Sign out actions are reserved for the User resource.

\n
\nField
\n

The Field column gives you an idea of what's been changed. It can display things like pageProcessors, connections, and names.

\n
\nOld and new values
\n

The field values before and after the change.

\n

In the Old and New value fields, you have options including Click to view edits, dates and times a token was updated, and secure connection details. integrator.io never displays secure connection details, such as keys, tokens, or passwords, in audit logs, because those details are encoded.

\n
\"7674780118427-old_and_new_values.png\"
\n

When you use Click to view, old and new edits are displayed side-by-side in a popup diff screen. This is a feature of the flow audit log that's also available in the integration logs. It drills down and shows you the exact changes you made, including any mapping changes.

\n
\"7674789537819-pageprocessor_example.png\"
\n
\n
\n
\n

\nRelated articles

\n\n
\n
\n
","user_segment_ids":[]}}