Help Documentation  / Automate & connect

Connect GrokBot to IterDone

Add IterDone as a custom connector in GrokBot: paste the server URL, sign in, approve access, then ask GrokBot to read and update your tasks.

What it does

Adds IterDone as a custom connector in GrokBot so it can read and update your spaces, lists, tasks, comments and docs in a conversation. You sign in and approve access once, no API key to copy.

Who needs it

Anyone who uses GrokBot and wants to ask it about their work, or have it create and update tasks, without leaving the chat.

Why use it

GrokBot acts as you, with your role and your permissions, limited to the read or write scope you approve. Each connection shows up as its own entry under Admin > API Keys and can be revoked at any time.

How it works

Connecting takes about a minute. The server URL to enter is https://iterdone.com/mcp (no /task or workspace name in it).

  1. Open the connector picker. In GrokBot, click Connect apps (bottom left), scroll to the bottom of the list, and click Add a custom connector.
GrokBot connector picker with the Add a custom connector button circled in red at the bottom.

Connect apps > Add a custom connector.

  1. Name it and paste the URL. Name: IterDone. Type: Remote HTTPS. Server URL: https://iterdone.com/mcp. Leave HTTP headers and Client ID empty, then click Add plugin.
GrokBot Add a custom connector dialog with Type Remote HTTPS and Server URL iterdone.com/mcp; HTTP headers and Client ID left empty.

Name, type Remote HTTPS, and the server URL. The red "already exists" notice in this capture only appears if a connector with that name is already added.

  1. Sign in and allow access. GrokBot sends you to IterDone. Sign in if you are not already, check the workspace and return site on the consent page, then click Allow access. GrokBot shows the connector as connected.

Check it works. Start a new chat, enable the IterDone connector, and ask GrokBot to run whoami or list_spaces. Data coming back means the connection works. The connection also appears as a "Connector: ..." row under My API Keys.

Try it. Ask for things like:

  • "What tasks are assigned to me and due this week?"
  • "Create a task called 'Review Q4 budget' in the Finance list, due Friday, and assign it to me."
  • "Mark the 'Launch checklist' task as In Progress and add a comment that design sign-off is done."
  • "Summarize what changed in the Website space and list anything blocked."

What GrokBot can do. The connector exposes the same operations as the REST API: spaces, folders and lists, tasks, statuses, comments, tags, custom fields, checklists, dependencies, time tracking, goals, views, docs, attachments, templates, webhooks, automations and invitations. Frequently used tools are named directly, such as whoami, list_spaces, list_tasks, create_task and set_task_status; everything else is reachable through list_operations and describe_operation, which list and describe the operations, and invoke_read_operation, invoke_create_operation, invoke_update_operation and invoke_delete_operation, which run them.

Access and revocation. GrokBot can only see and change what you can. Approving a connection mints one entry in Admin > API Keys; revoke it there and access ends immediately. If your workspace restricts members from creating API keys, only an Owner or Admin can approve a connection. See the Privacy Policy for how connector data is handled. Using Claude instead? See Connect Claude to IterDone.

Ready when your team is.

Create your workspace, bring your work across, and get the afternoon back. Iterate until done.

Nothing to install. Productive on day one. No signup for the demo. Already have an account? Sign in

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.