{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Enabled by default.
- Authentication: OAuth 2.0.
- Connection: A user authorizes the connection in the provider's consent screen.
- Scopes:
default.
Credentials
Set these per environment. See Connect an integration.
These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.
Setup
- Choose who owns the Asana OAuth app: On hosted Veryfront, Asana uses the Veryfront-managed Asana OAuth app: connect Asana from the project's integrations and approve the Asana consent screen, no environment variables needed. Set ASANA_CLIENT_ID and ASANA_CLIENT_SECRET only to use your own Asana OAuth app, which is required for local and self-hosted runs.
- Create an app: In the Asana developer console, create a new app.
- Set the redirect URL: Under OAuth, add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/asana for hosted Veryfront, or your app origin followed by /api/auth/asana/callback for a local or self-hosted app. Set ASANA_CLIENT_ID and ASANA_CLIENT_SECRET from the app's credentials.
- Make the app available: Under Manage distribution, make the app available in the workspaces whose users will connect; Asana refuses authorization from other workspaces.
- Verify access: Run List Workspaces (read-only). It returns the workspaces of the connected user without changing anything.
Provider notes
- The connection requests the default scope, which gives the app the full permissions of the user who authorizes it.
- Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.
Tools
Verify the connection
Call a read tool such as asana__list_tasks with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.