> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/integrations/other/whatagraph.md).
# Whatagraph
Create rich dashboard visualisations of LeadBoxer data with Whatagraph
Note: you need access to the Whatagraph **Custom API Connection** feature in order to use our integration.
#### Getting Started.
1. Before you start, think about the data you want to visualise.
2. Create a segment and use the filters to narrow down the audience you want to graph out. For example everyone that downloaded a white-paper.
3. Login to Whatagraph as Admin, go to your sources page and select Custom API source and click New account.
4. Give the source a name, and when you click 'add account' you will be provided with an API key, copy this key
5. Switch to LeadBoxer and login as admin, go to the integrations page and select Whatagraph
6. Add a New Integration and fill out the steps in the form
7. Make sure the integration is enabled and Save
8. Wait 24 hours and you should see yesterday's data in Whatagraph when you use this new source.
9. You can add multiple sources per dataset, and visualise journeys etc.
For more details see:
---
# 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://help.leadboxer.com/leadboxer/integrations/other/whatagraph.md?ask=&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.
