Asana + Grok Bot

How to connect Asana to Grok Bot

Use Grok Bot with Agent200 for read-only Asana task briefings. Check owners, deadlines and completion states with the user's own connection.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Asana tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Grok Bot for an on-demand briefing from a selected Asana task. Attach the Agent200 connector to the conversation and name the task you want. This keeps the source of the answer explicit when the Bot also has browser access or other connected apps.

Begin with one task the connected user can access. The Asana catalogue on this page is read-only: a briefing does not create, assign, complete or delete work. Discover the available tools and use their returned schemas before running the test.

Product reference: Grok Bot documentation. For Asana task fields and optional field selection, see Asana’s task-read reference.

Connector
Asana
Works with
Grok Bot ยท Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
6 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Asana enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Asana account. They approve access once, on Asana's own page.
  • 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 Asana to Grok Bot

  1. 1

    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 Asana and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    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.

  3. 3

    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.

    Add a custom connector
    MCP: Grok Bot custom connector form
    Name:          Agent200
    Type:          Remote HTTPS
    Server URL:    https://api.agent200.com/mcp/
    HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
  4. 4

    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.

  5. 5

    Step 5: Connect your Asana account

    The first time you ask Grok Bot for something in Asana, Agent200 returns an authorization link. Open it and approve access on Asana's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.

Test your connection

Run one request to check everything is wired up.

Ask

Using Agent200, read the Asana task identified in this chat. Give me a status briefing with its owner, deadline and description. Ask me to identify the task if needed. Do not use browser data or modify anything.

What should come back

  • The selected task is identified clearly.
  • The answer uses only the task information returned, including owner, due date and completion state when available.
  • Missing fields and access failures are reported without guessing; no Asana records are changed.

If authorization is requested, complete it with the intended Asana account. If a tool or field is unavailable, report it and check the actual tool definition. Workspace task search has separate premium access requirements.

Get your API key

Create a key in the Agent200 dashboard. It reaches Asana and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Asana to Grok Bot.

Agent brief
Goal: connect Asana to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/asana/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 Asana 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. The first Asana request returns an authorization link if the user has not connected Asana yet: show it to them and continue once they have approved access on Asana's own page.
5. Check it works with this request: "Using Agent200, read the Asana task identified in this chat. Give me a status briefing with its owner, deadline and description. Ask me to identify the task if needed. Do not use browser data or modify anything."
   What should come back:
   - The selected task is identified clearly.
   - The answer uses only the task information returned, including owner, due date and completion state when available.
   - Missing fields and access failures are reported without guessing; no Asana records are changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Asana, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/asana/framework/grok-bot.md

Asana tools Grok Bot can call

  • Read a task

    Read
    asana_get_task

    Retrieve an Asana task's details, including its description, assignee, due date and completion status.

  • Search tasks

    Read
    asana_search_tasks

    Search workspace tasks by text and filters. Requires Asana premium search access.

  • List project tasks

    Read
    asana_list_project_tasks

    List the tasks in a selected project, then read individual tasks for descriptions, ownership and deadlines.

  • List subtasks

    Read
    asana_list_subtasks

    List the subtasks of a parent task so your agent can inspect the smaller work items behind it.

  • List projects

    Read
    asana_list_projects

    List projects in a workspace to find the project relevant to a request.

  • Read a project

    Read
    asana_get_project

    Read a project's name and description to understand its purpose and context.

How it works

  1. 01

    You ask Grok Bot

    In your own words, for something in Asana.

  2. 02

    Grok Bot picks a tool

    It sees the Asana tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Asana connection, within the tools and scopes your project allows.

  4. 04

    Grok Bot answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Asana account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Asana enforces what its API grants.

Troubleshooting

The task is missing or cannot be read

Confirm the task ID and that the connected Asana user can open it. An access error is not an empty task. Ask for the right task rather than guessing an ID or claiming a result.

The answer omits the owner or deadline

Check the fields actually returned by the tool. An omitted field does not prove a task is unassigned or has no due date. Report unavailable information explicitly.

Task search fails even though a task read works

Asana workspace task search requires premium eligibility and may lag recent changes. Use an identified accessible task for the first test. See Asana’s search requirements.

FAQ

How do I know the answer came from this connector?

Name Agent200 and the selected Asana task in the request, and inspect the tool activity. A browser visit or a response from a different connector does not verify the Agent200 path. Check that the returned task is the one you requested.

Use Asana with another framework

200 OK

Asana, connected to Grok Bot.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)