InfobloxInstall

Summary

Updates an existing Infoblox Threat Defense scheduled report by ID, sending a PUT request to /api/atcfw/v1/scheduled_reports/{id} with a body built from mapped fields and optional JSON.

Inputs

• resourceId (required) — ID of the scheduled report to update. It is URL-encoded and appended to the endpoint path.
• dataFields (required) — Resource mapper listing body fields. Fields are loaded from the Infoblox Atcfw API schema for the credential's realm. Supports auto-map or defining fields manually.
• jsonBody — JSON object merged over the mapped fields, so its keys override mapped values. Use it for fields missing from the schema. Defaults to {}.
• queryParameters — Extra name/value query-string pairs added to the request.

Output shape

One output item per input item, containing the JSON response from the Infoblox API for the updated scheduled report. If the response isn't an object, it is wrapped as {result: value}.

PUT usually replaces the whole object, so include all required fields, not just the changed ones. With Continue On Fail enabled, a failure returns an item with an error message instead of stopping. Requires the Infoblox CSP API credential.

Examples

Example 1: Change the name and recurrence of an existing scheduled report

Resource ID = report ID; map the required fields (e.g. name, recurrence settings) in Fields or supply them via JSON Body.

Example 2: Update a report using a field missing from the schema

Resource ID = report ID; JSON Body = {"name":"Weekly Threat Report"} plus any other fields the API needs.

Links

• n8n community nodes installation guide