Hacker News Reader

After spending a reasonable amount of time looking for an answer on the site: Assuming I have a SaaS with some third-party integrations that don't need Nango, why am I taking on the business/technology risk of this external dependency to do "custom" integrations?

View on HN

(Nango co-founder here) Because there will be a lot less that you need to build. You will write less code & ship faster. You will get reporting, monitoring, alerting, a management dashboard & APIs. You will also have an integration architecture that scales to many complex integrations as your company grows!

Can you share an example?

For example, if you want to synchronize a specific object type, you would get: the authorization for the API, a helper for paginating requests, easy data deduplication, resilient background syncing, rate-limits handled, and a way to get the data that's unified across APIs and use-case: `nango.getRecords('zendesk', 'user123', 'ticket')`. And you benefit from the tooling around: all sync runs are logged, you get alerted on Slack on errors, you can inspect your integration activity per end-user, etc.

Reply on news.ycombinator.com