> 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/relay-data-troubleshooting/integration-requests.md).

# Integration Requests

Review, filter, and export integration relays in Settings > Integrations > Integration Requests, and resend failed relays with Push unsent in your account.

**Integration Requests** is the delivery log for your integrations. Each time Anedot sends a record to a connected tool, the attempt shows up here as a relay, with its status, the request we sent, and the response we got back. Go to **Settings > Integrations > Integration Requests**. The page is titled **Integration relays**. This article covers how to find and review relays, export them, and resend failed relays.

## Before You Begin

* To view Integration Requests, you need **Integrations: View** permissions.
* To export relays, you need **Integrations: Export** permissions.
* To resend failed relays with **Push unsent**, you need **Integrations: Edit** permissions.

See [Permission Sets](https://docs.anedot.com/settings/access/permission-sets.md).

## Find A Relay

The list shows each relay's **Created** date, **ID**, **Product**, **Name**, **Connection**, and **Status**, with the newest first.

To find a relay:

1. Go to **Settings > Integrations > Integration Requests**.
2. Enter a relay ID or submission ID in the search box.
3. To narrow the list, click **Filter**, choose your filters, and apply them.

| Filter                  | What It Does                                                           |
| ----------------------- | ---------------------------------------------------------------------- |
| Start date and End date | The date range to show. Defaults to the last 30 days.                  |
| Relayed entity type     | Submission, Donation, ActionPagesCommitment, or ActionPagesRecurrence. |
| Integration service     | The connected tool, such as Mailchimp.                                 |
| Integration ID          | One specific integration.                                              |
| Product type            | Action Pages or Campaigns.                                             |
| Status                  | Success, Failure, or Error.                                            |

## Review A Relay

To review a relay, click **View details** in its row. The details show the **Request headers**, **Request body**, **Response status**, and **Response body**.

Use the response to see why a relay failed:

* A response status from 200 to 299 means the connected tool accepted the record.
* A status of 400 or higher means it didn't. For example, 401 usually means the login details saved on the integration are wrong.
* The response body often includes the connected tool's own error message.

## Export Relays

Click one of these buttons at the top of the page:

* **Export all:** Exports the relays that match your current filters. The message "Integration relay export started." appears.
* **Export failed:** Exports only failed relays that match your current filters. The message "Failed relay export started." appears.

## Resend Failed Relays

**Push unsent** resends relays that failed for one integration during a date range. Successful relays aren't sent again.

To resend failed relays:

1. Go to **Settings > Integrations**.
2. In the integration's row, click **Push unsent**.
3. Enter a **Start date** and **End date**. The range can be up to 31 days, the start date can't be more than 12 months ago, and the end date can't be later than today.
4. Click **Push unsent** to confirm.

The message "Push started." appears. You can start another push for the same integration 5 minutes after the last one.

## Common Causes of Failed Relays

* **Incorrect login details:** Check the account name, username, password, or API key saved on the integration. A 401 response usually points to this.
* **Page scope:** Check whether the integration is set up for all pages or only one page. Records from pages outside its scope aren't sent.

If relays keep failing, contact our Support team at <help@anedot.com>.

## Related Articles

* [Integrations](https://docs.anedot.com/integrations.md)
* [Webhooks (API)](https://docs.anedot.com/integrations/integration-automation-tools/webhooks.md)
* [Zapier](https://docs.anedot.com/integrations/integration-automation-tools/zapier.md)
* [Permission Sets](https://docs.anedot.com/settings/access/permission-sets.md)


---

# 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/relay-data-troubleshooting/integration-requests.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.
