Webhook

The Webhook node is a trigger that exposes a public URL. When that URL receives an HTTP request, the workflow starts automatically with the received payload as input data.

Function

Activates the workflow when a GET or POST request is made to the URL generated by Floogos. The payload (query params for GET, body for POST) is available to all subsequent nodes.

Configuration

Field	Type	Description
url_webhook	Auto	Automatically generated URL. Displayed when selecting the node in the editor.

Available URLs

Each webhook generates two URLs:

Environment	Path	Usage
PROD	/webhooks/<hash>	Real traffic. Records statistics and applies security policies.
DEV	/webhooks-dev/<hash>	Identical to PROD but with extended response for debugging.

Both URLs are available in the side panel (drawer) of each webhook under the Webhooks section of the platform.

HTTP Response

The response behavior varies depending on the environment and the final node of the workflow:

Scenario	PROD (/webhooks/<hash>)	DEV (/webhooks-dev/<hash>)
Workflow ends with webresponse	Code, headers, and body configured in the node	Same as PROD
Workflow executed without webresponse	{"status": 200}	{"response": {...}, "message": "Workflow launched successfully (METHOD)."}
Error during execution	{"status": 500}	{"error": "error message"}

Production URL (PROD)

The production URL returns minimal responses to avoid exposing internal workflow data:

• If the workflow ends with a webresponse node, the response is fully customizable (HTTP status code, headers, JSON body).
• In any other case, the response is limited to {"status": 200} on success or {"status": 500} on error.

Development URL (DEV)

The DEV URL returns the full workflow response, useful for debugging:

• If there is a webresponse → same response as PROD.
• Without webresponse → returns the complete workflow result plus a confirmation message.
• On error → returns {"error": "error message"} with failure details.

Tip

Use the DEV URL to inspect the complete workflow output during development. In production, control the HTTP response using the webresponse node when you need a custom body or status code.

Data Available in the Workflow

The node injects the _request object alongside the body or query string payload:

{
  "payload": { "...body or query fields..." },
  "_request": {
    "method": "POST",
    "timestamp": "2026-04-28T10:00:00.000Z",
    "headers": { "content-type": "application/json" },
    "ip": "1.2.3.4",
    "isDev": false
  }
}

Common Usage

• Receiving events from external services (Stripe, Shopify, GitHub, etc.)
• Processing public form submissions
• Integrating CRM / ERP systems via HTTP
• Triggering workflows from custom scripts or applications

Security

Webhooks support configurable security policies from the platform:

• Rate limiting — request limit per time window (per IP or global)
• IP filtering — whitelist or blacklist with CIDR support (e.g. 10.0.0.0/8)
• HMAC-SHA256 signature — verifies the body is signed with a shared secret
• Schedule restrictions — allows calls only on specific days and time ranges

See the full guide at Webhook Management.

Recommendations

• Share the URL only with trusted services.
• Always activate a security policy in production to prevent abuse.
• Use the DEV URL during development to separate test traffic from real traffic.
• Check the Access Insights to monitor traffic in real time.

Multi-language

• help.es: Activa el trigger de webhook para iniciar un workflow
• help.en: Activate the webhook trigger to start a workflow