Logs for debugging integrations
When an integration does something unexpected, you need to know who did what and when.
- Who can use this
- Account owner, Manager, Developer
When an integration does something unexpected, you need to know who did what and when.
When an integration does something unexpected, you need to know who did what and when. Audit Logs is a record of every signed-in action in your workspace: sign-ins, two-factor, staff changes, broadcasts, conversations and API tokens. This page shows how to use it, and where to look for webhook and API problems.
Settings → Audit → Logs. The page is titled Audit Logs. You need the Manage Settings permission.
Other places to look:
| Problem | Where |
|---|---|
| Webhook not arriving, failing or disabled | Settings → App → Developers → Deliveries and Health |
| REST API call refused | Developer portal → Your console → Request log |
| Who created or revoked a token, changed a setting, sent a broadcast | Settings → Audit → Logs |
request_id from the API error.Click a row to see its details.
Click Integrity. The log is a hash chain:
Do it with Copilot
(logs_search; the audit part is for managers only)
Do it with Copilot
Do it with Copilot
| What you see | Why | What to do |
|---|---|---|
| "Audit API rejected your token. Reload the page." | Your session expired | Reload the page and sign in again |
| "Integrity check failed: …" | The check could not run | Try again later |
| An action you expect is missing | Wrong time range or filters | Click Clear all and widen the range |
| Empty page or no access | You lack Manage Settings | Ask an account owner |