Integrations

Integrations give nimo more context and a place to reach you. Audits already work without any of them. Each connection adds one kind of evidence or one destination, so connect only what helps your workflow.

How integrations fit together

Connected data shows up in two places. Audits pull it in while Lighthouse runs, so the report can say which slow pages also earn search clicks or sessions. Chat reads it on demand when you ask a question that needs it. If a connected source fails or has no data, the audit still completes and the report says the data is missing.

At a glance

Slack

Slack lets you talk to nimo from a DM or channel mention and receive audit updates in chat.

nimo asks Slack for permission to post messages and reactions, read its DMs and messages in channels you invite it to, register the /nimo command, and upload files such as PDF reports. See the Slack guide for commands, channel mentions, and example questions.

Google Search Console and Analytics

Google Search Console adds search context. Google Analytics 4 adds traffic context. Together, they help nimo connect speed problems to pages that matter. One Google sign-in covers both, with read-only access: nimo requests the Search Console read-only and Analytics read-only scopes plus your email address.

With Search Console connected, nimo can show clicks, impressions, queries, and average position; check a page's index status with Google's URL Inspection; and compare your sitemaps with the pages that earn impressions. With Analytics connected, audits add sessions, device split, and bounce rate, and chat can count sessions referred by AI assistants such as ChatGPT, Perplexity, Claude, Gemini, and Copilot.

nimo never adds Search Console clicks to Analytics sessions: clicks are not visitors, and each number stays labeled with its source.

Ahrefs

Ahrefs adds SEO data such as domain rating, organic traffic, keywords, backlinks, and top pages. Use it when performance work needs to connect to organic search opportunity.

In Ahrefs, open your profile, go to API, and generate a key in the MCP Keys section. Once connected, audits add an SEO context section, nimo can compare your site with organic competitors, and chat can list referring domains and backlinks. Live backlink reads use your Ahrefs allowance, so nimo only runs them when a question needs fresh data.

Cloudflare

Cloudflare is used for edge optimization. It lets nimo read zone settings and suggest safe infrastructure fixes for images, compression, caching, and headers.

nimo waits for a three-audit baseline before it suggests Cloudflare changes, so one noisy run cannot trigger a recommendation. The full approval, apply, and rollback flow is in Cloudflare optimization.

Linear

Linear is used for explicit incident and Agentic readiness issues when the integration is enabled. nimo can preview a narrow issue from stored evidence, and creates the issue when you explicitly ask for it.

nimo asks Linear for read access plus permission to create issues and comments. It cannot edit, close, or delete existing issues. A good issue from nimo names the affected page and metric, the before and after values, the likely owner, and what "fixed" means, so the developer does not need to open nimo to act.

PostHog

PostHog adds product traffic context for an owned site: pageviews, distinct visitors, recorded sessions, top pages, top events, and devices.

Choose your PostHog region (US or EU) before signing in. From chat, nimo can create a secure setup link that stays valid for 30 minutes; it never asks for API keys in chat. To read traffic, nimo creates one saved query endpoint in your PostHog project, scoped to the site's exact hostname over the last 28 complete UTC days. Results are cached for up to 12 hours. The endpoint stays in PostHog if you disconnect, and saved reports keep their existing snapshots.

Custom MCP servers

Use a custom MCP connection when your own tools or workspace data should be available in nimo chat. Add the server URL, transport, and any required headers in Settings.

nimo supports Streamable HTTP and SSE transports. Headers such as API keys are stored encrypted, and URLs that point at private or internal network addresses are rejected. After you add a server, nimo tests the connection. Each connection shows as Connected, Paused, or Needs attention, and you can pause, test, edit, or remove it at any time.

Notion

Manage and disconnect

You stay in control of every connection. Disconnecting stops new reads right away; reports that were already saved keep the data they captured at the time.

• Google: disconnect each connected Google account from Settings. Removing the last one turns off Search Console and Analytics context.
• Slack and PostHog: use Disconnect on the integration card in Settings.
• Cloudflare, Ahrefs, and custom MCP servers: remove the connection in Settings, which deletes the stored credentials. Pause a custom server instead if you only want to hide it from chat for a while.
• Telegram: send /unlink in the chat or disconnect from Settings.

Troubleshooting

Search Console shows no data for my site. The Google account must have access to a Search Console property that matches the site URL. nimo lists the properties it can see, which makes a domain or URL-prefix mismatch easy to spot.

Analytics data is missing. Reconnect Google and approve Analytics access, then confirm the GA4 property for the site.

PostHog says no data. The project is connected, but no events match the site's exact hostname in the last 28 days. Check that the site sends events to that project.

A custom MCP server needs attention. Use Test connection. Confirm the URL is public, the transport matches your server, and any header values are current.