See exactly what ran, what failed, and where to fix it
Note: Available on Outreach Pro plan and above.
Whether you want to confirm a workflow ran as expected or track down why something failed, Execution Logs give you a complete record of every automation that has run inside your CRM integration, with node-level detail so you can see precisely what happened at each step.
What are Execution Logs?
Execution Logs is a dedicated tab inside your CRM integration settings. It records every execution across both your Custom Workflows and your existing Trigger Rules in one unified view.
Each row in the logs table represents one execution, triggered by an event, a schedule, or an API call.
How to Access Execution Logs
Go to Settings → Integrations, open your connected CRM, and click the Logs tab. The table loads all recent executions for that CRM.
Click Refresh at the top of the table to pull the latest executions.
Filtering Logs
Use the filters to narrow down what you're looking at:
Status — All, Success, or Error
Date Range — Set a From and To date. Both dates are inclusive.
Filtering by Error with a specific date range is the fastest way to investigate an issue during a particular campaign period.
Inspecting an Execution
Click any row to open the Execution Detail panel on the right.
The panel shows the full node chain for that execution. For each node you can see:
Node name and method
Status (success or failed)
Duration
Raw request payload — the data sent by that node
Raw response payload — what the system received back
How to Debug a Failed Execution
When a workflow errors, the failing node is highlighted in the Execution Detail panel so you can find the root cause without digging through logs manually.
Step 1: Filter by Error
In the Logs tab, set the Status filter to Error and apply a date range if needed.
Step 2: Open the failed execution
Click the relevant row to open the Execution Detail panel.
Step 3: Find the highlighted node
The Error node is visually marked. Every node before it ran successfully. Every node after it did not run.
Step 4: Read the request and response
Expand the request payload to check what data was sent. Expand the response to read the error message returned. This tells you what the system expected versus what it received.
Common issues to look for:
A required field is missing or has an incorrect value in the request
An action references a CRM field that has been renamed or removed
The trigger fired with incomplete data, causing a condition to evaluate incorrectly
An authentication token has expired or been revoked
Step 5: Fix and re-publish the workflow
Go back to the workflow list, open the workflow in edit mode, make the fix, and re-publish.
Fixing a workflow does not re-run past failed executions. The trigger must fire again to generate a new execution.
FAQs
Do Execution Logs show both Custom Workflows and Trigger Rules?
Do Execution Logs show both Custom Workflows and Trigger Rules?
Yes. The Logs tab is a unified view, both custom workflows and your existing trigger rules appear in the same table for that CRM.
Can I re-run a failed execution?
Can I re-run a failed execution?
No. Failed executions cannot be manually re-triggered from the logs. Fix the workflow and wait for the trigger to fire again, or re-trigger it manually if you're using an API Call trigger.
Why does an execution show as Error if some nodes succeeded?
Why does an execution show as Error if some nodes succeeded?
A workflow is marked Error if any node in the chain fails, even if earlier nodes completed successfully. The highlighted node in the detail panel shows the exact point of failure.
Will I see a log entry if the trigger fired but conditions weren't met?
Will I see a log entry if the trigger fired but conditions weren't met?
No. If conditions aren't satisfied, the workflow doesn't execute and no log entry is created.
How long are execution logs retained?
How long are execution logs retained?
Log retention depends on your plan. Contact support for details.
Can I export the logs?
Can I export the logs?
Export availability depends on your plan. Contact support for details.