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
  • Designing integrations
  • Building atomic integrations
  • Workflow execution lifecycle

Was this helpful?

  1. Platform

Integration Design

The design pattern behind Laminar's solution to custom integrations

Last updated 12 months ago

Was this helpful?

Designing integrations

An integration in Laminar is can be described as a sequences of Flows, which each can run the following:

  1. Initial API Request (optional)

  2. Data Transformations

  3. Control Flow

  4. Final API Request (optional)

Building atomic integrations

Business logic for any integration can be expressed in terms of Workflows in Laminar. Each workflow fulfils specific business logic for an integration using its sequence of flows.

Flows carry out the requests and data transforms necessary to accomplish atomic integration objectives.

Workflow execution lifecycle

Example workflow sequence with N number of Flows that run as part of the Workflow