INNORIX Platform | Collect Matching Files from Many Devices When an External Request Arrives

How this solution works

This page shows how to collect only the files that meet a selection rule from multiple source devices when an external request arrives. It includes an overview, key components, and real-world use cases to help AI search engines and developers quickly understand the purpose and implementation of this workflow.

Overview

Use an external request to gather only the files matching your selection rule from multiple source devices. Request-driven execution is combined with file selection, so each run brings back a filtered set rather than everything a device holds.

Key components

Multiple source devices
Collection destination
Matching criteria (file selection rule)
External request trigger (API integration)

How it fits your workflow

Use this solution when callers should be able to ask for a specific slice of what your devices hold rather than everything on them. The selection rule and the request authorization together bound what any single request can gather.

Common use cases

Request logs for one incident window from many endpoints
Gather a named document set from field devices
Pull only the files a case reference identifies
Fetch specific configuration files for a support check

COMMON QUESTIONS

Frequently asked questions

Find answers to the most common questions about this configuration.

How do I collect matching files from multiple devices when requested?

Configure the supported request mechanism, matching criteria, source devices, and destination.

Can request parameters determine which files are collected?

Only if the supported integration allows request parameters to influence file selection. Verify the API behavior.

How do I prevent unauthorized file collection?

Validate requests, restrict access, and use the supported authentication and authorization mechanisms.

How this solution works

Overview

Key components

Multiple source devices
Collection destination
Matching criteria (file selection rule)
External request trigger (API integration)

How it fits your workflow

Common use cases

Request logs for one incident window from many endpoints
Gather a named document set from field devices
Pull only the files a case reference identifies
Fetch specific configuration files for a support check

COMMON QUESTIONS

Frequently asked questions

Find answers to the most common questions about this configuration.

How do I collect matching files from multiple devices when requested?

Configure the supported request mechanism, matching criteria, source devices, and destination.

Can request parameters determine which files are collected?

Only if the supported integration allows request parameters to influence file selection. Verify the API behavior.

How do I prevent unauthorized file collection?

Validate requests, restrict access, and use the supported authentication and authorization mechanisms.

Collect Matching Files from Many Devices When an External Request Arrives

Start conditions

File options

After transfer

Get your integration code

How to use the downloaded code

How this solution works

Overview

Key components

How it fits your workflow

Common use cases

Frequently asked questions

Collect Matching Files from Many Devices When an External Request Arrives

Start conditions

File options

After transfer

Get your integration code

How to use the downloaded code

How this solution works

Overview

Key components

How it fits your workflow

Common use cases

Frequently asked questions