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

# Mixmax

Integration with Mixmax for enrolling prospects in sequences, sending email, automating rules, and reporting on sequence engagement.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Mixmax    | API Token      |

#### Mixmax

Connect to Mixmax with an API token to enroll prospects in sequences, send email, automate rules, and pull sequence engagement reports.

**Set up in Mixmax**

1. Prepare the Mixmax account or service that the workflow will access. Grant access to the required resources and operations.
2. **API Token:** Your Mixmax API token, from Settings > Integrations in Mixmax. Mixmax shows this token only once, so save it somewhere safe when you generate it.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Mixmax**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                            |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| API Token     | Yes      | Your Mixmax API token, from Settings > Integrations in Mixmax. Mixmax shows this token only once, so save it somewhere safe when you generate it. [Provider instructions](https://mixmax.com/app/settings/integrations). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Mixmax** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Enroll Recipient in Sequence

Enroll a prospect into a Mixmax sequence by email.

**Inputs**

| Field                     | Type            | Required | Description                                                                                                                                                                                        |
| ------------------------- | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Sequence                  | select (string) | Yes      | The sequence to enroll the prospect into. Options load from the selected connection.                                                                                                               |
| Email                     | string          | Yes      | Email address of the prospect to enroll.                                                                                                                                                           |
| Personalization Variables | textarea        | No       | Merge-field values for this recipient, as a JSON object. Each sequence defines its own variables — run List Sequences to see which ones this sequence needs. Leaving one out stops the enrollment. |
| Scheduled At              | datetime        | No       | When the first email should go out. Leave empty to enroll and start immediately.                                                                                                                   |

**Outputs**

| Field        | Type   | Description                                  |
| ------------ | ------ | -------------------------------------------- |
| Recipient ID | string | The enrolled recipient's Mixmax id.          |
| Email        | string | The enrolled prospect's email address.       |
| Sequence ID  | string | The sequence the prospect was enrolled into. |
| Status       | string | Enrollment outcome for this recipient.       |

#### List Sequences

List sequences in your Mixmax account, optionally filtered by name or folder.

**Inputs**

| Field         | Type            | Required | Description                                                                                    |
| ------------- | --------------- | -------- | ---------------------------------------------------------------------------------------------- |
| Name contains | string          | No       | Only return sequences whose name contains this text.                                           |
| Folder        | select (string) | No       | Limit to your personal sequences or shared team sequences. Available values: Personal, Shared. |
| Page cursor   | string          | No       | Pagination cursor from a previous call to fetch the next page.                                 |

**Outputs**

| Field       | Type          | Description                                        |
| ----------- | ------------- | -------------------------------------------------- |
| Sequences   | object\_array | The list of matching sequences.                    |
| Next cursor | string        | Pass this back as the cursor to get the next page. |

#### Send Email

Send a one-off email through your connected Gmail account. The message is tracked by Mixmax, so opens and clicks show up in your Mixmax analytics.

**Inputs**

| Field   | Type     | Required | Description                          |
| ------- | -------- | -------- | ------------------------------------ |
| To      | string   | Yes      | Recipient email address.             |
| Subject | string   | Yes      | Email subject line.                  |
| Body    | textarea | Yes      | The email body. HTML is supported.   |
| CC      | string   | No       | Comma-separated CC email addresses.  |
| BCC     | string   | No       | Comma-separated BCC email addresses. |

**Outputs**

| Field      | Type    | Description                                     |
| ---------- | ------- | ----------------------------------------------- |
| Success    | boolean | Whether Mixmax accepted the email for delivery. |
| Message ID | string  | Mixmax's id for the sent message.               |

#### Create Automation Rule

Create a rule that POSTs to a webhook of your choice whenever a chosen email event happens (a message is sent, a reply comes in, and so on).

**Inputs**

| Field         | Type            | Required | Description                                                                                                             |
| ------------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| Rule Name     | string          | Yes      | A name for this rule, shown in the Mixmax Rules dashboard.                                                              |
| Trigger Event | select (string) | Yes      | The email event that triggers the rule. Available values: Message sent, Message received, Replied, Unopened, Poll vote. |
| Webhook URL   | string          | Yes      | The HTTPS URL Mixmax will POST the event payload to.                                                                    |
| Filter        | textarea        | No       | Optional JSON filter to narrow which events fire the rule.                                                              |
| Create Paused | boolean         | No       | Create the rule in a paused state so it does not fire until you enable it. Default: false.                              |

**Outputs**

| Field         | Type    | Description                                                      |
| ------------- | ------- | ---------------------------------------------------------------- |
| Rule ID       | string  | Mixmax's id for the created rule.                                |
| Action ID     | string  | Mixmax's id for the attached webhook destination, when returned. |
| Rule Name     | string  | The rule name, echoed back.                                      |
| Trigger Event | string  | The trigger event, echoed back.                                  |
| Paused        | boolean | Whether the rule was created paused.                             |

#### Get Sequence Report

See how a sequence is performing: sent, opened, clicked, replied, bounced.

**Inputs**

| Field      | Type            | Required | Description                                                                                                                   |
| ---------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Sequence   | select (string) | Yes      | The sequence to report on. Options load from the selected connection.                                                         |
| Date Range | select (string) | No       | How far back to measure engagement. Available values: Last 7 days, Last 30 days, Last 90 days, All time. Default: last30days. |

**Outputs**

| Field       | Type    | Description                                   |
| ----------- | ------- | --------------------------------------------- |
| Sequence ID | string  | The sequence this report covers.              |
| Sent        | integer | Emails sent from this sequence in the window. |
| Delivered   | integer | Emails delivered in the window.               |
| Opened      | integer | Emails opened in the window.                  |
| Clicked     | integer | Links clicked in the window.                  |
| Replied     | integer | Replies received in the window.               |
| Bounced     | integer | Emails that bounced in the window.            |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/mixmax.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.
