Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node allows you to create export jobs by sending a POST request to an exports endpoint. It is useful for scenarios where you need to programmatically trigger data exports, such as exporting asset layouts or other structured data from a system that supports this API. For example, you might use it to automate the extraction of configuration data or reports in JSON format for backup, analysis, or migration purposes.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional JSON fields to include in the body of the export request. The main option is: export which expects a JSON object (e.g., specifying asset_layout_ids as an array). This allows customization of what exactly to export by providing additional parameters in the request body. |
Output
The node outputs JSON data representing the response from the export creation API. This typically includes details about the export job created, such as its ID, status, and any metadata returned by the service. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests.
- Depends on the external API endpoint specified by the base URL credential.
- Uses JSON content type for request and response handling.
Troubleshooting
- Invalid JSON in Additional Body Fields: If the JSON provided in the "export" field is malformed, the node will likely throw a parsing error. Ensure valid JSON syntax.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key or token is correctly set up in n8n.
- API Endpoint Issues: Network errors or incorrect base URL configuration can prevent successful requests. Confirm the base URL and network connectivity.
- Unexpected Response Structure: If the API changes its response format, the node's output may not match expectations. Check API documentation for updates.
Links and References
- Refer to the API documentation of the service you are exporting from for detailed information on the export request body structure and response format.
- n8n documentation on creating HTTP Request nodes and using JSON input fields for further customization.