Skip to main content
Triggr works with Proofpoint Essentials organisations, users and user sync exemptions.

​
Set up Proofpoint Essentials

1

Choose an admin account for Triggr

Use an Organization Admin for one organisation, or a partner admin (such as Channel Partner Admin) for every organisation under your partner account. End users can’t use the API. Proofpoint lets you mark one admin per organisation as a Service Account, which isn’t billed.
2

Note your Proofpoint address

It’s the one you sign in to, such as https://us1.proofpointessentials.com or https://eu1.proofpointessentials.com.
See Proofpoint’s API documentation.

​
Connect it in Triggr

1

Open the configuration

Go to Integrations > Proofpoint Essentials and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the address and account

Enter your Proofpoint address as Hostname, with https:// and no path, the admin’s Password, and their email address as Username. Click Save Configuration.
The Proofpoint Essentials configuration window with Hostname, Password and Username fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
Actions take the organisation’s domain, such as example.com. Get Endpoints returns the Proofpoint address that serves a domain.

​
Troubleshooting

Check Username is the admin’s full email address, Password is current, and the account is an admin rather than an end user.
The account can’t manage that organisation. Use an admin of the organisation, or a partner admin above it.
Hostname must start with https:// and have no trailing / or path. Run Get Endpoints for the domain to check the address.