Skip to content

Nango

Manage customer permission to connect an external service, then run or build the jobs that read and transfer the data.

Visit Nango

What part of the connection can Nango handle?

Nango gives customers a way to approve a connection from your app. It can store the resulting permission and refresh it where the provider supports refreshing. You still decide whose account the connection belongs to and which access to request.

What work remains after the customer connects?

Choose a sync or build one to fetch and shape the records your app needs. With Nango Cloud, fetched sync records can sit in Nango’s cache before your app reads them. Decide what you will save in your own app and what happens when a connection ends.

Budget for the number of connections, the time your integration runs and the data it transfers. The free plan caps each of those.

What would you check before a first import?

On paper, label two fictional customer accounts with one contact in each. Check that your proposed connection for the first customer has one place to save its result.

  1. Choose the smallest data request
    Ask to read contact names for the fictional import. Write down who approves it.
  2. Name the owner of the result
    Draw where that contact will appear and which customer can see it. Mark the other customer’s list as a separate destination.
  3. Decide what disconnect means
    Write what the customer sees after they disconnect and what your app will do with the copy it already imported.