Stackflows
HomePricingContactBPMN Academy
  • Introduction to StackFlows
  • Getting started
    • 🚀 How to start?
    • ❓FAQ
    • 🤗 Our community
    • 📖 Definitions
    • 📚 Knowledge base
  • Products
    • Studio
      • Collaboration with others
        • Comments
        • Model share
      • Model categories
      • Model design
        • Node types
          • Start node
          • Task
          • User task
            • User task forms (Custom fields)
          • Business rule (DMN) task
          • Service (external) task
          • Call another process
          • End node
          • Gateway
        • Start (Test) process
        • Data mapping
        • Data forms
        • Flow conditions
        • Time formats
        • Token simulation
        • Process real-time simulation
        • General model settings
        • Advanced model settings
      • Model deployment
        • Deployment errors
      • Process execution (Start)
        • Manual process start
        • Process start by email
        • Process start with webhook
        • Process start via API
      • Process execution errors
      • Insights and analytics
        • Model real-time activity
        • Heatmap insights
      • Embedded BPMN Studio
      • Basic features
        • Model versions
        • Version compare
        • Process tags
        • Model import/export
        • Model draft version
        • Model notes
    • App (User area)
      • Dashboard and metrics
      • User tasks
      • Workflows
      • User management
      • Organization structure (Tree)
      • Organization settings
    • Core features
      • Variables
      • Organization (Business) units
      • Tags
      • Profiles
      • Environments
    • Apps & Connectors
      • Make.com integration
      • Custom app integration
      • Camunda 7 connection
      • App & Integration profiles
  • BPMN & DMN modelling
    • Introduction of BPMN
  • API
    • API Introduction
    • API reference
  • Subscriptions & Billing
    • Introduction
  • Troubleshooting
    • How to report a problem?
  • Policies
    • Terms of services
    • Privacy
    • Data processing
Powered by GitBook
On this page
  1. Products
  2. Core features

Profiles

PreviousTagsNextEnvironments

Last updated 1 year ago

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:

  • in the User Area

Profiles management
Using profiles when building service tasks