The job of this console
Find the failure, read the masked detail, fix mapping or the source, retry the job. Never paste raw payloads into chat or Work Graph.
Integrations · Logs
Integration Logs
Payload and error detail for connector runs — operational logs, masked, not Admin audit and not a business register.
Scroll to Flowcharts. Scenario: Inspect a connector log then fix mapping or data.
Operational detail
Why a batch failed — not the employee file
Integration logs show connector errors and payloads. They are not Admin audit, not AI audit, and not a place to edit people or projects.
Integrations → Integration logs
Route
/integrations/logs
Org flag logsEnabled
Integration admin · Ops
Seat at the table
Integration admins and ops with logsEnabled.
The working rhythm
From a red health card, open the log, fix, retry, confirm in product.
Moments that bring you here
A poison payload. Vendor schema change. Duplicate external ids. A compliance question about what was sent.
ⓘ
Three audits
This page: connector ops. Admin audit: org events. AI audit: masked agent runs. Keep sensitive fields masked in all three.
Flowcharts
1 — Log then fix
Read the error, change the map or source, retry.
flowchart TD
A[Open Integration logs] --> B[Filter]
B --> C[Open failure]
C --> D[Mapping or source]
D --> E[Retry job]
- 1OpenIntegrations → Integration logs.
- 2FilterConnector and time.
- 3ReadMasked payload / error.
- 4FixThen retry the job.
Overview
Integration logs are operational. Admin audit is the org event register. AI audit is masked AI runs. Logs must not become an unmasked warehouse of bank, tax, or medical payloads.
How to use
1. Retention
Follow data-retention policy.
2. PII in payloads
Treat as a mapping defect if raw sensitive fields appear.
3. Not a queue editor
You do not approve leave from a log line.