<Provider> and render a <Config> component; the customer connects and configures in an in-app modal, with no redirect to an external page.
It’s the low-effort, in-product option: you get prebuilt components that handle connection status, OAuth, config fields, and workflow toggles, while keeping the whole flow inside your application.
This flow needs a linked account and a session token in place first. Both are created on your backend and documented on the Overview. Never expose your API key in the browser.
When to use it
Choose the React SDK flow when:- You have a React app and want the connect experience embedded in-product.
- You want prebuilt components, not a fully custom UI,
<Config>renders connection status, fields, and workflow toggles for you. - You don’t want a redirect to an externally hosted page.
How it works
Wrap your app in the Provider
Pass your customer’s session token to
<Provider>. Place it high enough in the tree to cover every component that renders <Config>.<Config> component handles the whole experience: connection status, initiating OAuth, rendering your config fields, and saving the customer’s choices.
Next steps
React SDK reference
Every prop on
<Provider> and <Config>, with examples.Config fields
What the customer configures inside the component.
Custom styling
Style the
<Config> component to match your brand.Connection status
Check whether a customer’s account is connected.