Open Integrations to create and manage connections for the selected company. Individual channel resources may open from this page instead of appearing separately in the sidebar.
Related video lesson
Related workspace navigation chapter. Provider authorization must be configured and verified separately.
Connect customer channels
- Chat Widgets for websites, full-page chat, and PWA experiences.
- WhatsApp and its API setup guide.
- Other communication channels, including available Instagram, Messenger, and SMS controls.
- WordPress setup for embedding website chat.
Connect business systems
| Integration | Use it for |
|---|---|
| Agent Tools | Retrieve live data or perform a configured action during a conversation. |
| API Actions | Send mapped workflow data to an external endpoint. |
| Webhooks | Deliver configured events to an external receiver. |
| Linked Stores | Connect a compatible WordPress/WooCommerce store. |
| Outbound Messaging API | Send company-scoped WhatsApp messages with a dedicated credential. |
| Mobile SDK sessions | Embed authenticated customer chat in a host app. |
| Data Stores API | Query stored form entries and update tags. |
| Account Management REST API | Manage supported company resources with per-key BREAD permissions. |
| Account Management MCP | Give an MCP client access to the same permitted company resource operations. |
| API Definition Exports | Download Postman collections and MCP schemas filtered to one key's effective access. |
| SMTP | Connect your own verified sender for email broadcasts and optional chat-widget verification email. |
The n8n connection card accepts its API URL and header-auth API key. This is separate from a webhook URL used by an individual workflow action.
Create account-management credentials in API Settings. Use the scope and field reference to check which resource actions and attributes the REST and MCP interfaces support.
Connect an SMTP account
Open Integrations → SMTP → Manage SMTP accounts. Add a name, choose SendGrid, Mailchimp Transactional, Zoho Campaigns Email API, Zoho ZeptoMail, or another SMTP provider, then enter the provider's SMTP credential and a sender address verified with that provider. Nviti tests the encrypted SMTP connection when you add or change its login details. The secret is stored encrypted and is not shown again in the form.
SendGrid and Zoho Campaigns Email API use apikey as the SMTP username. Zoho ZeptoMail uses emailapikey. Mailchimp Transactional uses its Transactional API key and SMTP service; a normal Mailchimp Marketing login is not an SMTP credential. Mailchimp Transactional and ZeptoMail are limited to chat-widget verification emails in Nviti because their SMTP services are for transactional mail, not audience campaigns. Mailchimp Marketing campaigns require a separate API integration.
An account can optionally be selected for chat-widget verification emails. Without that selection, the widget keeps using Nviti's existing application mail transport. Set each account's messages-per-minute limit to match its provider quota; the limit is shared by campaigns using that account. Customer SMTP accounts require the customer's own sender domain; nviti.ng and nvt.ng addresses cannot be used here.
Customer SMTP gives each workspace its own sending account and sender address. Email broadcasts still include an unsubscribe link on api.nviti.ng, so link-domain reputation is shared until customer-branded unsubscribe domains are supported. SMTP acceptance is recorded as Sent; bounce, complaint, and inbox-placement data require provider webhooks and are not tracked by this integration yet.
Set up and verify
Create the connection, configure the requested credentials, save, and run a controlled end-to-end test. Confirm incoming data, the assistant or workflow action, and the resulting delivery. Recheck the connection after changing credentials or the external system.
Use AI Assistants to configure the behavior behind a channel, and AI Features and Usage to understand consumption.
CRM and service connections
Use the Zoho CRM and Zoho Desk cards alongside the other integration cards. Each authorization belongs to the selected company and verified provider organization; CRM authorization does not authorize Desk.
- Zoho CRM: connect, review and exchange supported Contacts.
- Zoho Desk: connect and map supported ticket fields.
- Record updates: explicitly enable individual-record notifications and queued updates, separately from manual import/export.
- CRM Migration: stage existing exports and reconcile a reviewed migration.
Connection/setup controls may open a side panel; fuller mapping and per-record operations retain their dedicated screens. Cards show availability separately from connection state. Setup unavailable requires checking operator configuration, rollout, purchased capability and staff permissions. Ordinary users are not asked to register OAuth callback URLs themselves.
Cards use provider-specific descriptions and theme-aware medium logos. SMTP is toward the end. See Workspace controls for the current action/menu convention.