n8vDocs

Integrations

Connect a service once, decide what your assistants may do with it, and approve anything that costs money or cannot be undone before it happens

Integrations is where the services your assistants act on live: what is connected, what each tool may do, and what asks you first.

Integrations is being rolled out. When it is on for your account you see Integrations in the sidebar.

Connect a service

  1. Open Integrations, then Catalog. Search or pick a category.
  2. Open a service to read what an assistant can do with it and what signing in asks for.
  3. Choose Sign in and finish at the service.

A remote MCP server that is not in the catalog is added with Add by address. Add only a server you trust: what it answers reaches your assistants.

A new connection starts with nothing allowed. It is off for assistants and off in new chats until you turn it on.

Some services are marked Needs setup (an app has to be registered for n8v first) or Not yet (the service has no public way to act for a person). The card says why.

What each tool may do

Every tool has a class:

ClassMeaningBy default
ReadLooks, changes nothingRuns
WriteChanges something that can be changed backRuns
SpendMoves moneyAsks you
Cannot be undoneDeletes, sends or books for goodAsks you

On a connection's page you choose, per tool:

  • whether assistants may call it at all,
  • its class, when n8v could not tell or you want it more careful,
  • when it asks: Runs, Asks the first time or Always asks,
  • for a tool that spends, which keys and connected apps may call it.

A tool that moves money always asks, on every connection, including ones you connected before Integrations. A monthly spend limit per connection comes with the first services that report a price before they charge.

If a service changes what a tool does, the tool asks every time until you accept it as it is now.

Approving

When an assistant asks for something that must ask first, nothing runs. It waits under Needs you with:

  • what it does, in n8v's words, and the price when there is one,
  • which connection and account,
  • who asked, and the reason it gave,
  • exactly what will run, field by field.

Approve runs it at once, exactly as shown. For money and for what cannot be undone, n8v may ask for your second factor. Decline runs nothing; you can say why, and the assistant is told.

Approving is done only here, by you. No assistant, key or connected app can approve an action, whatever permissions it has.

If n8v sent an action and heard nothing back, it shows No answer: it may have happened. n8v never sends it again. Look at the service, then say whether it happened.

Your profile

Profile holds what a service may need to act for you: home, work, a payment method's name, dietary notes, time zone and language. It is kept encrypted.

A connection reads a field only after you tick it on that connection. An assistant passes a field by name and n8v does not show it the value; you see the value on the approval card.

For assistants and scripts

Over MCP and the REST API the same operations exist:

OperationMCPREST
List, with cataloglist_connectorsGET /api/v1/connectors?catalog=1
Call a toolcall_connectorPOST /api/v1/connectors/{id}/call
Connect (a link)connect_servicePOST /api/v1/connectors
Read a connectorread_connectorGET /api/v1/connectors/{id}
Tighten accessset_connector_accessPATCH /api/v1/connectors/{id}
List actionslist_connector_actionsGET /api/v1/connectors/actions
Read an actionread_connector_actionGET /api/v1/connectors/actions/{id}
Decline an actiondecline_connector_actionPOST /api/v1/connectors/actions/{id}/decline
  • A call that must ask answers an action in state waiting (REST: 202). Read its outcome with the action's id; read_connector_action can wait up to 45 seconds.
  • Pass idempotency_key for anything with a side effect: the same key with the same request is the same action and never runs twice.
  • mode: "prepare" stores a call and runs nothing; mode: "commit" with the action's id and sha256 runs it.
  • With Manage your connectors (connectors:manage), access can be tightened: fewer tools, a stricter rule, a lower limit. A change that opens more is refused with what it would open and the page where you make it.
  • A profile field is passed as { "$profile": "home" }. n8v fills it in and does not show it to the assistant; a service that repeats what it was sent in its answer can still return it.