Skip to main content

HTTP Trigger

The HTTP Trigger allows you to start a workflow by sending an HTTP request to a Boltic-generated endpoint. It is ideal for building APIs or creating workflows that run when an external system calls a URL.

Overview​

The HTTP Trigger acts as the entry point of your workflow, enabling external applications or users to send data directly to Boltic. You can use it to create custom APIs, process webhook requests, or connect different systems.

Key Features​

  • Supports multiple HTTP methods like GET, POST, PUT, and DELETE.
  • Captures and processes request body, query parameters, and headers.
  • Allows defining path parameters for dynamic URLs.
  • Enables synchronous execution when used with the Response node (workflow waits and returns the result).
  • Ideal for API endpoints, webhook integrations, and data ingestion workflows.

Configuration​

Method​

Select one or more HTTP methods (GET, POST, PUT, DELETE) that can trigger the workflow.

Path Parameters​

Define dynamic path variables that can be used in your URL. These values will be available in the workflow payload.

Query Parameters​

Specify query parameters to capture from the request URL. These can be referenced later in the workflow.

Request Body​

Provide JSON or text payload as input. The request body data becomes available through {{payload}}.

Headers​

Include any headers required by the request. These can be accessed using {{payload.headers}}.

How It Works​

  1. Boltic provides a unique webhook URL for the workflow.
  2. When an HTTP request is sent to this URL, the workflow is triggered.
  3. The request data (body, parameters, headers) is passed as payload to subsequent nodes.
  4. Optionally, add a Response node to send back an HTTP response after the workflow finishes.

Example Use Case​

Example: Collecting Form Submissions

  1. A user submits a form that sends a POST request to your Boltic workflow URL.
  2. The workflow captures the form data from the request body.
  3. It stores the data in a Boltic Table or forwards it to another service.
  4. The Response node replies with a confirmation message like:
{
  "message": "Form submission received successfully."
}

Notes​

  • The workflow must complete within 90 seconds. If it exceeds this limit, the caller receives a timeout error.
  • Use the Response Activity to define structured responses such as JSON, Text, XML, etc.
  • Common use cases include building APIs, processing webhooks, and returning data to clients synchronously.