> 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/crm-donor-management/i360.md).

# i360

Connect Anedot to i360 to sync donations and supporter data into your CRM workflows and related records from Settings → Integrations → Directory.

Connect Anedot to i360 to automatically relay supporter data—such as name, email, phone, address, and occupation—from Action Pages, with contact matching and donor management through i360's CRM tools.

i360 is a CRM and digital marketing platform offering analytics, compliance, and engagement tools for free-market political organizations and commercial clients.

## Connecting Anedot to I360

Follow these steps to set up the integration:

1. In your Anedot account, go to **Settings → Integrations → Directory**.
2. Click **+ New Connection** in the top-right corner.
3. Select **i360** from the integration list.
4. Choose the Action Pages to sync. All pages are selected by default. To exclude any pages, enter their Action Page IDs (comma-separated).
5. (Optional) Limit the integration to a specific Team.
6. Enter your i360 Username and Password.
7. Click **Create integration** in the bottom-right corner to complete the setup.

You can edit Action Pages, Team settings, or credentials anytime after setup.

## Data Relays

* Anedot sends relays for both financial and non-financial Action Pages.
* Relayed fields include: Name, Employer, Occupation, Address, Email, Phone.
* If any of this data does not exactly match an existing i360 record, a new contact is created.
* After 5 consecutive relay failures, the integration is marked Inactive, and relays stop automatically.

## Finding Donors in I360

Once a relay is successful, donor contacts can be found by searching name, email, or phone:

1. In i360, go to the **Contacts** tab.
2. Click **Management** to open the Contact Management List.
3. From there, you can view, filter, and take action on donor records.

## Field Mapping

### Contact Fields

| Anedot Field                                                                          | i360 Field                                    |
| ------------------------------------------------------------------------------------- | --------------------------------------------- |
| email                                                                                 | email                                         |
| employerName                                                                          | employer                                      |
| lastName                                                                              | lastName                                      |
| firstName                                                                             | firstName                                     |
| phone                                                                                 | cellNumber                                    |
| occupation                                                                            | occupation                                    |
| address `{city}`                                                                      | mAddress\_City                                |
| address `{line1}`                                                                     | mAddress\_Line1                               |
| address `{line2}`                                                                     | mAddress\_Line2                               |
| address `{region}`                                                                    | mAddress\_State                               |
| address `{postalCode}`                                                                | mAddress\_PostalCode                          |
| i360 field — tags\* `"tags": [{"tagName": "Anedot Donor", "categoryName": "Anedot"}]` | tag `"Anedot Donor"` with category `"Anedot"` |

\* The i360 Client Services team requested tag support to help onboard shared customers. The tags here are specific to i360 and are not related to Anedot teams/tags.

## Payload Data

### Request Headers

```json
{}
```

### Request Body

```json
{
  "email": "admin@anedot.com",
  "employer": "",
  "lastName": "Dot",
  "firstName": "Annie",
  "cellNumber": "8765678987",
  "occupation": "",
  "mAddress_City": "New Orleans",
  "mAddress_Line1": "1340 Poydras St",
  "mAddress_Line2": "",
  "mAddress_State": "LA",
  "mAddress_PostalCode": "70112"
}
```

### Response Body (Success)

```json
{
  "message": null,
  "success": true,
  "personId": 1234
}
```

### Response Body (Failure)

```json
{
  "message": "Unauthorized"
}
```

### Response Status (Success)

```
200
```

### Response Status (Failure)

```
401
```


---

# 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/crm-donor-management/i360.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.