Skip to main content
The pre-OAuth2 model gives the same result as the embedded model without development on your side. The requirement is that your software already has an OAuth2 authentication flow. You share one URL for each app you want to connect. Your own OAuth2 flow protects that URL, so only people with an account in your software can open it. Chift creates the consumer and the associated connection from that authentication. If your end-user returns to the configuration page later, Chift reuses the existing consumer and connection instead of creating new ones.

​
What you build

Nothing is required. You share the URL, and Chift handles the consumer, the connection, and the setup page. You can still call the Chift API if you want to read execution statuses or show logs inside your product. That is optional. See Monitor sync executions.

​
What your end-user sees

A configuration page embedded in your software, behind your own authentication. The page is white-label, so the experience stays inside your product.

​
Requirements

  • Your software has an OAuth2 authentication flow.
  • You share one URL per app you want to connect.
Chift sets up this model with you. Contact us to enable it for your account.