Connect Google Workspace to record Gmail phishing reports (Beta)
Beta: The Google Workspace integration is in beta. Run the connection test after setup and check the first reports in Phishing → Reported Emails.
When employees click Gmail's built-in Report phishing option on an AutoPhish simulation, AutoPhish records it as a report – just like the Outlook add-in or forwarding the e-mail to the report address. Employees don't install anything and keep using Gmail as usual.
The report still goes to Google as well, so it still appears in your Google Alert center and still helps train Gmail's filters. AutoPhish reads the User reported phishing alerts from your Alert center. It never changes or deletes them.
Before you begin
You need:
- the Admin role for your company in AutoPhish
- a Google Workspace super admin, or another admin who can manage domain-wide delegation, for step 2 below
- a Workspace admin account with access to the Alert center. AutoPhish reads the alerts on behalf of this admin.
- the domain of that admin's e-mail address verified for your company in AutoPhish – see "Step 2 – Verify your domain" in Getting Started: How to set up AutoPhish for your Company
- a Google Workspace edition that includes the Alert center. We are still confirming which editions are supported during the beta. If the connection test fails for a reason that isn't listed under Troubleshooting below, contact support.
Set up the connection
- In AutoPhish, go to Settings → Directory Sync and open Google Workspace phishing reports. The page shows a Client ID and an OAuth scope, each with a Copy button.
- In the Google Admin console, go to Security → Access and data control → API controls → Manage Domain Wide Delegation and click Add new. Paste the Client ID and the scope
https://www.googleapis.com/auth/apps.alerts, then click Authorize. - Back in AutoPhish, enter the admin's address under Workspace admin email and click Save.
- Click Test connection.
Always copy the Client ID from the settings page in AutoPhish, so it is exactly right.
The connection test
Test connection shows whether AutoPhish can reach Google with this setup. If it can, you see every User reported phishing alert from the last 7 days, with its number of messages and a result for each message:
Result | Meaning |
|---|---|
Matched by Message-ID | A simulation e-mail, recognised directly. |
Matched by subject | A simulation e-mail, recognised by recipient and subject. This is typical when your company sends simulations through its own mail server. |
Not a simulation | A real e-mail. It is recorded as an external report. |
Ambiguous | Not linked to a campaign, for safety. |
Recipient mismatch | Not linked to a campaign, for safety. |
The test shows counts and results only, never subjects or e-mail addresses. The test itself doesn't record any reports.
The connection status is Pending verification after saving, Active once AutoPhish has reached Google successfully, and Error if a check failed. Last error then shows the reason.
When reports appear
Google creates these alerts asynchronously. A report can therefore show up in AutoPhish up to a few hours after the employee clicked Report phishing. This is expected and not an error.
Where reports appear
Reports appear in Phishing → Reported Emails, alongside reports from the Outlook add-in and the report address:
- A report of an AutoPhish simulation is linked to its campaign and the employee. It counts as Reported in your reports and lowers the risk figures, like any other report of a simulation.
- A report of a real e-mail appears under External Emails.
- The Source of these reports is
google-workspace. - No raw e-mail is stored for these reports, so there is no original message to view or download.
Anonymous Mode applies to these reports the same way as to reports from other sources – see Reported Emails: Review What Your Staff Report.
Disconnect
Click Disconnect to stop recording new reports. Reports that were already recorded are kept. To also remove AutoPhish's access in Google, delete its entry under Manage Domain Wide Delegation in the Google Admin console.
Good to know
- A Google Workspace can be connected to only one AutoPhish company.
- Employees don't need to do anything differently. The report address and the Outlook add-in keep working as before.
Troubleshooting
"The admin email's domain must be a verified domain of this company"
Verify that domain in AutoPhish first, or enter an admin address on a domain that is already verified.
The test fails with "unauthorized_client" or "Client is unauthorized"
Domain-wide delegation is missing or wrong. Check step 2 again: the exact Client ID from the settings page, the exact scope https://www.googleapis.com/auth/apps.alerts, and that you clicked Authorize.
The test fails with "The caller does not have permission" or another permission error
The admin you entered in AutoPhish has no access to the Alert center, or the account was suspended or deleted. Enter an admin who has Alert center access.
"This Google Workspace is already connected to another AutoPhish company"
A Google Workspace can feed only one AutoPhish company. Contact AutoPhish support.
"The admin belongs to a different Google Workspace than this connection"
Click Disconnect, then connect again with an admin of the right Google Workspace.
"The Google Workspace integration is not enabled on this AutoPhish instance"
Contact AutoPhish support.
The test succeeds but shows 0 alerts
Nobody has reported anything in the last 7 days, or Google hasn't created the alerts yet. Ask a test user to report a simulation with Report phishing and run the test again a few hours later.
The status shows "Error" with a "Last error" text
Fix the cause using the sections above. AutoPhish retries automatically every few minutes.
If the test fails for another reason, contact AutoPhish support.
Updated on: 10/11/2026
Thank you!