Cyber Aware connects to Autotask through Zapier: you build a zap on Cyber Aware's phishing.campaign-completed or course.completed trigger and choose an Autotask action — a new ticket, a ticket note, a company update or a billing line item. There is no native plugin to install and no API key to write code against; the whole connection is point-and-click and most MSPs have it running in under an hour. This guide walks through the exact setup, the triggers worth wiring, and the three automations that save the most admin time.
What the integration actually does
Cyber Aware exposes every platform event as a Zapier trigger, and Autotask is one of the apps those triggers reach. In practical terms that means:
- Campaign results become tickets. When a phishing campaign completes, a zap can open an Autotask ticket with the click and report rates attached — per client, automatically.
- Course completions become ticket activity. A learner finishing a training course logs an activity note in the PSA without anyone exporting CSVs.
- New clients become billing lines. The moment a client is provisioned in Cyber Aware, an Autotask billing line item can be created so the subscription never invoices late.
The integrations page lists Autotask among the PSA category alongside ConnectWise PSA, HaloPSA, Datto and N-able, with two-way sync of companies, contacts, agreements and tickets available through the same machinery.
Before you start
- An active Cyber Aware account (any plan — Zapier access is not a top-tier feature)
- An Autotask account with API access enabled for the user you will authenticate as
- A Zapier account on a plan that covers your task volume (campaign completions generate one task per zap run)
Step 1: pick your trigger
In Zapier, start a new zap and search for Cyber Aware. The triggers relevant to Autotask sync are:
| Trigger | Fires when | Typical Autotask action |
|---|---|---|
| phishing.campaign-completed | A phishing campaign finishes | Create ticket with results |
| course.completed | A learner finishes a course | Add ticket activity note |
| client.created | A new client is provisioned | Create billing line item |
| learner.created | A learner is added | Update company contact |
| lead.created | A gap-assessment lead arrives | Create sales ticket/opportunity |
Start with phishing.campaign-completed — it is the trigger that replaces the most manual work.
Step 2: connect your accounts
Zapier asks you to authenticate Cyber Aware and Autotask once each. Cyber Aware connects with your admin credentials; Autotask uses its API-user mechanism, so create a dedicated API user in Autotask rather than tying the zap to someone's personal login — if that person leaves, your automation does not leave with them.
Step 3: map the fields
For a campaign-completed zap, map the Cyber Aware payload — client name, campaign name, click rate, report rate, date — into the Autotask ticket fields. Two mapping tips that save rework:
- Put the client name in the ticket's company reference so the ticket lands on the right account, and put the rates in the description or a user-defined field so you can report on them later.
- Use Zapier's line-item or formatter steps if you want one tidy summary instead of raw numbers.
Step 4: test and turn it on
Send a test from Cyber Aware (or use the zap's test event) and check the ticket that appears in Autotask. If it lands on the right company with readable results, publish the zap. Run the first real campaign afterwards and confirm the ticket created itself — that is your end-to-end proof.
Three automations worth copying
- Campaign results → Autotask ticket. The classic. Every client's phishing campaign closes with an evidence ticket your QBR deck can cite.
- Course completions → ticket activity. Turns training delivery into a visible service in the PSA, which supports renewals and compliance conversations.
- New client → billing line. Provision once in Cyber Aware and the subscription bills itself in Autotask — no invoice ever slips because someone forgot to add the line item.
Troubleshooting
- Zap did not fire: confirm the campaign actually completed in Cyber Aware and check the zap's task history — the error message there usually names the failing field.
- Ticket lands on the wrong company: the client name in Cyber Aware must match the Autotask account name exactly; add a lookup step if your naming differs.
- Rate limits: bulk campaign completions create one task per run — if you run hundreds of small client campaigns per day, review your Zapier plan.
FAQ
Is there a native Autotask plugin for Cyber Aware? No native plugin is needed — Cyber Aware connects to Autotask through Zapier, and everything the platform does is exposed as a Zapier trigger or action, plus a full API if Zapier is not enough.
What data moves from Cyber Aware to Autotask? Whatever the trigger payload carries: client and campaign names, click and report rates, course completions, learner additions and leads. You choose which fields map to which ticket fields.
Does the Autotask connection cost extra? Cyber Aware does not charge for Zapier access. Zapier itself bills by task volume on your Zapier plan, and Autotask requires API access on the user you authenticate.
Can Autotask changes flow back into Cyber Aware? Two-way sync of companies, contacts, agreements and tickets is available across the PSA category — for anything beyond the standard zap templates, the API covers custom flows.
How long does setup take? Most MSPs have the first zap running in under an hour: pick a trigger, authenticate both accounts, map fields, test, publish.
Related guides
One last thing
The PSA connection is what turns awareness training from a tool you run into a service you sell: tickets prove delivery every month, and billing lines prove revenue. Wire the campaign-results zap first — it is the one your clients actually see.