Getting Started

Learn how to quickly get started on building integrations with Laminar. This guide will help you familiarize with concepts and terminologies you will come across on the Laminar platform.

Goal: In this example, we will build an order fulfilment workflow. We will receive an incoming new order, send order to warehouse for processing, and update the order status.

0. Create a workspace

When you sign up to use Laminar, the first step is to create a workspace. You can invite other colleagues to your workspace and manage their roles.

Creating a workspace

1. Create a workflow

In Laminar, every integration starts with creating a workflow. A workflow is a logical sequence of steps that represent a business operation (ex: Fetching product inventory data, Filtering product inventory data by category).

Creating a workflow

2. Add steps to workflow

Once the workflow is set up, the next phase is adding steps to it. A workflow step is a specific task that accepts an input, performs some processing, and produces an output. In other words, a function.

The input of a every step is the Global Workflow Object — a data structure that keeps track of the input and output of each step up to the current point. This comprehensive input allows users to access previous step's output in order to transform it.

Global Workflow Object Model

Different types of workflow steps

There are multiple workflow step types, each designed for specific tasks, such as HTTP requests, data transformations, and more. See the complete list for more information.

For the purpose of this tutorial, we are going to focus on the two most common:

• HTTP Requests: This step type is used to send or receive data through REST APIs. In our integration example, we are going to use this block to make a request to the <insert_api> to retrieve <insert_description_of_data>

• General Transform: This step type is used to transform data to a desired format.

A flow's logic is typically written in JavaScript . The following imports are made readily available to users in the flow editor to facilitate data transformations:

- lodash as _
- date-fns: { format, parseISO }

Adding workflow steps

3. Executing Workflow

Now that we have all workflow steps configured, we can start testing out our workflows.

In Laminar, there are two ways to trigger a workflow: Inside the app and remotely via API call.

In-app Execution

In-App Workflow Execution

Remote Execution

To achieve this, we simply need to make a POST request to a workflow execution url which can be generated within the Laminar platform.

Users must first create an API key associated to the workspace and perform the following request

Remote Execution

4. Analyzing Execution Results

After executing our first workflow, we can now inspect execution logs through the console panel to validate the result of the execution.

Analyzing execution results

5. See Also

Advanced