Connecting Asana (setup checklist)

This checklist walks you through connecting Asana to Harriet. Follow it top to bottom and you'll end with a working connection. Most failed Asana setups come from one of three misses, all covered below: the wrong app type, missing redirect URLs, or missing OAuth URL overrides.

You'll need: admin access to your Asana account, and access to Harriet's Company settings → Integrations.

How access works (before you start)

Installing this connector registers an OAuth app for your organization — Harriet does not read or write Asana as you, the admin. After setup, each user connects their own Asana account under Profile → Integrations, and the assistant can only do what that user's own Asana permissions allow.

Step 1 — Create an MCP app in Asana

Critical: choose the "MCP app" type, not "API app". An API app will fail later with a "client not found" error during user sign-in, and Asana does not let you change the type afterwards — you would have to recreate the app.

1. Go to the Asana developer console: https://app.asana.com/0/my-apps
2. Sign in as the Asana account you want to administer the app from.
3. Click Create new app.
4. Name it (e.g. Harriet) — users see this name on the consent screen.
5. Choose MCP app as the app type, then click Create app.

You'll see a Client ID and Client secret. Keep this tab open — you'll need both shortly. Treat the client secret like a password.

Step 2 — Add the redirect URLs

In the Asana app's left sidebar, open OAuth and add both redirect URLs:

https://hrharriet.com/bots/integrations/mcp/oauth/callback/
https://harriethq.com/bots/integrations/mcp/oauth/callback/

The match must be exact, including the trailing slash.

Leave scopes empty — Asana MCP apps don't use them.

Step 3 — Configure workspace access

In the left sidebar, open Manage distribution and choose:

• Specific workspaces — then add the workspace(s) you want to use, or
• Any workspace — usable everywhere.

Save changes.

Step 4 — Enter the credentials in Harriet

In Harriet's Install Asana dialog:

1. Paste the Client ID into Asana OAuth client ID.
2. Reveal the Client secret in Asana and paste it into Asana OAuth client secret.

Step 5 — Set the OAuth URL overrides

On the Asana connector's configuration, check that both override fields are set — Harriet pre-fills them for new catalog installs, but the connection will not work without them. They point Harriet at Asana's authorization server, where your app is registered.

Field	Value
OAuth authorize URL (override)	https://app.asana.com/-/oauth_authorize
OAuth token URL (override)	https://app.asana.com/-/oauth_token

Step 6 — Review, connect, verify

1. If your organization uses Endpoint AI review, submit the connector for review and have it approved.
2. On the connector, click Sync tools so Harriet discovers the Asana actions, then enable the tools you want under Tool permissions and save.
3. Attach the connector to a skill and assign the skill — users won't see anything until this is done.
4. Connect your own Asana account under Profile → Integrations: you'll be sent to Asana's consent screen — click Allow.
5. Verify it works: ask Harriet something like "show me my Asana tasks due this week."

Troubleshooting

Symptom	Most likely cause
"Client not found" at sign-in	App was created as an API app instead of an MCP app (recreate it), the Client ID has a typo, or the app isn't distributed to your workspace (Step 3).
Redirected to an error page after consenting	A redirect URL is missing or doesn't match exactly — check both URLs and the trailing slash (Step 2).
Consent screen never appears / generic OAuth error	The OAuth URL overrides aren't set (Step 5).
Setup looks complete but users see nothing	The connector isn't attached to a skill, the skill isn't assigned, or review approval is pending (Step 6).

See also How to create an MCP connector (Company settings) and MCP authorization and stored credentials.