Connect other services

Besides Google, Slack, Salesforce and GitHub, nouter ships these services ready to connect. The steps are the same for all of them.

Connect any of them

1. Go to Customize (in the sidebar) and open Connectors.
2. On Discover, find the service and click the + on its card.
3. The service’s screen opens. Sign in and authorize with your company account.
4. Back in nouter, the service shows up under Yours. It works in any conversation, with no re-authorizing.

Each one uses your own account and its permissions. Reads happen right away and anything that writes waits for your approval (Why it asks for your approval).

Each service

Notion

Pages, databases and comments.

Linear

Issues, projects and comments.

Jira and Confluence (Atlassian)

Jira issues and Confluence pages.

Caution

Your company’s Atlassian admin has to allow this project’s domain in Rovo → MCP server. Without it, Atlassian refuses the connection.

Supabase

Projects, databases and functions. Everything that writes, SQL included, waits for your approval. Avoid connecting production projects.

Stripe

Customers, payments and invoices. Besides your approval, Stripe asks its own confirmation for refunds and payouts.

Cloudflare

Your Cloudflare account. It has a tool that runs code against the API, so review each approval carefully.

Twenty

People, companies and opportunities. It is for Twenty Cloud workspaces; a self-hosted Twenty is added as your company’s own MCP server (an admin does that).

NetSuite

Records, saved searches and SuiteQL, with your own NetSuite role. An admin sets it up first with your company’s NetSuite Account ID and integration: an integration with the “REST Web Services” scope (not “NetSuite AI Connector Service”). When you connect, pick the NetSuite role you were given for Nouter: the role needs “REST Web Services” and “Log in using OAuth 2.0 Access Tokens”, and the administrator role is refused. The agent reads what that role can see. It does not run reports or approve and reject records, and it never deletes anything; everything it creates, updates or transforms waits for your approval.

If the admin changes the integration or the Account ID, reconnect NetSuite once. If a project used the earlier version of NetSuite (Oracle’s MCP server), it asks you to reconnect NetSuite the first time you open it, also once.

EmDash

Pages, posts and media of a site built with EmDash, Cloudflare’s CMS.

You need a user in that site’s EmDash. When you connect, you paste the site’s address (https://your-site.com, with no path), sign in to the site with your EmDash user and leave ticked the permissions you want the agent to have. Each connection is one site; for another site, connect again. What the agent can do is capped by the permissions you leave ticked and by your role in EmDash: an Editor cannot change the site’s schema even if the permission is ticked. If you untick one and the agent needs it, it tells you which one is missing and you reconnect.

The agent can read content, save drafts, upload images (up to 10 MB each) and propose changes. What waits for your approval:

• Drafts and uploaded images are the only things that can be applied on their own, and only if you turned on the automatic approval rule; the first time you approve one, Nouter offers to turn it on (Automatic approval).
• Anything that goes live always asks: publishing, unpublishing, scheduling, editing an entry that is already published or scheduled, moving it to the trash, discarding a draft, and changing menus, taxonomies, authors or the site’s settings. Editing the SEO, authors or categories of a published entry also goes live, even if EmDash shows it as a draft, so it asks too.
• What cannot be undone is never approved on its own: deleting for good, deleting an image, a menu, a taxonomy or an author, changing the schema, exporting the site (it also needs an admin’s approval inside EmDash), and any tool a plugin of the site adds (those need the Admin role in EmDash).

A change’s approval shows the site, the collection, the title, which fields change and, for publishing, what changes against the live version. It also carries a preview link to the draft, valid for 24 hours. That link opens the site’s public pages, not EmDash’s admin: if the site’s public pages are behind Cloudflare Access, whoever approves has to be able to pass Access to see it. Many changes can be undone from Nouter; deleting for good, changing the schema and exporting the site cannot.

If someone has the entry open in EmDash’s admin, the change fails and the notice says who; the agent only overwrites it if you ask it to.

A project that uses EmDash can be shared: each person connects their own user of the same site and Nouter confirms they can see what the project read. A project can have access to the whole site, to one collection or to a single page.

Caution

Connect only EmDash sites that belong to your company or that you trust. EmDash does not yet confirm which site an authorization comes back from: if you connect a malicious site, it could keep access to another EmDash site where you have a user. Nouter checks what it can, but that risk remains until EmDash resolves it.

To disconnect or change what the agent sees, see Disconnect an account.