Credentials
Think of a credential like a saved login on your phone: you set it up once, and from then on your apps open without asking for your password every time. A credential in Nirvai works the same way — it stores the sign-in details (the private password or access pass a service needs) so your agents can connect to outside tools like Gmail, Slack, HubSpot, and Shopify on your behalf. Without one, your agents can chat, but they can't take action in the tools you use every day.
Image: The credentials page showing saved credentials as cards with provider logos
What you can do here
| You can… | What that means for you |
|---|---|
| Connect outside services | Let your agent send emails, update your CRM, post messages, or create orders in the tools you already use |
| Set it up once | Save your sign-in details a single time, and every agent reuses them automatically |
| Choose how you connect | Pick from a guided AI helper, a ready-made template, or a quick Facebook sign-in for Meta apps |
| Keep secrets safe | Your passwords and access passes stay encrypted — they never show up in chats, logs, or anywhere you can read them |
| Manage everything in one place | Edit, reconnect, or delete any saved connection whenever you need to |
How it fits together
Your agents become truly useful when they can do things in other tools, not just talk. A credential is the piece in the middle: your agent asks it to act, and it proves to the outside service that the request is allowed — without ever exposing your password.
Credentials vs. channels
People often mix these two up. A credential lets your agent reach out to a tool and do something there. A channel is the opposite direction — it's how people reach in to chat with your agent.
| Credentials | Channels | |
|---|---|---|
| Purpose | Let your agent act inside outside tools | Let people message your agent on a platform like WhatsApp |
| Direction | One-way — your agent pushes information out to a service | Two-way — people send messages in, your agent replies |
| Example | Your agent uses a Gmail connection to send an email | Your agent is published to WhatsApp so customers can chat with it |
Channel example: You publish your agent to WhatsApp. A customer asks "What's my order status?" and your agent replies "Your order #123 ships tomorrow." They can keep asking follow-up questions — it's a back-and-forth conversation.
Credential example: During that same conversation, your agent uses a Gmail connection to send the customer a shipping confirmation email. Information flows out to Gmail, but Gmail doesn't send anything back into the chat.
To publish your agent on WhatsApp, Instagram, or Telegram, use Channel exports in the Agent Control Panel — you don't need a credential for that. You'd only use a credential with a messaging app if you want your agent to notify it (like posting alerts to a Slack channel), which is a one-way push.
All credentials are encrypted, both while stored and while in transit. Your secrets — passwords, private keys, and access passes — are never visible in logs, chat history, or anywhere you can read them. Only you and authorized team members can change a saved connection.
What's next
Credential Types
Learn the different ways to connect — API key, access pass, sign-in, and more
Meta Platforms
Connect WhatsApp, Instagram, Messenger, and Meta Ads with a Facebook sign-in
Browse Templates
Use a ready-made setup for popular services like Google, Slack, and HubSpot
AI Assistant
Let AI guide you through connecting any service, step by step
Use with Tools
Attach a saved connection to your agent's tools
Manage Credentials
Edit, reconnect, or delete your saved connections