> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/connect/tally.md).
# Tally
## Connection
When you're setting up your first workflow with Tally, you will need to create a [connection](https://docs.getmesa.com/going-further/credential) in order to connect MESA with Tally.
To establish your connection, login to your Tally account and navigate to Settings. Then, click API keys.
Click the Create API key button and enter MESA for the API key name, then click Create.
Once your API key is generated, copy it and paste it into the API Key field in the Tally step of your MESA workflow. Then, click Add connection to complete the process.
{% hint style="warning" %}
You will only be able to see the API key once after it's created.
{% 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://docs.getmesa.com/connect/tally.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.
