> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/pandium-integration-tutorial.md).

# Pandium Integration Tutorial

This tutorial will walk you through your first integration, and see how all the pieces of Pandium work together. During this process, you will touch a large portion of the Pandium platform and publish your first integration in less than a day.

In it, you will create a Pandium integration that sends a Slack message about a new Pokémon each day!

Check out Part 1, where you'll create a fully-functional integration from start to finish:

{% content-ref url="/pages/ysJeGqtiGy9kEcRNd4Bu" %}
[Pokémon of the Day, Part 1](/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1.md)
{% endcontent-ref %}

Check out Part 2, where you'll learn how to configure more advanced options of an integration:

{% content-ref url="/pages/RZrnYC1w5wfpyIAf55rF" %}
[Pokémon of the Day, Part 2](/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-2.md)
{% endcontent-ref %}


---

# 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.pandium.com/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/pandium-integration-tutorial.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.