Workflows

Trigger Block

The starting point of your LemmeBuild workflow, handling input data to initiate processes.

The Trigger Block is the essential starting point for any workflow in LemmeBuild. It initiates the workflow process by receiving input data, making it crucial for workflows that rely on incoming data to execute subsequent actions. Whether the data comes from external services, user inputs, or automated triggers, the Trigger Block handles it all and passes it down the workflow chain.

Trigger Block


Functionality

Input Data Handling

The Trigger Block is designed to handle input data in JSON format, but it's versatile enough to accept data from multiple sources, including:

  • API calls: Directly receive data from external APIs.
  • Webhooks: Get data pushed directly from other web services.
  • Manual inputs: Input data manually entered by users.

Once the input data is received, it’s stored in a special variable called $trigger. This variable becomes accessible to all subsequent blocks within the workflow, allowing for seamless integration and processing of the data across your workflow.

Key Features

  • Data Availability: The input data received by the Trigger Block is immediately made available to all subsequent blocks through the $trigger variable, ensuring smooth data flow across your workflow.
  • Input Flexibility: The Trigger Block can handle a variety of input types, including:
    • JSON Inputs: Structured data in JSON format.
    • Empty or null values: In case no input data is provided, the block gracefully handles empty or null inputs.

Why Use the Trigger Block?

The Trigger Block is your entry point to creating dynamic, data-driven workflows in LemmeBuild. By receiving and handling input data with ease, it sets the stage for all subsequent actions, ensuring your workflows run smoothly from start to finish.


Leverage the capabilities of the Trigger Block to effectively kick-start your automated processes in LemmeBuild.