Lowcoder icon

Lowcoder

Consume Lowcoder API

Overview

This node, named "Lowcoder," is designed to consume the Lowcoder API within an n8n workflow. It primarily acts as a webhook listener that waits for HTTP requests on a specified path corresponding to a Lowcoder app or module ID. The node supports various HTTP methods (GET, POST, PUT, PATCH, DELETE, HEAD) and can be configured to ignore bot traffic such as link previewers or web crawlers.

Common scenarios where this node would be beneficial include:

  • Integrating Lowcoder apps or modules with n8n workflows by triggering workflows upon receiving HTTP requests from those apps.
  • Resuming paused workflows when an external event occurs in a Lowcoder app, using the provided webhook URL format.
  • Handling custom webhook events from Lowcoder apps with flexible HTTP methods and options.

Practical example:

  • A user configures this node to listen for POST requests from a Lowcoder app identified by its app ID. When the app sends data via webhook, the node captures the request details (headers, query parameters, body) and passes them into the workflow for further processing.

Properties

Name Meaning
Select App or Module The ID of the Lowcoder app or module to listen to. Can be selected from a searchable list or entered as an ID string matching [a-zA-Z0-9]{2,}.
Webhook HTTP Method The HTTP method to listen for on the webhook endpoint. Options: DELETE, GET, HEAD, PATCH, POST, PUT.
Ignore Bots Whether to ignore requests from bots like link previewers and web crawlers. If enabled, requests identified as bots will be rejected.
Resume the workflow notice Informational notice showing how to resume the workflow by calling a specific webhook URL with workflow execution ID and Lowcoder app ID.
Workflow-Execution-ID notice Informational notice indicating that the Workflow-Execution-ID is available via the n8n REST API.

Output

The node outputs the incoming webhook request data structured as follows:

  • json:

    • headers: Object containing all HTTP headers received in the request.
    • params: Route parameters extracted from the webhook URL.
    • query: Query string parameters from the URL.
    • body: The parsed request body if present; otherwise, an empty object.

  • binary: An empty object (no binary data output).

This structure allows downstream nodes to access all relevant parts of the incoming webhook request for processing.

Dependencies

  • Requires an API key credential for authenticating with the Lowcoder API.
  • Uses the external library isbot to detect bot user agents for the "Ignore Bots" option.
  • The node depends on n8n's webhook infrastructure to receive HTTP requests at dynamic paths based on the selected Lowcoder app ID.
  • No other external services are directly called during execution except the Lowcoder API for listing/searching apps.

Troubleshooting

  • Issue: Webhook requests are rejected with an authorization error.

    • Cause: The node may have detected the request as coming from a bot when "Ignore Bots" is enabled.
    • Resolution: Disable the "Ignore Bots" option if legitimate requests are being blocked, or ensure that the client sending requests does not identify as a bot.

  • Issue: Invalid Lowcoder App ID entered.

    • Cause: The app ID must match the regex pattern [a-zA-Z0-9]{2,}.
    • Resolution: Verify and enter a valid app ID or select one from the provided list.

  • Issue: Workflow does not resume after webhook call.

    • Cause: The webhook URL or HTTP method might be incorrect.
    • Resolution: Use the exact webhook URL format shown in the notice property and ensure the correct HTTP method is used.

Links and References

Discussion