Looply Academy
  • What is Looply?
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Managing & Using Environment Variable Profiles
  • Creating & Managing Profiles
  • Selecting a Profile for Execution
  1. Workflows

Environment Variables & Profiles

Define workflow environment-specific variables to keep your logic clean, flexible, and reusable.

PreviousTriggering WorkflowsNextVersioning Workflows

Last updated 8 days ago

Workflow Environment Variables in Looply allow you to define reusable sets of values that can be injected into your workflow at runtime. Each environment consists of a profile - a JSON object containing key-value pairs - that can be used to dynamically configure workflow behaviour. You can create multiple profiles per workflow, select which one to use at runtime, and set a default profile to fall back on when no specific selection is made. This helps keep your workflows clean, flexible, and easy to maintain across different environments or use cases.

Managing & Using Environment Variable Profiles

Environment variables in Looply make it easy to configure workflow behaviour dynamically - without hardcoding values into each step. With environment profiles, you can switch between sets of values tailored for different environments like dev, qa, staging, or prod.

Creating & Managing Profiles

To manage environment variable profiles:

  1. Open your workflow in the Workflow Studio.

  2. Click the workflow settings menu (⋮) and select Environment Variables.

  3. In this section, you can:

    • Create new profiles for different environments.

    • Edit each profile’s JSON data to suit the needs of that environment.

    • Set a default profile, which is used when no other profile is specified.

    • Rename existing profiles.

    • Duplicate profiles

    • Delete profiles that are no longer needed.

Each profile is essentially a JSON object of key-value pairs that will be injected into the workflow’s payload at runtime.

Selecting a Profile for Execution

Once profiles are set up, executing a workflow with a specific profile is easy:

  1. Click Execute in the top-right of your workflow.

  2. A dialog will appear prompting you to select an Execution Profile from a dropdown.

  3. Choose the profile you want (e.g. prod, staging, dev) and click Execute.

The selected profile’s environment variable data will be injected into the payload and accessible to all steps in the workflow.

💡 Tip: You can also reference environment variables as parameters in function steps, conditions, or integrations using the workflow data binding menu.

Developer API

For advanced usage or automated execution, environment variable profiles can also be selected programmatically via the Developer API. See the Developer API documentation for details on how to pass a profile name as part of your workflow execution payload.

Workflow API