đ¤ Only Managers and Technical Admins can access automation logs in Hook
View Run History with Automation Logs
Automations in Hook run across accounts, users or contacts automatically. But knowing which accounts have been processed - and whether each step succeeded or failed - has historically required digging around to find out.
Automation logs are Hook's record of every time an automation fires. They show you which accounts were picked up, what actions were taken, and whether each action succeeded or was skipped.
Related Article: Automations Troubleshooting
When to use Automation Logs
Viewing logs will help in the following scenarios:
Viewing performance across all automations
Checking whether a specific account has been processed by an automation
Investigating why an automation didn't complete an action for an account you expected it to cover
Confirming that outreach emails were triggered correctly
Troubleshooting a failing step without raising a support request
How to Find Automation Logs
All Automations Activity - At a glance
To view the activity across all automations in one view, go to Organisation settings > Automations:
Activity: The total number of actions completed (e.g. Slack messages sent, signals created etc) for the selected period
Green tick: Successful runs of the automation
Red warning: Errored runs of the automation
Grey tick: The automation is yet to run (set to inactive or no triggers have been satisfied yet)
Show activity for: Filter to control the period of activity to show automation logs for (up to the last 180 days).
Example automation activity view with total runs for the last 7 day period
Single Automation Activity - Detailed View
Automation logs can be viewed at the trigger or action level level.
Logs for automation triggers show the total number of entities that satisfy the conditions of the trigger e.g. total accounts matching Customers table filters.
Logs for automation actions show a detailed view of each timestamped automation run and the status.
For each separate automation trigger in If... and action in the Then... section, you can see the history of automation runs.
Select an automation in Automation settings
Click the three dots next to an automation action or trigger
Select View activity
Click the three dots next to an automation action to view the logs
Log Components
The following information is available in automation logs for individual automations (actions or triggers):
Date: The date of the automation run
Status:
Success: Automation run successfully
Error: Automation errored, with the given error message
Skipped: Automation succeeded previously and automation will not re-try on the same entity based on automation set not to re-run if conditions haven't changed
Info: For triggers only - no action completed, informational output
Closed: Signal closed (signal automations only)
Customer: Link to the Hook account page for the corresponding account run
User or contact: Link to user or name of contact for the corresponding run
Details: More information on the status. If the run failed, the error message is displayed here.
Example logs for the Activate an agent action
Example logs for the An external activity is received trigger
Filtering Logs
To view the most relevant automation logs, the view for logs from automation actions can be filtered in the following ways:
Status: Only view Errors or Successes for automations
Show activity for: Change the time period of logs viewed (up to 180 days ago)
Customer, User or Contact: Filter for specific entities. E.g. See how many times a detected signal was created for a specific account
Retries
The automation logs can be filtered to remove runs with the Skipped status by selecting Hide retries. Skipped runs of an automation indicates no change, but is an informative log to see that, while the customer, contact or user did match the triggers for the automation, no action was taken since action was taken on a previous run.
Whether an automation run is skipped is determined by the setting for When to recreate in the automation action. If this is set to Never, then the automation will show skipped runs.
Checking Whether an Account Was Processed
Select an automation in Automation settings
Click the three dots next to an automation action
Select View activity
Search for the account name in the Customer filter
Investigating a Failed or Skipped Action
Select an automation in Automation settings
Click the three dots next to an automation action
Select View activity
Apply a filter for Status: Error to view failed automation logs
Confirming Outreach Was Sent
Select an automation in Automation settings
Click the three dots next to an automation action
Select View activity
For Slack notifications, the log will show the specific channels and people the message was sent to.
For automated emails set up as draft Actions, confirm the draft was created for review before being sent.
đĄ Automations run every two hours, and immediately after an automation is created. If you've just activated an automation and don't yet see log entries, wait for this interval to pass before investigating further.
âFrequently Asked Questions
Why didn't my automation fire for a specific account?
Check the run log for that automation. If the account appears with a skipped action, the log will show an explanation of why the step didn't execute in Details - for example, a condition wasn't met or a user wasn't found. If the account doesn't appear at all, check your trigger conditions and filters. See Automations Troubleshooting for a full checklist.
Why can't I see the Logs button?
Only Managers and Technical Admins can access automation settings and logs. If you don't have this access, ask your manager or a Technical Admin to review the log on your behalf.
How far back do run logs go?
You can see logs up to 180 days in the past.
Do logs show which accounts did NOT go through an automation?
Logs record the accounts that were evaluated and the outcome for each. If an account was never picked up by the automation's trigger conditions, it won't appear in the log at all. To understand why an account was excluded, review the automation's trigger and filter settings.



