Lamatic Webhook icon

Lamatic Webhook

Starts the workflow when a Lamatic webhook is called

Overview

The Lamatic Webhook node triggers an n8n workflow when it receives a POST request on a specified webhook path. It is designed to integrate with Lamatic services by listening for incoming webhook calls and starting the workflow accordingly. This node supports multiple authentication methods to secure the webhook endpoint.

Common scenarios include:

  • Automating processes triggered by events in Lamatic, such as task updates or new data submissions.
  • Integrating Lamatic with other systems by reacting to webhook notifications.
  • Using different authentication schemes to control access to the webhook.

For example, you might configure this node to listen on the path /webhook and require Basic Auth. When Lamatic sends a POST request to that URL with valid credentials, the workflow starts processing the received data.

Properties

Name Meaning
Path The URL path segment where the webhook listens for incoming POST requests (e.g., "webhook").
Authentication Method used to authenticate incoming webhook requests. Options: Basic Auth, Header Auth, JWT Auth, None.
Note Informational notice stating the node automatically responds after the last node finishes.
Respond Defines when and how the node responds to the webhook call. Options:
- Immediately: Respond as soon as this node executes.
- Using 'Respond to Lamatic Webhook' Node: Response controlled by a separate response node.
Insert a 'Lamatic Respond to Webhook' node to control when and how you respond. Notice shown only if "Respond" is set to use the separate response node, linking to more details.

Output

The node outputs JSON data containing the webhook request details and any additional workflow data:

  • json.headers: HTTP headers from the incoming webhook request.
  • json.params: URL parameters.
  • json.query: Query string parameters.
  • json.body: The body payload of the webhook request.

If authentication is successful, the output also includes a JWT payload (if applicable) merged into the workflow data.

The node does not output binary data.

Dependencies

  • Requires an HTTP server environment capable of receiving POST requests at the configured path.
  • Supports multiple authentication methods; appropriate credentials or tokens must be configured in n8n.
  • No external API dependencies beyond the webhook caller (Lamatic service).
  • Uses internal utility functions for authentication validation and response handling.

Troubleshooting

  • Method Not Allowed (405): If the webhook receives a non-POST request, it will reject it with a 405 status. Ensure the webhook caller uses POST.
  • Authentication Errors: If authentication fails, the node responds with the appropriate HTTP status and message. For Basic Auth failures, it returns a 401 with a WWW-Authenticate header prompting for credentials.
  • Missing Request or Response Object: The node throws an error if the HTTP request or response objects are undefined, indicating misconfiguration or runtime environment issues.
  • Response Mode Misconfiguration: If the response mode is set to use a separate response node but that node is missing or misconfigured, the workflow may not respond correctly.

Links and References

Discussion