Execution History
The Execution Log tracks every time a workflow runs (or is skipped). Use it to verify your workflows are working, diagnose failures, and understand how your automations are performing.
Access it from the sidebar under Workflows → Execution History.
Execution List
The main view shows a chronological list of workflow executions with the following columns:
| Column | Description |
|---|---|
| Workflow | The name of the workflow that ran |
| Trigger Call | The call that triggered the workflow (links to Call Details) |
| Execution Time | When the workflow ran |
| Status | The outcome of the execution |
Execution Statuses
- Success — All conditions passed and all actions completed without errors
- Failure — One or more actions encountered an error during execution
- Skipped — The workflow was triggered but conditions were not met, so no actions ran
Execution Details
Click on any execution to see a detailed breakdown of what happened:
Conditions Evaluation
If the workflow has conditions, you will see which conditions were evaluated and whether each one passed or failed. This is invaluable for understanding why a workflow was skipped.
Action Results
For each action in the workflow, you can see:
- Action type — What the action was (e.g., GHL log_call, Slack message)
- Status — Whether this specific action succeeded or failed
- Error message — If the action failed, the error details are shown here
Filtering
Use the filter controls to narrow down the execution list:
- Workflow — Select a specific workflow to see only its executions
- Status — Filter by Success, Failure, or Skipped
- Date range — Focus on a specific time period
After creating a new workflow, filter the execution log by that workflow’s name and make a Test Call. You should see a new execution entry appear within a minute. This is the quickest way to verify your workflow is configured correctly.
Common Failure Reasons
If you see failed executions, here are the most frequent causes:
Invalid API Credentials
The integration’s API key or OAuth token has expired or been revoked. Go to Integrations to reconnect the affected service.
Missing Required Fields
An action requires a field that is not available in the call data. For example, a “create contact” action needs a phone number, but the call data might not include it in rare edge cases.
Rate Limiting
The external service (CRM, calendar, etc.) is rejecting requests because too many were sent in a short period. This can happen if you have many calls ending simultaneously. The action will typically succeed on the next call.
Integration Not Connected
The workflow references an integration (e.g., HubSpot) that has not been set up yet. Connect the integration from the Integrations page.
Failed actions do not automatically retry. If an action fails, you will need to manually address the issue (fix credentials, reconnect the integration, etc.) and wait for the next matching call to trigger the workflow again.
Monitoring Best Practices
- Check the log after deploying a new workflow — Make a test call and verify the execution appears with a Success status
- Review failures weekly — Set a reminder to check for failed executions so issues do not go unnoticed
- Use Slack notifications as a canary — Add a Slack action to critical workflows so your team gets immediate feedback when they run