AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation updates a Scheduled Report by sending an update request with specified fields to the corresponding API. It is useful in scenarios where you need to modify existing scheduled reports, such as changing recipients, adjusting report parameters, or updating organizational selections within the report schedule.

Practical examples include:

  • Changing the list of recipients who receive the scheduled report.
  • Updating the sub-organizations included in the report.
  • Modifying any other optional fields related to the scheduled report configuration.

Properties

Name Meaning
Id The unique identifier (ID) of the Scheduled Report to update.
Additional Body Fields Optional additional JSON fields to include in the update request body. This can contain:
- scheduled_report: A JSON object representing the scheduled report resource, including:
- scheduled_report_recipients: Array of recipient objects, each possibly containing organization info.
- selected_sub_orgs: Array specifying selected sub-organizations for the report.

Output

The node outputs JSON data representing the response from the update operation on the Scheduled Report. This typically includes confirmation of the updated report details or status information returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external service managing Scheduled Reports.
  • The node uses a base URL and headers preset for JSON communication with the API.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Scheduled Report ID will likely result in an error indicating the report was not found.
    • Malformed JSON in the "Additional Body Fields" may cause request failures.
    • Missing required authentication credentials will prevent successful API calls.
  • Error messages and resolutions:

    • "Scheduled Report not found": Verify that the provided ID corresponds to an existing scheduled report.
    • "Invalid JSON format": Ensure that the JSON entered in Additional Body Fields is correctly formatted.
    • Authentication errors: Confirm that the API key credential is correctly configured and has necessary permissions.

Links and References

  • Refer to the API documentation of the Scheduled Reports service for detailed schema and field descriptions.
  • n8n documentation on how to configure API key credentials and use collection-type input properties.

Discussion