Cyber Aware connects to Slack through Zapier: you build a zap on a Cyber Aware trigger — a phishing campaign completing, a learner finishing a course, a new client or a new lead — and choose a Slack action that posts the result into the channel your team actually reads. No code, no API keys, and most teams have the first alert flowing within the hour. This guide walks through the setup, the triggers worth wiring, and the three Slack automations that save the most admin time.
What the integration actually does
Cyber Aware exposes every platform event as a Zapier trigger, and Slack is one of the apps those triggers reach. In practice that means:
- Campaign results hit your channel. When a phishing campaign completes, a zap can post the click and report rates into a security channel — per client, automatically.
- Completions become channel updates. A learner finishing a training course can post a line into a training channel, keeping engagement visible without CSV exports.
- New clients and leads announce themselves. The moment a client is provisioned or a gap assessment lead arrives, Slack tells the team before the inbox does.
Slack is one of the 6,000+ apps Cyber Aware reaches through Zapier, alongside Microsoft Teams, Salesforce, HubSpot, Jira and ServiceNow — and a REST API covers anything Zapier does not.
Before you start
- An active Cyber Aware account — Zapier access is available on every plan, not a top-tier feature
- A Slack workspace where you can install the Zapier Slack app
- A Zapier plan that covers your task volume (each trigger firing creates one task)
- A channel plan. Decide which channels get which events before you build — one noisy channel defeats the purpose
Step 1: pick your trigger
| Trigger | Fires when | Typical Slack action |
|---|---|---|
| phishing.campaign-completed | A phishing campaign finishes | Post click and report summary to a security channel |
| course.completed | A learner finishes a course | Post learner and course name to a training channel |
| client.created | A new client is provisioned | Post the client name to a clients channel |
| lead.created | A gap-assessment lead arrives | Post the lead to a sales channel |
Start with phishing.campaign-completed — it is the event your security team most needs to see without opening the admin portal.
Step 2: connect your accounts
Zapier asks you to authenticate Cyber Aware and Slack once each. Cyber Aware connects with your admin credentials; Slack connects through the Zapier Slack app, which requests permission to post messages to the channels you choose. Install it with a service account rather than a personal login — if that person leaves, your alerts do not leave with them.
Step 3: map the message
For a campaign-completed zap, map the Cyber Aware payload — client name, campaign name, click rate, report rate, date — into the Slack message text. Two tips that save rework:
- Put the client name first and the rates after it, so a channel scan reads naturally: Northside IT — Xero invoice campaign: 8% clicked, 14% reported.
- If you run one channel per client, use a lookup on the client name to route the message; otherwise a single security channel with the client named in every message is simpler and easier to search.
Step 4: test and turn it on
Send a test from Cyber Aware (or use the zap test event) and check the message that appears in Slack. If it lands in the right channel with readable results, publish the zap. Run the next real campaign afterwards and confirm the alert posted itself — that is your end-to-end proof.
Three automations worth copying
- Campaign results to the security channel. Every client phishing close-out posts itself, and the channel history becomes a running evidence trail for quarterly reviews.
- Leads to the sales channel. A gap-assessment lead pings the team the second it lands — the difference between a warm conversation and a cold call a week later.
- Client created to the clients channel. New tenants announce themselves, so nobody discovers a missing onboarding two weeks in.
Troubleshooting
- Zap did not fire: confirm the campaign actually completed in Cyber Aware and check the zap task history — the error message there usually names the failing field.
- Message posted to the wrong channel: the channel is set on the action step, not the trigger; re-check it after editing the zap.
- Channel is too noisy: split events across channels (results vs leads) rather than turning alerts off — silent channels get muted, and muted channels get missed.
FAQ
Is there a native Slack app for Cyber Aware? No native app is needed — Cyber Aware connects to Slack through Zapier, and every platform event is exposed as a Zapier trigger, plus a full API if you want webhooks instead.
What data moves from Cyber Aware to Slack? Whatever the trigger payload carries: client and campaign names, click and report rates, course completions, learner additions and leads. You choose which fields appear in the message.
Does the Slack connection cost extra? Cyber Aware does not charge for Zapier access. Zapier itself bills by task volume on your plan, and Slack accepts incoming webhook messages on its free tier.
Can staff report phishing in Slack itself? Reporting happens through the Outlook and Gmail add-ins and the learner portal — Slack is where results and alerts are posted, not the report button.
How long does setup take? Most teams have the first alert flowing in under an hour: pick a trigger, authenticate both accounts, map the message, test, publish.
Related guides
- How to connect Cyberaware to Microsoft Teams for training reminders
- How to connect Cyber Aware to Autotask for ticket sync
- Human risk reporting
One last thing
The Slack connection is worth exactly as much as the channel discipline behind it: pick three events, route them to three channels, and resist the urge to wire everything. An alert you read beats a firehose you mute.