GoPhish
Connect each customer's self-hosted GoPhish server so your product can launch phishing simulations, pull campaign results, and track employee click and report rates. Every customer brings their own GoPhish host; Askel keeps each connection isolated.
What you can do
Create and launch phishing campaigns
POST a new campaign to the customer's GoPhish server with a template, landing page, sending profile, and target group. Askel handles auth and translates your product's campaign spec into GoPhish's API format.
Read campaign results and event timelines
Fetch per-campaign results including email sent, opened, clicked, submitted data, and reported counts. Pull the full event timeline per recipient to see exactly which actions each user took.
Manage sending profiles
Read and create sending profiles on the customer's GoPhish instance, covering SMTP host, from address, and header configuration, so simulations appear to come from realistic internal addresses.
List and create email templates
Read existing phishing templates stored on the customer's GoPhish server, or create new ones from your product's template library. Covers HTML body, subject line, and attachment configuration.
Manage landing pages
Read and create landing pages on the customer's GoPhish instance. Landing pages capture submitted credentials (in simulation mode) and can redirect users to awareness training after submission.
Fetch target groups and individual results
Read user groups configured on GoPhish and pull per-user results across campaigns to build a risk score or track improvement over time within your product.
Running a quarterly phishing simulation as part of a security awareness programme
You sell a security awareness training platform. A customer, Whitmore Financial Services, runs their own GoPhish server inside their corporate network. Every quarter you need to run a phishing simulation against their staff, pull per-user results, and trigger remediation training for anyone who clicked.
- 1
Customer provides the API key
Whitmore's IT admin opens their GoPhish admin panel, navigates to Settings, copies the API key, and pastes it into your product's connection wizard along with their GoPhish host URL. Askel validates the connection with a GET /api/campaigns/ call.
- 2
Template and landing page sync
Askel reads the existing templates and landing pages on Whitmore's GoPhish server. Your product displays them alongside its own template library so the admin can pick or create the quarterly simulation template.
- 3
Campaign created
Your product calls Askel to POST a new campaign to Whitmore's GoPhish server with the chosen template, a landing page, the configured sending profile, and the staff target group. GoPhish schedules the send.
- 4
Results pulled daily
Askel reads the campaign's results each day during the simulation window. Your product updates its dashboard with click rates, credential-submission counts, and per-user event timelines.
- 5
Remediation training triggered
For each user who clicked, your product automatically enrols them in the next phishing-awareness module in Whitmore's training plan. Askel marks the campaign complete after the simulation window closes.
API token
Each customer provides their GoPhish server URL and the API key from their GoPhish admin Settings page. Because every customer runs their own GoPhish instance, the host URL is different per customer. Askel stores the URL and key per customer connection and sends the key as an API key header on every request to that specific host.
How Askel sits between your product and the customer's system
FAQ for GoPhish
Does the customer's GoPhish server need to be publicly accessible?+
What GoPhish version is required?+
Is the data from GoPhish stored in Askel permanently?+
Can we run simulations against multiple GoPhish servers for the same customer?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.