⏱️ 1 hour to complete
Authorization overview.
Generate a session token (backend)
ℹ️ Details on end user and organization information
end_user
and organization
information fields help identify which connection belongs to which end user and organization. This information is also used for display purposes in the Nango UI and, in some cases, for custom billing plans.end_user.id
is required. Pass in your internal ID of the user who initiated the authorization flow. This ID, and potentially the organization.id
, are necessary for reconciling the connection details that your backend receives from Nango after the connection is created (as described in the section 3).end_user.id
(or use the information of the user who initiated the authorization flow).Embed the auth flow (frontend)
Nango's default authorization UI.
Listen for webhooks (backend)
POST
requests with the following JSON body:connectionId
value alongside its corresponding user or organization.