Overview
This node, named "entitys," supports two main operations: Import and Export. The Export operation sends data via an HTTP POST request to a specified URL with a customizable JSON payload and optional additional headers. This is useful for integrating workflows with external APIs or services that accept POST requests to receive data.
Common scenarios include:
- Sending processed data from n8n workflows to third-party APIs.
- Triggering remote actions by posting JSON data.
- Exporting workflow results to webhooks or custom endpoints.
For example, you might use this node to send order details to an external order management system or push sensor data to a monitoring service.
Properties
| Name | Meaning |
|---|---|
| Operation | Choose between "Import" (trigger on incoming HTTP POST) or "Export" (send data via POST). |
| URL | The endpoint URL where the HTTP POST request will be sent. |
| JSON Body | The JSON payload to send as the body of the POST request. |
| Additional Headers | Optional HTTP headers to include in the POST request. Specify multiple name-value pairs. |
Output
The node outputs an array with one item containing a json object structured as follows:
statusCode: The HTTP status code returned by the POST request.headers: The response headers received from the server.body: The parsed JSON response body from the server.
This output allows subsequent nodes to handle the response, check for success, or process returned data.
Dependencies
- Requires an active internet connection to reach the specified URL.
- No special API keys or credentials are enforced by the node itself; however, if the target API requires authentication, users must provide appropriate headers (e.g., Authorization) via the "Additional Headers" property.
- Uses n8n's built-in HTTP request helper for making the POST call.
Troubleshooting
- Invalid JSON Body: If the JSON Body input is not valid JSON, the node throws an error indicating "Invalid JSON Body." Ensure the JSON syntax is correct.
- HTTP Request Failures: Network issues, incorrect URLs, or server errors can cause the HTTP request to fail. Check the URL and network connectivity.
- Missing Required Fields: The URL field is required for the Export operation. Make sure it is provided.
- Headers Format: Additional headers must be provided as name-value pairs. Incorrect formatting may lead to unexpected request behavior.