entitys icon

entitys

entitys.io app node: choose an operation (Webhook POST or HTTP POST).
Join our community

Overview

This node allows you to send HTTP POST requests to a specified URL with a customizable JSON payload and additional headers. It is useful for integrating with APIs or web services that accept POST requests, enabling workflows to push data or trigger actions remotely.

Common scenarios include:

  • Sending form data or event information to an external API.
  • Triggering webhooks on third-party platforms.
  • Posting JSON data to REST endpoints for automation purposes.

For example, you could use this node to send order details from your workflow to an e-commerce platform's API or notify a monitoring service by posting JSON alerts.

Properties

Name Meaning
URL The endpoint URL where the HTTP POST request will be sent.
JSON Body The JSON payload to include in the body of the POST request.
Additional Headers Optional HTTP headers to add to the request. You can specify multiple headers as name-value pairs.

Output

The node outputs an array with one item per input item processed. Each output item contains a json object with the following structure:

  • statusCode: The HTTP status code returned by the server (e.g., 200, 404).
  • headers: The response headers received from the server.
  • body: The parsed JSON response body from the server.

No binary data output is produced by this node.

Dependencies

  • Requires internet access to reach the specified URL.
  • No special credentials are enforced by the node itself, but the target API may require authentication tokens or API keys to be included in the headers.
  • No environment variables or external configurations are required by the node beyond what the user provides in the properties.

Troubleshooting

  • Invalid JSON Body: If the JSON Body property contains invalid JSON syntax, the node will throw an error indicating "Invalid JSON Body". To fix this, ensure the JSON is well-formed.
  • Network Errors: If the URL is unreachable or times out, the node will fail. Verify the URL is correct and accessible from the n8n instance.
  • Authentication Issues: If the target API requires authentication, make sure to provide the necessary headers (e.g., Authorization) in the Additional Headers property.
  • Unexpected Response: If the response is not JSON or the server returns an error status code, inspect the statusCode and body fields in the output to diagnose issues.

Links and References

Discussion