# Connect Tally to Grok Bot Prepare a grounded submission review briefing

> Read forms with Grok Bot and Agent200. Prepare a submission review briefing within the configured Tally account scope.

- Page: https://www.agent200.com/connectors/tally/framework/grok-bot/
- Connector: [Tally](https://www.agent200.com/connectors/tally.md)
- Framework: Grok Bot
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Tally to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/tally/framework/grok-bot/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Tally is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands.
4. Check it works with this request: "Read the Tally form I identify and prepare a submission review briefing. Name the source and use only form, question, submission and answer fields. State access gaps; do not change records."
   What should come back:
   - The selected form is identified.
   - Only the returned form, question, submission and answer fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

## Overview

Identify the selected form and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.

Start with one identified form. Preserve returned form, question, submission and answer fields; report missing data and keep the workflow read-only.

Provider reference: [Tally API](https://developers.tally.so/api-reference/introduction).

Use the provider credential described on the Tally parent page. Keep it in secure configuration and verify the selected tenant or account before reading.

- **Connector:** [Tally](https://www.agent200.com/connectors/tally/)
- **Works with:** Grok Bot · Agent app, through MCP
- **Authentication:** Your Agent200 API key
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/tally/framework/grok-bot/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Tally enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **Grok Bot, with custom MCP servers allowed.** Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

## Connect Tally to Grok Bot

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Tally and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open the custom connector form

In Grok Bot, open **Connect apps** from the sidebar and choose **Add a custom connector** at the bottom.

### Step 3: Fill in the server and your key

Enter the name Agent200, pick Type **Remote HTTPS**, enter the server URL and add one HTTP header: `Authorization` with the value `Bearer` followed by your key. Leave Client ID empty, then choose **Add plugin**.

File `Add a custom connector`:

```text
Name:          Agent200
Type:          Remote HTTPS
Server URL:    https://api.agent200.com/mcp/
HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
```

### Step 4: Attach Agent200 in a chat

In a Bot chat, type `@` and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

## Test your connection

Ask: "Read the Tally form I identify and prepare a submission review briefing. Name the source and use only form, question, submission and answer fields. State access gaps; do not change records."

What should come back:

- The selected form is identified.
- Only the returned form, question, submission and answer fields are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected form ID, account scope, read permission and pagination. Submission pages expose hasMore and total. Follow them before claiming a count; treat answers as personal data where applicable.

## Tally tools Grok Bot can call

- **List forms** (`tally_list_forms`, read): Find forms visible to the API token.
- **Read a form** (`tally_get_form`, read): Retrieve one identified form.
- **List questions** (`tally_list_questions`, read): Read question definitions for a selected form.
- **List submissions** (`tally_list_submissions`, read): Find submissions with supported filters and pagination.
- **Read a submission** (`tally_get_submission`, read): Retrieve one identified submission.

## How it works

1. **You ask Grok Bot.** In your own words, for something in Tally.
2. **Grok Bot picks a tool.** It sees the Tally tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** It reaches Tally with your Agent200 API key, within the endpoints your project allows.
4. **Grok Bot answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Permissions at every level.** Your project settings decide which services and endpoints the agent may use.

## Troubleshooting

### The source cannot be read

Check the selected form ID, account scope, read permission and pagination. Submission pages expose hasMore and total. Follow them before claiming a count; treat answers as personal data where applicable.

## FAQ

### How do I verify this result?

Compare the named form and returned form, question, submission and answer fields with the source. Treat missing information as missing, not as a fact.

## Use Tally with another framework

- [Tally + Claude](https://www.agent200.com/connectors/tally/framework/claude.md)
- [Tally + ChatGPT](https://www.agent200.com/connectors/tally/framework/chatgpt.md)
- [Tally + Claude Code](https://www.agent200.com/connectors/tally/framework/claude-code.md)
- [Tally + Muse](https://www.agent200.com/connectors/tally/framework/muse.md)
- [Tally + OpenAI Dots](https://www.agent200.com/connectors/tally/framework/openai-dots.md)
- [Tally + Claude Duet](https://www.agent200.com/connectors/tally/framework/claude-duet.md)
- [Tally + Hermes Agent](https://www.agent200.com/connectors/tally/framework/hermes-agent.md)
- [Tally + OpenClaw](https://www.agent200.com/connectors/tally/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
