How Motion launched 189 integrations with Nango

Motion is building an AI work platform with AI employees, workflows, and productized integrations that let users automate work across the tools they already use.

As Motion expanded its AI workflows product, integrations became critical infrastructure for making those workflows useful in real customer environments.

Before Nango: integrations were slow, bespoke, and hard to scale

Before adopting Nango, Motion built integrations one by one.

For core product surfaces like calendar providers and Slack, the team had to handle OAuth, token storage, infrastructure, webhook setup, and user experience themselves. That worked for a small number of integrations, but it did not scale to the number of tools Motion wanted to support for its AI employees and workflow builder.

Some integrations also became long-running engineering efforts. Calendar integrations, for example, evolved over years as Motion iterated on the product and handled the long tail of edge cases that appeared with growing usage. Even a single Slack integration could take four to eight weeks to launch because it required both deep technical work and careful UX design.

As Omid Rooholfada, Co-founder at Motion, put it: “We had to approach integrations in a very bespoke way.”

Why Motion chose Nango

When Motion evaluated integration platforms, two things mattered most.

First, coverage. Motion assumed most vendors would support roughly the same set of APIs, but that was not the case. Some lacked important integrations like email or Slack, which were essential for Motion’s product.

Second, flexibility. Motion did not want a rigid abstraction that forced them into a predefined product model. Their team was still iterating on how users should interact with integrations, which endpoints mattered, and how those interactions should appear inside their product. They needed infrastructure that would accelerate development without limiting UX or technical design.

Nango stood out for a few reasons:

Flexible OAuth, without giving up control

The biggest factor was Nango’s architecture. Motion liked that OAuth was separated from syncing and API access, and that Nango’s proxy let them call the underlying APIs directly when needed. That meant they could move quickly without being boxed into a unified schema or fixed workflow.

As Omid said: “The OAuth layer was kind of separate from all the syncing and APIs layers.”

Support for the integrations Motion actually needed

Beyond flexibility, Nango already supported several integrations that were important to Motion, including Gmail and Slack. That gave the team a practical starting point instead of forcing them to fill major gaps themselves.

A white-labeled product experience

Motion wanted integrations to feel native within their own products. Nango allowed them to keep full control over the user experience, rather than exposing users to a third-party interface or a forced authorization flow.

That was critical for a company building AI employees and workflow automation directly into the product.

How Motion uses Nango today

Motion primarily uses Nango for OAuth and API access across its integrations.

Instead of implementing authentication and token storage for each provider internally, Motion uses Nango as the integration layer behind its workflow builder. Each integration is represented inside Motion as a block with predefined tool calls. Users describe what they want to do, and Motion maps that into the relevant API actions, which are then executed through the Nango proxy.

This model gives Motion the freedom to shape integrations around real product workflows, not around the structure of a third-party platform.

Nango also helped on the trigger side. Rather than managing many separate webhook endpoints across providers, Motion benefited from a simpler integration model for triggers and event-driven workflows.

Results with Nango

Launching 189 integrations

With Nango, Motion was able to launch about 189 integrations for its AI employees and workflows.

That let the team support a broad set of customer tools out of the box, including major systems like Gmail, Outlook, and HubSpot, while keeping engineering effort focused on the product itself.

Shipping fast enough to keep product momentum

Motion built and launched the first version of its workflow builder in roughly three to four months. By launch, it already supported a wide range of integrations.

That changed the nature of product feedback. Instead of hearing that a key integration was missing, the team could focus on improving the product experience itself.

In Omid’s words, the main impact was “the speed of being able to ship these things.”

More time for product, less time on infrastructure

By offloading OAuth, token storage, and integration plumbing, Motion freed its engineering team to focus on workflow design, AI behavior, and customer experience rather than rebuilding the same integration infrastructure over and over.

As Omid put it: “Focus on the product experience.”

Fast iteration without platform constraints

One of the strongest outcomes for Motion was that Nango did not get in the way. The team could move fast, preserve their own UX, and adapt integrations as they learned from customers.

Omid summed it up clearly: “It allowed us to get all these integrations out of the box really quickly, and we didn’t feel impeded by the platform.”

Looking ahead: going deeper on the integrations that matter most

For Motion, the next phase is not about maximizing the number of integrations. It is about identifying the integrations customers use most and investing more deeply in them.

Broad coverage helped Motion learn where demand actually is. Now the company can see which integrations are critical to users’ workflows and double down on quality for those systems.

Conclusion

Nango helped Motion go from bespoke, one-by-one integrations to broad integration coverage across its AI workflow product.

By handling OAuth and exposing a flexible proxy layer, Nango gave Motion the speed to ship 189 integrations, the freedom to design its own product experience, and the ability to focus engineering effort where it matters most.

For Motion, the value was not just shipping integrations faster. It was shipping them without compromising the product.

And that is what made the difference.