From a technical perspective there are two main ways that Trelica connects to other SaaS applications. We've pre-configured every integration and included instructions so you don't need to worry about this, but it's helpful to know why Trelica connects in different ways to different applications.
OAuth is an open standard which lets you delegate access to your data to another application. This means that you can easily instruct one of your SaaS applications to give Trelica access to certain types of data. OAuth is the simplest way to control data sharing between SaaS applications.
The typical flow for configuring an OAuth integration is:
- 1.Click on a button in Trelica to initiate the connection to the app.
- 2.Trelica sends a message to the app saying that you want to give Trelica access to certain types of data.
- 3.The app asks you to login.
- 4.The app shows you what Trelica has requested (e.g. access to user data).
- 5.You click a button to authorize this request.
API Keys are an older way of giving another SaaS application access to data. They're like a password, and they typically give quite broad access rights in terms of what Trelica can do. Some applications give you a single API key that you use for all the applications you want to connect, whereas others let you generate specific API keys for each application that you want to connect to (a better approach).
The typical flow for configuring an API Key integration is:
- 1.Login to the app you want to connect with.
- 2.Find the page that shows the API key, or lets you create API keys.
- 3.Copy the API key to the clipboard.
- 4.Click on a button in Trelica to initiate the connection to the app.
- 5.Paste in the API key.
- 6.Click to save the connection.