Laminar
  • Laminar
  • Platform
    • Overview
    • Getting Started
    • Advanced
      • Configurations
      • HTTP Request Batching
      • Workflow Exit Points
      • Invoke Secondary Workflows
      • Managing Notifications
    • Best Practices
    • Keywords
      • lam.resolveThenExecute
      • lam.exit
      • lam.execute
      • lam.asyncExecute
      • lam.httpRequest
      • lam.httpRequests
  • Concepts
    • Workflows
      • Global Workflow Object
    • Flows
      • Flow Types
        • HTTP Request
        • Data Transformations
      • Flow Runs
      • Supported Languages
    • API Key
    • Configurations
    • API
      • Reference
        • Workspaces
          • Issues
          • Users
          • Invitations
            • Decline
            • Accept
            • Received
            • Created
          • Workflows
          • Flows
          • Auth credentials
          • Api keys
          • Api descriptions
        • Workflow
          • Execute
            • External
          • Flows
          • Executions
        • Users
        • Flows
          • Runs
          • Versions
          • Stats
          • Recent runs
          • Read
        • Configurations
          • Properties
          • Flow credentials
          • Workspace
        • Auth credentials
        • Api descriptions
        • Api keys
        • Transform
          • Test
        • Lami
          • Public
          • Direct
        • Auth
          • Signin
          • Register
          • Refresh
          • Me
          • Users
            • Password
    • Changelog
  • External Links
    • Book a Demo
    • Playground
    • Sign In
  • Specification
Powered by GitBook
On this page
  • 1. Creating a configuration
  • 2. Use configuration in workflow steps
  • 3. Execute workflow with specific configuration

Was this helpful?

  1. Platform
  2. Advanced

Configurations

Learn how to use configurations in Laminar

PreviousAdvancedNextHTTP Request Batching

Last updated 1 month ago

Was this helpful?

A common pattern in building integrations is validating them across different settings, environments or even customer profiles. For example, you may want to validate an integration using test credentials. In Laminar, this is handled by configuration stores.

With configuration stores, users can create different configurations and choose a specific configuration to execute a workflow.

1. Creating a configuration

The first step is to create key-value configuration pairs

Configuration keys are case-sensitive.

2. Use configuration in workflow steps

When you need to use configuration variables within your workflow steps definition, use the following format:

{{props.<configuration_key>}}

Example:

(data) => {
  let transformed_data = data.step_1.response
  
  return {
    "lam.httpRequest": {
      "method": "POST",
      "url": "{{props.WAREHOUSE_API_URL}}/warehouse/orders",
      "headers": {
        "Content-Type": "application/json"
      },
      "body": transformed_data
    }
  };
}

3. Execute workflow with specific configuration

In order to execute a workflow with a specific configuration, you need to add the configuration id to the workflow execution url. Refer to the example below:

# Execute workflow for Customer A
# workflow_execution_url: https://api.laminar.run/workflow/execute/external/<workflow_id>?api_key=<api_key>

curl -X POST '<workflow_execution_url>&configuration_id=<configuration_id>' \
  -H 'Content-Type: application/json' \
  -d '{
    "data": "your workflow input"
  }'
Creating configurations