> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/richpanel.md).

# Richpanel

Zigpoll offers two ways to integrate with Richpanel:

1. **Ticket Creation** — Automatically create Richpanel tickets from survey responses, complete with participant info and all submitted answers.
2. **HTTP Integration** — Display Zigpoll customer data directly within Richpanel tickets using Richpanel's HTTP Target.

You can use either or both.

> **Note:** Richpanel's developer API is available on Richpanel's Enterprise plan. You'll need API access enabled to use these integrations.

***

## Getting your Richpanel API Key

All three integrations authenticate with a single Richpanel API key (sent as the `x-richpanel-key` header — Zigpoll handles this for you).

1. Log in to Richpanel.
2. Go to **Settings → Integrations → API Keys**.
3. Create an API key and copy it.

***

## Ticket Creation

Connect your Richpanel account to Zigpoll and automatically create support tickets from survey responses. Each response generates a new ticket, complete with the survey title, participant info, and all submitted answers. If the respondent provides an email address, Zigpoll sets them as the ticket customer so the ticket is linked to their Richpanel profile.

**Step #1: Connect Richpanel in Zigpoll**

1. In Zigpoll: Click **Settings → Manage Integrations → enable the Richpanel integration**.
2. Paste the **API Key** you generated above.

**Step #2: Configure Ticket Creation**

1. Click "Click here to add a ticket configuration."
2. **Select a Survey** — Choose which survey should trigger ticket creation, or select "All Surveys" to create tickets for every survey response.

**Step #3: Configure Ticket Creation Rules**

Choose when tickets should be created:

* **Create a ticket if the survey is partially or fully completed** — A ticket is created for every response, even if the survey is not fully completed.
* **Create a ticket only if the survey is fully completed** — Tickets are only created once the participant finishes the entire survey.
* **Create a ticket only if the respondent submitted an email address** — Tickets are only created when the participant provides an email.
* **Create a ticket only if an open-ended response is submitted** — Tickets are only created when the participant writes a free-text answer.

**Step #4: Save Changes**

Click "Save Changes" to activate the integration.

**That's it.** Zigpoll will now create a new ticket in Richpanel each time a matching survey response is submitted.

### Ticket Details

Each ticket created by Zigpoll includes:

* **Subject** — "New Survey Response: {survey title}"
* **Message Body** — Survey title, participant name, all question-and-answer pairs, email address (if provided), and any metadata (UTM parameters, Shopify data, etc.)
* **Customer** — Set to the respondent's email address if available, which automatically creates or matches a Richpanel customer profile
* **Channel** — `email`

### Multiple Configurations

You can add multiple configurations to route different surveys to separate ticket workflows. Each configuration has its own survey filter and ticket creation rules.

### Behavior Tab Actions

You can also trigger Richpanel ticket creation from the **Behavior** tab on individual surveys. Add a "create richpanel ticket" action to create tickets based on specific survey logic rules, such as when a particular answer is selected or a condition is met.

***

## HTTP Integration (Display Data in Richpanel)

You can use Richpanel's HTTP Target to display Zigpoll customer data — such as sentiment and past survey responses — directly within Richpanel tickets. This is a pull-based integration where Richpanel fetches data from Zigpoll when a ticket is opened.

**Step #1: Get your Integration URL and API Key**

1. In Zigpoll: Click **Settings → Manage Integrations → enable the Richpanel integration**. Copy the generated **Integration URL** to your clipboard.
2. Scroll down to **API Keys** and create a Zigpoll API key. Copy it for later.

**Step #2: Create your Richpanel HTTP Target**

1. In Richpanel, go to **Settings → Integrations → HTTP Target** and add a new target.
2. Set the **HTTP Method** to `GET` and paste in the **Integration URL** from Step 1.
3. Map the customer email into the URL's `email` parameter using Richpanel's customer-email variable.
4. Add a header named **Authorization** with your Zigpoll API key from Step 1 as the value.
5. Subscribe the target to the **Ticket created** / **Ticket message created** events.

Once a ticket comes in, open it and drag the new Zigpoll information into the info bar so you can view satisfaction and survey data alongside the rest of your Richpanel data.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zigpoll.com/integrations/richpanel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
