> For the complete documentation index, see [llms.txt](https://help.hummingbird.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hummingbird.co/data-integrations/how-should-i-integrate-transaction-monitoring-alerts-whats-the-recommended-data-flow.md).

# How should I integrate transaction monitoring alerts? What’s the recommended data flow?

To facilitate an AML investigation that arises from a transaction alert, we recommend using the following data flow when integrating with Hummingbird:

1. Start from the transaction(s) that triggered an alert.
2. Pull the customer profile, linked account records, and other account details for the customer that made the transaction.
3. Query for all of the customer's transactions over a recent period of time (generally the last 3-12 months of activity, but this time window is at your compliance team’s discretion).
4. Call the Hummingbird Alerts API with this information to create an alert and send the initial case information you assembled in the previous steps.

The Hummingbird Alerts API will automatically combine multiple alerts from the same customer into a single case – this is very handy for your compliance team!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.hummingbird.co/data-integrations/how-should-i-integrate-transaction-monitoring-alerts-whats-the-recommended-data-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.