> 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/political-campaign-tools/directsnd.md).

# DirectSnd

Anedot integrates with DirectSnd to send supporter data from Donation and Lead Pages for SMS marketing campaigns via Settings → Integrations.

Anedot integrates with DirectSnd to send supporter data from Donation and Lead Pages for SMS marketing campaigns.

DirectSnd is an SMS marketing platform that helps you reach supporters through text messaging.

### How It Works

Anedot sends supporter data from **Donation** and **Lead Pages** to DirectSnd once the integration is connected.

* Custom field data is *not* sent.
* International phone numbers are *not* supported and will fail to relay.

## Connecting Anedot to DirectSnd

Follow these quick steps to set up the integration:

1. Go to **Settings → Integrations → Directory** in your Anedot account.
2. Click **+ New Connection**.
3. Select **DirectSnd** from the list.
4. Choose which **Action Pages** to connect:
   * All are selected by default.
   * To exclude pages, enter a comma-separated list of their IDs.
5. *(Optional)* Limit the sync to a specific **Team**.
6. Enter your **DirectSnd API Key**.
7. Click **Save** in the bottom-right corner.

*You can update Action Pages, Team settings, or API credentials anytime after setup.*

## Field Mapping

### Relay Fields

The Anedot Fields match the Submission's Raw Data and the DirectSnd Fields match the Request Body relay.

| Anedot Field         | DirectSnd Field   |
| -------------------- | ----------------- |
| address {city}       | city              |
| email                | email             |
| address {region}     | state             |
| phone                | number            |
| address {postalCode} | zip\_code         |
| lastName             | last\_name        |
| firstName            | first\_name       |
| "Anedot"             | opt\_in\_method   |
| address {line1}      | address\_line\_1  |
| "False"              | is\_black\_listed |
| "False"              | message\_supress  |

## Payload Data

### Request Headers

```
{}
```

### Request Body

```json
{  "city": "New Orleans",  "email": "admin@anedot.com",  "state": "LA",  "number": "2251231234",  "zip_code": "12345",  "last_name": "Dot",  "first_name": "Annie",  "opt_in_method": "Anedot",  "address_line_1": "1239 First St",  "is_black_listed": "False",  "message_supress": "False"}
```

### Response Body (Success)

```json
{  "detail": "We are processing your request. Thank you!",  "status": "Success"}
```

### 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/political-campaign-tools/directsnd.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.