How integrations work in Zapini (overview)

What integrations are

Integrations connect Zapini to external tools you already use — from CRMs to messaging channels and banking services. Instead of switching between several systems, you centralize support and let information flow between platforms.

All connections live in the Integrations menu (/integrations), where each item shows its status and configuration options.

What you can connect

Zapini offers integrations organized by purpose:

• Messaging channels: Telegram, Instagram Direct, and Slack.
• CRMs and marketing: RD Station Marketing, RD Station CRM, and CV CRM.
• Networking and prospecting: LinkedIn.
• Finance and payments: Banco Cora and Mercado Pago.
• Services and automation: Uber, Web Scraper, EzServer, and Meta.

How each integration is set up

Every integration has its own connection flow, which usually involves one of these methods:

• API keys: you paste a key generated in the external tool's dashboard.
• OAuth: you authorize Zapini directly within the service, without copying passwords.
• Webhook URL: you register an address provided by Zapini in the other platform to receive events.

The exact step by step appears on the integration's own screen, with the fields required for that service.

💡 Tip: enable one integration at a time and test the flow before moving to the next. That makes it easy to trace the source of any adjustment you need.

AI as a consumer of integrations

Some integrations go beyond receiving data: the Zapini AI can use them as tools during support. This lets the assistant look up or record information in external systems while chatting with the customer, always within the permissions you configured.

Next steps

To get started, open /integrations, choose the tool you want, and follow the on-screen instructions. If you're connecting a CRM, see the dedicated article on RD Station and CV CRM; for channels like Telegram and Instagram, there's a separate guide.