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

# SendPulse

Connect Anedot to SendPulse to sync donor data from Action Pages to your mailing lists. Step-by-step guide to setup, credentials, and contact syncing.

Connect Anedot to SendPulse to sync donor data from Action Pages to your mailing lists. Step-by-step guide to setup, credentials, and contact syncing.

**SendPulse** is a digital marketing platform and CRM that enables organizations to reach their supporters through multiple channels, including **email**, **messaging apps**, and **chatbots**. Anedot’s integration allows you to automatically send donor data from Action Pages to your SendPulse mailing lists.

## Connecting Anedot to SendPulse

To integrate your Anedot fundraising account with SendPulse:

1. Navigate to **Settings → Integrations → Directory** in your Anedot account.
2. Click the blue **+ New Connection** button in the upper right corner.
3. Select **SendPulse** from the integration directory.
4. Choose the **Action Pages** you want to sync with SendPulse *(default: all Action Pages)*.
   * To exclude specific pages, enter a **comma-separated list** of Action Page IDs.
5. *Optionally*, restrict the sync to a specific **Team**. If no Team is selected, all listed pages will be included.
6. Enter**SendPulse Credentials**
   * **List ID**: The ID of the mailing list where new contacts will be added.
   * **Client ID**: Found in **Account Settings → API tab** within SendPulse.
   * **Client Secret**: Also found in **Account Settings → API tab**.
7. Click **Save** to activate the connection.

*You can modify the synced Action Pages, Team, or credentials at any time.*

## Data Relays

* **Supported Pages**: We relay data from both **financial** and **non-financial** Action Pages.
* **Push Unsent Feature**: Use the **Push Unsent** tool to retry failed or unsent donations with a selected date range (available for financial pages only).

## View Data in SendPulse

Once data is successfully relayed:

* Go to your **Mailing List** in SendPulse.
* Navigate to the **Contacts** tab to view imported donor records.

## Field Mapping

### Contact Fields

| Anedot Field         | SendPulse Field |
| -------------------- | --------------- |
| email                | email           |
| address {postalCode} | zip             |
| address {city}       | city            |
| created\_at          | date            |
| “firstName lastName” | name            |
| phone                | phone           |
| address {region}     | state           |
| total\_amount (x100) | amount          |
| address {line1}      | street          |
| address {line2}      | street2         |

## Payload Data

### Request Headers

```
{ }
```

### Request Body

```json
{  "emails": [{    "email": "admin@anedot.com",    "variables": {      "zip": "70112",      "city": "New Orleans",      "date": "2023-02-09T21:48:41.586Z",      "name": "Annie Dot",      "phone": "2252501301",      "state": "LA",      "amount": 50.0,      "street": "1340 Poydras St",      "street2": null    }  }]}
```

### Request Body *(Error)*

```
null
```

### Response Body *(Success)*

```json
{  "result": true}
```

### Response Body *(Error)*

```
{ }
```

### Response Status *(Success)*

```
200
```

### Response Status *(Error)*

```
null
```


---

# 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.anedot.com/integrations/email-marketing-communication/sendpulse.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.