entitys Export icon

entitys Export

entitys.io: Export (HTTP POST).
Join our community

Overview

This node performs an HTTP POST request to a user-specified URL, sending a JSON payload in the request body. It is designed for scenarios where you need to export or send data to an external API endpoint that accepts JSON input via POST. Typical use cases include integrating with third-party services, submitting form data, triggering webhooks, or exporting data from n8n workflows to external systems.

For example, you might use this node to:

  • Send customer data to a CRM system's API.
  • Post event information to a monitoring service.
  • Export processed data to a custom backend endpoint.

Properties

Name Meaning
URL The full URL of the API endpoint where the POST request will be sent.
JSON Body The JSON payload to include in the POST request body. Can be a JSON object or stringified JSON.
Additional Headers Optional HTTP headers to include in the request. You can add multiple headers by specifying their name and value pairs.

Output

The node outputs an array with one item per input item. Each output item contains a json field structured as follows:

{
  "statusCode": <HTTP status code number>,
  "headers": { <response headers as key-value pairs> },
  "body": { <parsed JSON response body from the HTTP POST request> }
}
  • statusCode: The HTTP status code returned by the server (e.g., 200, 404).
  • headers: The HTTP response headers received.
  • body: The parsed JSON response body from the API.

The node does not output binary data.

Dependencies

  • Requires an active internet connection to reach the specified URL.
  • No special credentials are enforced by the node itself, but the user may need to provide appropriate authentication headers via the "Additional Headers" property if the target API requires it.
  • Uses n8n's built-in HTTP request helper to perform the POST request.

Troubleshooting

  • Invalid JSON Body: If the JSON Body input is not valid JSON (when provided as a string), the node will throw an error indicating "Invalid JSON Body". To fix this, ensure the JSON Body is correctly formatted JSON or a valid JSON object.
  • Network Errors: If the URL is unreachable or incorrect, the node will fail with a network-related error. Verify the URL and network connectivity.
  • Authentication Issues: If the target API requires authentication, make sure to add the necessary headers (e.g., Authorization) in the Additional Headers property.
  • Unexpected Response: If the API returns a non-JSON response or an error status code, inspect the statusCode and body fields in the output to diagnose the issue.

Links and References

Discussion