Use Escanor
Integrations
Which tools you can connect to Escanor, how each connection method works, what the dashboard shows, and how to fix a connection that needs attention.
Last updated
On this page
An integration is a connection between your workspace and one of your tools. Connect it once on the website or in an app and the supported workspace surfaces can use it. Individual dashboards, MCP operations and local capabilities vary by provider and platform.
What you can connect
The catalog contains hundreds of providers across multiple categories. Depth of support varies by provider: some have full dashboards (projects, deployments, repositories, incidents), others are available to the assistant and to MCP.
| Category | Examples |
|---|---|
| Source control | GitHub, GitLab, Bitbucket |
| Deployment and CI/CD | Vercel, Netlify, Render, Fly.io, Heroku, GitHub Actions, CircleCI, Jenkins, Argo CD |
| Cloud and infrastructure | AWS, Google Cloud, Azure, Cloudflare, DigitalOcean, Kubernetes, Docker, Terraform Cloud |
| Databases | PostgreSQL, MongoDB, Redis, Supabase, Neon, PlanetScale, Snowflake, BigQuery |
| Monitoring | Datadog, Sentry, Grafana, New Relic, PagerDuty, Prometheus |
| Project management | Linear, Jira, Notion, Asana, ClickUp, Trello |
| Communication | Slack, Discord, Microsoft Teams, Telegram |
| Finance | Stripe, Razorpay, PayPal, Plaid, QuickBooks |
| AI and inference | OpenAI, Anthropic, Google Gemini, Hugging Face, Ollama, Groq |
| And more | Secrets, identity, feature flags, analytics, testing, email delivery, CRM, commerce and CMS |
Open Integrations in the dashboard to see the full list, search it, and filter by category.
How connecting works
Each provider uses one of these ways, and the connect screen tells you which:
- Sign in with the provider. A window opens, you approve access, and you are returned. Escanor stores the granted token; renewal is possible only when the provider supports it and supplies a usable refresh token.
- An API token. You create a token in the provider's settings (the connect screen links to the right page) and paste it. Use the narrowest permissions that do what you need.
- Several fields. A few services need more than one value (a key and a secret, a connection string and a project id). The form lists each.
- A local agent. Some tools live on your own machine or network; the desktop app or an agent reaches them from there.
Credential handling depends on the service and storage path. Avoid placing tokens in chat or logs. Provider operations use saved provider credentials; Escanor does not copy them into the agent configuration. See Security and privacy for the supported storage behavior and limitations.
What Escanor shows you
Depending on the provider, the dashboard builds these views from your live data:
- Projects and services, including those inside a team or organisation account.
- Repositories, branches and recent activity.
- Deployments and their state.
- Incidents and alerts from monitoring tools.
- Activity, one timeline across tools.
Each list tells you which connected tools feed it and which are failing, so it does not ask you to connect a tool that is already connected.
Keeping connections healthy
Tokens expire. Escanor can renew supported OAuth connections using the provider refresh token. API keys, revoked grants and providers without renewal require a different recovery path. A connection can be in one of three states:
| State | Meaning | What to do |
|---|---|---|
| OK | The token is valid. | Nothing. |
| Renewing | Escanor is renewing it now. | Nothing. |
| Needs reconnect | The provider refused the renewal, or never gave a renewal token. | Open the integration and choose Reconnect. |
Vercel teams
Vercel's sign-in only identifies you; it cannot list the projects of a team. To see a team's projects, connect Vercel with an API token and give the team slug. Personal projects work with either.
Why a list can be empty
- The integration is connected but the account has nothing in that area yet.
- The token lacks the permission to read it (reconnect with broader read access).
- The provider is rate limiting; wait a few minutes.
- The connection needs reconnecting (see above).
Limits
The number of integrations you can connect depends on your plan: 6 on Free, 25 on Pro, unlimited on Team. See Plans and billing.
Removing an integration
Open it and choose Disconnect. Escanor deletes the stored credential. To also revoke access at the provider, remove the app or token in the provider's own settings.
Verify a connection before using it
After connecting, open the provider detail and run a safe read, such as listing projects or repositories. Confirm the account/team matches the one intended, and inspect the status and error text. A successful sign-in does not prove access to every project, resource or operation.
For a failed read, record the provider, operation and error code without copying tokens. Check the selected team, resource permissions and provider status. A 403 can indicate missing provider permissions; a 429 requires waiting for the provider's limit to recover. Signing in again will not fix either. Do not widen a token's write permissions to fix a read failure.
Related: Projects, Deployments, MCP, API and keys.
Need help? Contact support with a redacted error and the affected version.