Activity Logs
The audit trail of every user action, background job, and webhook event in your organization.
The Activity Logs page is your audit trail. Every meaningful change — by a user, a background job, or a webhook — is recorded here with timestamps, the actor, and the affected entity.
When something looks wrong, the activity log is usually faster than asking your team. "When did this contact get tagged VIP?" "Why did this release get cancelled?" — both 5 seconds away.
Where to find it
Activity in the dashboard sidebar.
Activity Logs
Tracking all system activities and events across your organization
| Time | Type | Actor | Event | Status |
|---|---|---|---|---|
| 2 min ago | BACKGROUND_JOB | system | PROCESS_RELEASE_PAYMENTS · Spring 2026 Reds | SUCCESS |
| 15 min ago | USER_ACTION | Riley Park | Contact updated · Alex Chen | SUCCESS |
| 1 hr ago | WEBHOOK | Stripe | payment_intent.succeeded | SUCCESS |
| 1 hr ago | WEBHOOK | Stripe | payment_intent.payment_failed | WARNING |
| 3 hrs ago | BACKGROUND_JOB | system | SYNC_SQUARE_STOCK | FAILED |
Activity types
| Status | Meaning |
|---|---|
| USER_ACTION | A team member did something — created a contact, processed payments, changed a setting. |
| BACKGROUND_JOB | A scheduled or triggered job — sync, payment processing, automations. |
| WEBHOOK | An incoming or outgoing webhook — Stripe events, FedEx tracking, OnCloudWine → external. |
| SYSTEM_EVENT | Internal system events — schema migrations, configuration changes, cache clears. |
Activity statuses
| Status | Meaning |
|---|---|
| SUCCESS | Completed without errors. |
| IN_PROGRESS | Currently running. |
| WARNING | Completed but with caveats — partial sync, retry-able failure, etc. |
| FAILED | Did not complete. Error captured on the entry. |
Filtering
Five filter axes:
- Type
Multi-select. Most common: BACKGROUND_JOB to triage failed syncs.
- Status
Multi-select. FAILED + WARNING is a useful pre-set when investigating.
- User
Filter to a specific team member's actions. For audit and onboarding — "what did the new hire do today?"
- Entity
Filter to actions on a specific entity type — contacts, releases, products, etc.
- Date range
Defaults to the last 24 hours. Extend back as far as needed.
What's logged
Every meaningful change. Examples:
| Category | Logged events |
|---|---|
| Contacts | Created, updated, deleted, status change, tags added/removed, merged. |
| Releases | Created, promoted to PENDING, cancelled, payments processed, modifications added. |
| Products | Created, updated, stock adjusted, synced from Square/Woo. |
| Fulfillments | Status changes, shipments created, swaps applied. |
| Payments | Charge attempts, success/failure, refunds. |
| Settings | Org settings changes, integrations connected/disconnected, team changes. |
| Background jobs | Job start/progress/completion for every scheduled or triggered job. |
Detail view
Click any entry to see the full detail:
- Actor
Team member, system, or external (e.g., Stripe, Square).
- Action
The verb (created, updated, deleted, etc.).
- Entity
The thing that was affected — links directly to that record.
- Before / After
For updates, the diff of changed fields.
- Metadata
Job-specific details — how many records processed, error stack traces for failures, request/response bodies for webhooks.
Investigating failures
When a background job fails:
Filter to FAILED
Filter Type: BACKGROUND_JOB, Status: FAILED.
Open the entry
The detail view shows the error message and (for code-level errors) the stack trace.
Re-run if appropriate
Many job types have a Retry button on the activity entry. Some (like one-time syncs) need to be re-triggered from their integration page.
If recurring, contact support
Provide the activity entry ID — we can look up the full server logs and root-cause faster.
Retention
Activity logs are kept for 2 years by default. Older entries are archived (still queryable via support) and eventually purged according to your data retention policy.
Exporting
For compliance audits, click Export CSV on the activity log toolbar. Honors your current filter set. Large exports run as background jobs and email the link when ready.