> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/rewst-documentation/documentation/integrations/integration-guides/proofpoint-integration-setup.md).

# Proofpoint integration

{% hint style="info" %}
If you’re new to integrations in Rewst, read through our introductory integration documentation [here](https://docs.rewst.help/documentation/integrations).
{% endhint %}

## What does the Proofpoint integration do?

Our Proofpoint integration enables the automation of email security and compliance. Use the Proofpoint API within Rewst workflows to manage organizations and users.

## Set up the Proofpoint integration

### Set up steps in Rewst

1. Navigate to **Integrations** in the left side menu of your Rewst platform.
2. In the Integrations page, search for the `Proofpoint` integration.
3. Click on the integration tile to launch the configuration setup dialog.
4. Choose from either Production or Demo Mode for the setup of your integration:
   1. **Production**: Connect with real credentials for live data
   2. **Demo Mode**: Explore the integration with simulated mock responses
5. Click **Next: Configure and Authenticate**.
6. Select **+ Create New Credential from the Credential** drop-down selector. 
7. Enter the following information into the relevant fields:
   1. **Stack hostname**: Use the drop-down selector to choose the Proofpoint Essentials stack your partner account lives on, e.g. `us1.proofpointessentials.com`; credentials only validate against their own stack; `GET /endpoints/{domain}` reports the right one
   2. **Username**: The Proofpoint API Username; this must be a channel admin user in Proofpoint
   3. **Password**: The password you use for that user in Proofpoint
   4. **Primary partner domain**: Your partner/channel organization's primary domain, e.g. `msp.example`; Org Mapping discovery lists your client organizations from `GET /orgs/{partner domain}/orgs`; Get Me (/me) reports it as `entity_primary_domain`
8. Click **Save Credential**.
9. Click **Authorize**. This will launch a dialog to log in to Pax8. Complete login and authorization in this dialog.
10. Return to the Rewst platform.
11. Click **Next: Confirm**.
12. Click **Install Integration**. The integration will now appear in the top Connected section of your Integrations page. 

{% hint style="success" %}
Got an idea for a new Integration? Rewst is constantly adding new integrations to our integrations page. Submit your idea or upvote existing ideas here in our [Canny feedback collector](https://rewst.canny.io/integrations).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/rewst-documentation/documentation/integrations/integration-guides/proofpoint-integration-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.