Delivery Logs
Review the complete history of every automated action — what was sent, when, and whether it succeeded.
Overview
Delivery Logs give you a full audit trail of your automation activity. Every time a trigger fires, a webhook sends data, or a drip sequence step executes, a record is created in the delivery log. Use these logs to confirm your automations are working, diagnose failures, and demonstrate compliance with your outreach records.
Delivery Logs are available on the Growth and Scale plans.
Accessing Delivery Logs
- Go to Automation in the left sidebar.
- Select Delivery Logs.
The log shows all automation events in reverse chronological order (newest first).
Reading the Log
Each log entry includes:
| Column | Description |
|---|---|
| Timestamp | The exact date and time the action was attempted |
| Type | The automation type: Webhook, Trigger Action, or Drip Step |
| Contact | The contact the action was performed for (if applicable) |
| Event / Step | The event that fired the trigger, or the drip sequence step name |
| Status | Whether the action succeeded, failed, or is pending |
| Details | A short description of the outcome or error message |
Status Values
| Status | Meaning |
|---|---|
| Delivered | The action completed successfully |
| Failed | The action could not be completed — see Details for the reason |
| Retrying | A failed delivery is being retried automatically |
| Skipped | The action was bypassed due to an exit condition or contact opt-out |
| Pending | The action is queued and has not yet executed |
Filtering Logs
Use the filter bar at the top of the page to narrow results:
- Date range — view logs for a specific time window.
- Type — show only Webhooks, Triggers, or Drip Sequences.
- Status — show only failures to quickly identify problems.
- Contact — search for all automation activity for a specific person.
- Campaign — filter by the campaign associated with the action.
Diagnosing Failures
When a log entry shows a Failed status, click the entry to expand it and see:
- The full error message returned by the destination (for webhooks).
- The step number and sequence name (for drip sequences).
- The exact payload that was sent (for webhooks) — useful for confirming the data format matches what your external system expects.
Common Failure Causes
| Cause | How to Fix |
|---|---|
| Webhook URL not reachable | Verify the URL is active and publicly accessible; check your external system's firewall settings |
| Webhook response timeout | Ensure your endpoint acknowledges receipt within 10 seconds |
| Contact opted out | The contact unsubscribed — this is expected and correct behavior |
| Invalid phone number | The contact's phone number is missing or incorrectly formatted |
| Sequence exit condition met | The contact was removed from the sequence before this step — not a true failure |
Log Retention
Delivery logs are retained for 90 days. If you need a permanent record, export logs using the Export button (CSV format) before they expire.
Tips
- Check logs after enabling a new automation: Confirm the first few events fire correctly before relying on the automation for live leads.
- Filter by "Failed" regularly: A quick weekly check of failed deliveries can surface webhook outages or misconfigured triggers before they become a larger problem.
- Use the contact filter for disputes: If a contact claims they received a message they shouldn't have, the delivery log gives you a precise, timestamped record of every automated touch.