> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/tutorials/building-an-email-integration.md).

# Building an Email Integration

This tutorial aims to guide a first-time Integration Gateway user through the process of building a real integration, step by step, from start to finish. This integration will take an email address as input, then query the [Hacker News API](https://github.com/HackerNews/API) for articles, and finally email a list of article URLs to the provided address.

Upon completion of the tutorial, the reader will understand:

* integrations, as well as how to build one,
* how to use the Admin site to configure Integration Gateway components,
* how to validate the data that passes through Integration Gateway,
* how to visualize that data at every step,
* how to trigger integrations,

and more generally, the *awesome power of* Integration Gateway!

{% hint style="warning" %}
The reader will need the following before starting:

* A Integration Gateway user account with admin privileges
* A Gmail/Google account
* A basic understanding of JSON and HTTP (helpful but not 100% required)
* Basic skills in the Python programming language (helpful but not 100% required)
  {% endhint %}


---

# 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://glyue.docs.sandboxbanking.com/tutorials/building-an-email-integration.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.