Skip to main content

Integrations

The Integrations page

What Integrations are, how they differ from channels, and what each connection card on the page shows.

Think of your agent as a new teammate on their first day: before they can help, they need keys to the apps you work in — your email, your CRM, your project tracker. The Integrations page is that keyring. You hand over each key once, and every app you've connected gets one card showing the credential you saved, the actions it unlocked, and which agents use them.

You'll come here whenever you want your agent to do something outside a conversation: look up an order, file a ticket, send an email, read a document.

TermWhat it is
CredentialA saved login for an outside service. Save it once; every tool reuses it.
Custom toolOne specific action you teach your agent — "look up an order in Shopify". Most use a credential.
MCP serverA whole app connected in one step. The app hands your agent a ready-made list of actions.

Apps your agent uses vs. places it answers​

These are two different jobs, and keeping them apart makes everything else easier:

Integrations (credentials, tools, MCP)Channels
DirectionYour agent reaches out to an app and acts therePeople reach in to chat with your agent
ExampleYour agent uses a Gmail credential to send a shipping confirmationYour agent is published to WhatsApp so customers can ask about their order
Where you set it upThis pageOn the agent itself, in the Agent Builder

A single agent usually has both: it answers on WhatsApp (a channel) and looks things up in HubSpot (an integration). You don't need a credential to publish on a channel. You'd only use one with a messaging app to notify it — like posting alerts to a Slack channel.

Two things called MCP

MCP servers here are apps your Nirvai agent uses — you connect Linear, your agent gets Linear's actions.

Connect your agent is the opposite direction: it lets an outside assistant like Claude Code use your Nirvai account. Different setting, different page.


A connection card​

HubSpotConnectedHubspot · hubspotDetailsEdit
  • List deal pipelineshubspot_list_deals_pipelinesGET2 agents
  • Create contacthubspot_create_contactPOST1 agent
  • Search CRM objectshubspot_search_crm_objectsGET
Show all 30

Reading it top to bottom:

  • The name and status. Green means the credential is saved and working. Amber Needs sign-in means the app wants you to sign in again — nothing will work until you do.
  • Details opens a read-only summary of the saved credential. Edit opens it for changes.
  • Each row is one action your agent can take, with its short name underneath and the kind of request on the right.
  • The faces show which of your agents currently use that action. No faces means no agent has picked it up yet.
  • Show all opens the full list in a side panel, so a card with thirty actions never crowds out its neighbours.
An empty card is normal

A connection with No tools yet means the credential is saved but you haven't given your agent any actions with it. Use Build with AI to describe what you need, or Browse templates for ready-made ones.


Finding things quickly​

Filter chips sit above the cards:

ChipShows
AllEvery connection
Needs attentionCredentials that expired or were never finished — fix these first
Not on any agentConnections nothing is using, so you can clean up
MCPOnly whole-app connections (MCP servers)

The search box matches both connection names and the actions inside them.


The tools panel​

Show all opens a side panel listing every action on that connection, with a search box of its own. Each row offers:

  • Details — what the action does and what it needs.
  • Edit — change it, for actions you or the AI built.

Actions that came from an MCP server show a lock instead. The app that provides them decides their shape, so you can switch them on or off but not rewrite them:

LinearConnectedMCPmcp.linear.app · Linear MCPDetailsEdit
  • Create issuelinear_create_issueMCPManaged by the app
  • List issueslinear_list_issuesMCPManaged by the app
Show all 62

Tools without a credential​

Not every action needs a credential, so those live in their own group rather than looking like broken connections:

GroupWhat it means
Public APIsOpen services that need no sign-in at all, like a weather lookup.
Login saved inside the toolOlder tools that keep their own key in their settings instead of using a shared credential.
Built into NirvaiAbilities that ship with Nirvai — web search, image generation, reading documents. Nothing to connect.

What's next​