In our automation tools, we have simplified the naming convention by using the term "Profiles" to encompass various functionalities such as "Connections," "Authorization profiles," and "Connectivity." This consolidation serves two primary purposes:

  1. Storing Authorization Profiles: Profiles allow users to securely store and manage authorization details and credentials for specific applications or connections. For instance, you can create a Profile by providing a name and token to authorize access to Google Drive. This Profile can then be utilized across multiple workflows and processes, simplifying the authorization process.

  2. Storing Configuration Sets: Profiles also serve as a means to store sets of configurations. When building processes that frequently interact with third-party systems, you often encounter similar endpoints or require the same data. By using Profiles, you can conveniently select a predefined configuration set, making it easier to access specific endpoints or retrieve consistent data. For example, if you need to search for a particular document in Google Drive, you can select the appropriate Profile that contains the necessary configuration for this task.

Read more about:

Last updated