Client reporting is the part of a security awareness programme MSPs quietly dread. The training runs itself; the reporting doesn't. Someone pulls scores, screenshots dashboards, pastes them into a ticket or a QBR deck - and does it again next month, for every client. Connecting Cyber Aware to HaloPSA puts the awareness-programme data where the MSP already works, so the monthly report stops being a chore.
TL;DR
- On Zapier, HaloPSA is listed as "Halo Service Solutions", with instant triggers for new and updated tickets.
- Cyber Aware exposes API and Zapier webhook access, so programme data can move into the PSA.
- The practical route is HaloPSA to Zapier to Cyber Aware - Cyber Aware's published integration list is Google Workspace, Microsoft 365, Zapier and a direct API.
- Branded client reporting (Human Risk Scores, per-client PDFs) stays in Cyber Aware; Halo keeps the ticket trail.
- Enable the Zapier module in Halo under Configuration > Integrations > Halo API > Applications, then test with one synthetic ticket.
Why this matters
Halo's own guide to the Zapier integration describes the pattern in both directions: trigger an action in another application based on an event in Halo - such as a new ticket being logged - or create an entity or ticket in Halo from an external application. That covers what an MSP actually needs: Cyber Aware events becoming HaloPSA records, and HaloPSA client records informing Cyber Aware enrolment.
There is a reporting angle as well as a records angle. Cyber Aware's Human Risk Reporting produces per-client branded PDFs - completion, engagement and risk trend - while HaloPSA holds the customer, site and service history. Connected, the monthly report generation can coincide with a ticket or note in HaloPSA, so the QBR conversation starts inside the system the client's whole history already lives in.
Who this is for
MSPs running HaloPSA who bill or report on security awareness training through Cyber Aware - especially teams where one technician owns both systems and the monthly client-report step is still manual.
Before you start
- A HaloPSA instance with the Zapier integration enabled. Halo's guide walks through the connection: search and select "Halo Service Solutions" in Zapier, authorise the connection from the account window, and manage it afterwards under Configuration > Integrations > Halo API > Applications. Only provide your tenant in the connection window if you are a cloud customer.
- A Cyber Aware partner account with API or Zapier webhook access. Cyber Aware's own comparison of white-label platforms lists its integrations as Google, Microsoft, Zapier and API - Zapier and the API are the two routes that bridge to HaloPSA.
- A Zapier account on a plan that supports multi-step Zaps.
- The gotcha: HaloPSA's Zapier triggers are instant rather than polling. That is good for ticket events, but a misconfigured Zap fires in real time - test with a synthetic ticket and a test client before pointing anything at live clients.
Step 1 - Enable the Zapier connection in HaloPSA
- In HaloPSA, open Configuration and navigate to Integrations > Halo API > Applications, where connected applications are managed.
- In Zapier, create a new Zap and search for "Halo Service Solutions" as the trigger or action app.
- Authorise the connection from the window Zapier opens. Halo's guide notes the tenant field applies to cloud customers only.
- Confirm the connection appears on the Halo side under Halo API > Applications.
Halo's API documentation also defines the authentication levels - No Authentication, User, Agent and Admin - and each resource and method is protected by a minimum level. If a Zap step fails with a permissions error, check which level the connected application was granted.
Step 2 - Choose the trigger
- Set the Zap's trigger to New Ticket or Ticket Updated - both are supported and instant.
- Run a test to pull sample data and confirm the fields populate: customer, site, ticket type, status, priority.
Expected result: the test step returns a sample HaloPSA ticket. If no sample appears, log one synthetic ticket in HaloPSA and retest - the trigger only sees events that happen after the Zap is live.
Step 3 - Push the event into Cyber Aware
- Add an action step to the same Zap: Cyber Aware, using the API or webhooks integration.
- Map the client identifier - customer name or site - to the matching Cyber Aware client, and choose what should happen: create a record, tag the client, or store the reporting-cycle reference.
- Save and test the action with the sample record.
Expected result: a test record appears against the matching client in Cyber Aware. From that point the programme runs itself - monthly courses auto-add, due and overdue reminders fire on schedule, and completed courses issue branded certificates under the MSP's brand.
Step 4 - Make reporting automatic, not just connected
- In Cyber Aware, schedule the client summary report to generate on a fixed date each month - the training portal's automation is built for exactly this cadence.
- Point Cyber Aware's outbound webhook at a second Zap whose action is HaloPSA's Create Ticket, so a ticket appears in the PSA when the reporting cycle completes.
- Export the branded PDF from Cyber Aware and attach it to that ticket, so the PSA shows both the delivery and the artefact.
The reporting artefacts stay in Cyber Aware; HaloPSA holds the delivery trail. That separation is deliberate - the PSA is the system of record, the awareness platform is the source of truth for the numbers.
Verification and a clean rollout
- Pick one test client with no live users.
- Log a synthetic ticket in HaloPSA and watch the Zap land in Cyber Aware.
- Run one reporting cycle manually and confirm the HaloPSA ticket appears.
- Switch live clients on one at a time.
Troubleshooting
- The Zap doesn't fire on a new ticket. The trigger only sees events after activation. Log a fresh synthetic ticket and retest.
- A step fails with a permissions error. HaloPSA's API resources are protected by minimum authentication levels - No Authentication, User, Agent, Admin. Check the application's level under Halo API > Applications.
- The Cyber Aware action errors on create. A mapped field is empty - usually the client name. Match the name in HaloPSA to the Cyber Aware client exactly, or map on a shared reference field.
- Duplicate notes every cycle. The Zap fires on Ticket Updated as well as New Ticket. Keep one trigger per Zap, or add a filter step.
What to do next
Reporting is only as good as the programme behind it. If clients question the numbers, show them the source: Human Risk Reporting explains how the score is built from real training and phishing behaviour. If the programme itself still has manual corners, security awareness training covers the automation that runs enrolment, reminders and certificates hands-off.
FAQ
Can Cyber Aware connect to HaloPSA directly?
No native HaloPSA connector appears in Cyber Aware's published integration list - Google Workspace, Microsoft 365, Zapier and a direct API. HaloPSA's Zapier app plus Cyber Aware's API or webhooks is the supported route.
What is HaloPSA called on Zapier?
"Halo Service Solutions" - HaloPSA's maker publishes the app under that name, and its page shows supported triggers and actions including New Ticket, Ticket Updated, Create Customer, Create Site, Create End User and Create Ticket.
Do I need HaloPSA admin rights?
To enable and manage the integration you work in Halo's configuration area, where the connected application appears under Halo API > Applications. Halo's API defines minimum authentication levels per resource, and the application needs the level your Zap's steps require.
How fast do events flow?
HaloPSA's Zapier triggers are instant rather than polling, so a ticket event reaches the Zap in seconds.
Is the client reporting branded?
Yes - Cyber Aware's portals, notification emails, reports and certificates carry the MSP's brand, and the per-client PDF export is built for the client conversation, not a raw data dump.
Can the direction be reversed - HaloPSA to Cyber Aware?
Yes. Halo's Zapier actions include Create Customer, Create Site and Create End User, so a new client set up in HaloPSA can drive Cyber Aware onboarding - the same pattern as this guide with the arrow pointing the other way.
One last thing
A connected report nobody reads is no better than a manual report nobody reads. The monthly report earns its keep when it opens a conversation - the risk snapshot, the leaderboard, the trend line. Automate the delivery, but keep the interpretation human; that is the part clients actually pay for.