How Replit powers connector triggers for 30+ integrations with Nango

Replit is building a platform where users can create not just apps, but automations that react to events across the tools they already use.

As that product expanded, integrations became a core part of the experience. Replit needed a scalable way to detect changes in third-party systems and turn them into reliable triggers inside the product, without building and maintaining that infrastructure for every API themselves.

Before Nango: Every event-driven integration required custom polling infrastructure

Before Nango, building a customer-facing integration that reacted to changes in a third-party system meant writing custom code for each provider.

That meant handling different APIs, different schemas, and different polling logic across every integration Replit wanted to support. As customers asked for more integrations, that tradeoff stopped making sense.

As Amadeo Pellicce, Tech Lead at Replit, put it, building that all in-house had become “untenable.”

Why Replit chose Nango

Replit was specifically looking for a reliable primitive for connector triggers and change detection across many third-party systems.

Nango stood out for a few key reasons:

Reliable, scalable webhook infrastructure

The biggest need was a dependable way to monitor changes in external systems and notify Replit when something changed.

Nango gave Replit a scalable webhook and sync layer that could watch for updates across many APIs and surface those changes through webhooks, without forcing the team to build and run their own polling infrastructure for each provider.

Coverage that matched the roadmap

Nango already supported the integrations Replit had on its roadmap, as well as the ones customers were asking for.

That mattered because it meant the team could move quickly instead of spending months building support for each source from scratch.

Open source, TypeScript-based, and deployable on-prem

For Replit, the platform model also mattered.

Because integrations are long-tail by nature, having an open source standard was important. The team valued the ability to fix issues or contribute them back through the repo. It also mattered that syncs were configurable in TypeScript, since that matched Replit’s stack, and that Nango could be hosted on-prem.

How Replit uses Nango today

Today, Nango powers connector triggers inside Replit’s automation projects.

Replit uses Nango syncs to detect changes in connected systems and surface those as events users can build on top of. That gives the platform a trigger layer across a broad set of integrations without requiring the team to manage custom change detection logic for each API.

The team started from Nango’s pre-built syncs, then adapted them to fit Replit’s setup, including a more incremental syncing model focused on new data rather than full historical syncs.

That implementation was lightweight enough that a junior engineer could make the required changes and get it working.

Results with Nango

Trigger support across 30+ connectors

Replit now uses Nango-powered syncs across more than 30 connectors, giving users a broad set of triggerable integrations inside the platform.

That means customers can build automations that react to changes across many of the tools they already use, without Replit having to build every integration trigger from scratch.

Faster path to an automation product

Nango helped Replit ship the trigger primitives needed for its automation layer much faster than would have been possible with a fully custom internal approach.

A foundation for broader agent and automation use cases

Today, Nango powers Replit’s automation stack. Longer term, the team sees this as foundational infrastructure for a broader product direction in which apps and agents can subscribe to events from integrations across the platform.

Conclusion

Nango gave Replit a scalable way to power connector triggers across 30+ integrations without building custom polling and sync infrastructure for every provider.

By providing reliable change detection, webhook delivery, roadmap-aligned integration coverage, and a flexible TypeScript-based platform, Nango helped Replit accelerate its automation product while keeping engineering effort focused on the product itself.

For Replit, the value was not replacing their entire integration stack.

It was solving one of the hardest parts cleanly, so the team could build faster.