Enabling direct campaign email delivery through INKY

Overview

The INKY integration connects BullPhish ID (BPID) with INKY's email protection platform, enabling direct campaign email delivery to protected targets without routing through SMTP. This integration enables Partner Administrators to synchronize organizations from INKY, monitor protection status per organization, and ensure campaign emails reach every target through the most appropriate delivery path.

Key capabilities

  • Direct INKY delivery: Campaign emails sent to INKY-protected targets bypass SMTP and are delivered through the INKY integration, improving deliverability and traceability.
  • Mixed-mode delivery: When an organization contains both protected and unprotected targets, BPID automatically routes protected targets through INKY and unprotected targets through SMTP without interrupting the campaign.
  • Organization status tracking: The integration continuously synchronizes organization protection state and displays one of four statuses — Active, Partially Active, Inactive, or Error — so you can identify and resolve coverage gaps.
  • Unprotected target export: For Partially Active or Error organizations, you can download a CSV listing every unprotected target, making it straightforward to remediate missing INKY coverage.
  • Credential lifecycle management: You can update, replace, or revoke the INKY application programming interface (API) key at any time. If credentials fail, BPID falls back to SMTP and alerts you with a banner and an error status.
  • Mutual exclusivity with Graphus: INKY and Graphus cannot be active simultaneously. BPID enforces this constraint and guides you through disconnecting one integration before enabling the other.

How it works

After you enter and verify a valid INKY API key, BPID begins synchronizing organizations from your INKY account. For each synchronized organization, BPID compares the active targets in that organization against the domains and inclusion groups configured in INKY. Targets whose email domains match an INKY-configured domain and belong to the billing-eligible inclusion group are classified as protected. All others are classified as unprotected. BPID then assigns a status to each organization based on that comparison.

When a campaign runs, BPID consults the current protection classification for each target and routes the email through INKY or SMTP accordingly. Synchronization runs on a schedule and can also be triggered manually, keeping statuses current as your target list and INKY configuration change.

Campaign delivery information is available on the Training & Awareness Dashboard, Phishing Dashboard, and the details page for each campaign. For more information, see the section Campaign delivery information.

INKY integration page

The INKY Integration page contains the API key setup controls and the synchronized organization table.

API key setup

The API key setup section contains the controls used to authenticate BPID with your INKY account and manage the connection.

Field Description
API Key The INKY API key used to authenticate and connect BPID to your INKY account. Required. Type the key provided by INKY. After successful verification, this field can be updated to rotate or replace the key.
Region The INKY server region associated with your account. Required. Select US or Europe. After successful verification, this field becomes read-only and cannot be changed without re-verifying with a new key.
Verify Submits the API key and region to INKY for authentication. A successful verification connects the integration and starts the initial organization synchronization.
Sync Now Manually triggers an organization synchronization. Displays the date and time of the most recent completed sync. Available only when the integration status is Connected.

Connected Organizations table

The Connected Organizations table lists every organization synchronized from your INKY account and shows the current protection status and delivery routing for each.

Field Description
Associated Organization The name of the organization as returned by INKY. Used as the primary identifier in the organization table and as a filter and sort option.
Status The current protection status of the organization. Possible values:
  • Active: All active targets in the organization are protected by INKY. Campaign emails route through INKY.
  • Partially Active: Some active targets are protected and some are not. Protected targets route through INKY; unprotected targets route through SMTP.
  • Inactive: The organization has no active targets or the organization has not yet been synced.
  • Error: Active targets exist but none are protected by INKY, or a sync failure occurred. All campaign emails for this organization route through SMTP.
Updated The date when the organization's status last changed. If a sync completes without changing the status, this date remains unchanged. Hover over the column header for a full description of this behavior.
Download Downloads a Comma-separated Values (CSV) file named "Unprotected users" listing every active target in the organization whose email domain is not covered by the INKY configuration. Available only for organizations in Partially Active or Error status.

Campaign delivery information

Campaign dashboards

With the INKY integration, there may be times when campaign emails were delivered via standard SMTP when delivery through INKY was expected. The Email Fallback column on the Training & Awareness Dashboard and the Phishing Dashboard provides clear visibility into the number of targets whose campaign emails were delivered via standard SMTP when INKY delivery could not be utilized.

The following conditions can cause campaign emails to be sent through SMTP, resulting in the Email Fallback field displaying the number of affected targets (for example, "18 targets"):

  • Integration Status in Error: Partner integration is down.
  • Uncovered Domains: Target email domain is outside INKY protected domains.
  • Upstream/Microsoft Failures: Delivery fails on Microsoft side during active integration.

Campaign details page

On each campaign's details page, the Sent At column shows a delivery-channel icon (INKY / SMTP / Graphus) for each email row and each resend log row.

For more information about the Email Fallback column and the Sent At column, see:

How to...

IMPORTANT  To configure the integration, you must complete the "Generate an API Key in INKY" and "Connect the INKY Integration" procedures. All other procedures are optional and depend on your organization's requirements.

FAQ

 

Revision Date

Initial release.

10/19/26