Nango: automation features and setup

Overview

Nango is intended for products that need to let each customer connect their own accounts. It provides layers for authorization and token refresh, synchronization functions, and actions invoked through an API or agent. Integrations remain in code, so you can adapt the mapping to product requirements. This differs from internal automation: you need to handle each customer's connection and data separately and provide a way to fix an authorization that has expired.

Features

• Manages OAuth, API keys, and authorization refresh for connections.
• Synchronization functions, actions, and triggers from external events.
• Documentation, retries, and handling of API rate limits.

Business uses

• Adding a CRM connection to a SaaS product, with contact synchronization for each customer.
• Exposing an authorized action in an external system as a tool for an agent in a product.

Getting started

• Choose one API and define the user permissions and required data.
• Build a synchronization function or action and test it with two separate accounts.
• Check revoked authorization, connection deletion, and repeated actions before release to customers.

What to check

• Authorization infrastructure does not remove the need to define which information each user may see in your application.
• Check how deletions and updates in the source system are reflected in synchronization, not just the addition of new records.