Laminar
  • Laminar
  • Platform
    • Overview
    • Getting Started
    • Advanced
      • Workflows
        • Global Workflow Object
        • HTTP Request Batching
        • Workflow Exit Points
        • Invoke Secondary Workflows
      • Configurations
      • Flows
        • Flow Types
          • HTTP Request
          • Data Transformations
        • Supported Languages
      • Managing Notifications
    • Best Practices
    • Keywords
      • lam.resolveThenExecute
      • lam.exit
      • lam.execute
      • lam.asyncExecute
      • lam.httpRequest
      • lam.httpRequests
  • API
    • Executing a Workflow
    • Creating a Configuration
    • Authentication
    • Changelog
  • External Links
    • Book a Demo
    • Sign In
Powered by GitBook
On this page

Was this helpful?

  1. Platform
  2. Advanced
  3. Workflows

Workflow Exit Points

Learn how to stop a workflow execution gracefully

When building integrations, you may wish to terminate a workflow early if some preconditions are not met.

Laminar solves this with the lam.exit keyword which can be used to stop a workflow execution and optionally return a payload providing more context on the exit.

(payload) => {
  const { step_1 } = payload;
  if (step_1.inventory.quantity < 1) {
    return {
      "lam.exit": true,
      // payload to be returned
      "data": { 
        "error": "Out of stock"
      }
    };
  }
  // Continue with normal processing...

PreviousHTTP Request BatchingNextInvoke Secondary Workflows

Last updated 2 months ago

Was this helpful?