InfobloxInstall

Summary

Creates a new Threat Defense scheduled report in Infoblox by POSTing a JSON body to /api/atcfw/v1/scheduled_reports on the configured CSP realm.

Inputs

• dataFields (required) — Resource mapper for the report's fields. Columns are loaded from the Infoblox 'Atcfw' API spec's POST body schema (read-only fields, id and _ref are skipped). Supports auto-mapping or defining fields manually. Falls back to an empty list with a notice if the schema can't be loaded.
• jsonBody — Extra request body as JSON, merged over the mapped fields (JSON keys override mapped values with the same name). Use for fields missing from the schema. Defaults to {}.
• queryParameters — Optional name/value pairs appended to the request URL as query string parameters.

Output shape

One output item per input item, containing the JSON response from the Infoblox API for the newly created scheduled report (typically the created record).

If the API returns a non-object value, it is wrapped as { result: value }. With Continue On Fail enabled, failures return an item with an 'error' message instead of throwing. Requires Infoblox CSP API credentials.

Examples

Example 1: Create a scheduled report using mapped fields

Resource: TD Scheduled Report, Operation: Create; map the required fields (e.g. name and the schedule/report settings from the schema) in Fields.

Example 2: Create a report from a JSON payload built upstream

Leave Fields empty and set JSON Body to an expression such as {{ JSON.stringify($json.reportConfig) }}.

Links

• n8n community nodes installation guide