INNORIX Platform | Collect Files from Many Devices When the Previous Transfer Ends With Follow-Up Actions

How this solution works

This page shows how to collect files from multiple source devices when the preceding transfer ends and run follow-up actions after collection completes. 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

Gather files from multiple source devices into a collection destination when the preceding transfer ends, then run configured actions once collection completes. Both the start of collection and the work that follows it are driven by the same workflow.

Key components

Multiple source devices
Collection destination
Completion-based trigger (after previous transfer)
Follow-up actions (after collection)

How it fits your workflow

Use this solution when collection must follow an earlier transfer and the gathered files then need further handling, such as notifications, archiving, or a processing script. It keeps the sequencing and the post-collection steps in one configured workflow.

Common use cases

Archive gathered logs once collection finishes
Notify an operations team when consolidation completes
Hand collected files to a processing script
Roll nightly device backups into a single retention job

COMMON QUESTIONS

Frequently asked questions

Find answers to the most common questions about this configuration.

How do I trigger collection after a transfer and run follow-up actions?

Configure the completion trigger, source devices, collection destination, and supported actions.

When do follow-up actions run?

Verify whether actions depend on overall collection completion or individual source results.

How do I troubleshoot a collection workflow that stops?

Inspect the preceding transfer status, source availability, trigger settings, and logs.

How this solution works

Overview

Key components

Multiple source devices
Collection destination
Completion-based trigger (after previous transfer)
Follow-up actions (after collection)

How it fits your workflow

Common use cases

Archive gathered logs once collection finishes
Notify an operations team when consolidation completes
Hand collected files to a processing script
Roll nightly device backups into a single retention job

COMMON QUESTIONS

Frequently asked questions

Find answers to the most common questions about this configuration.

How do I trigger collection after a transfer and run follow-up actions?

Configure the completion trigger, source devices, collection destination, and supported actions.

When do follow-up actions run?

Verify whether actions depend on overall collection completion or individual source results.

How do I troubleshoot a collection workflow that stops?

Inspect the preceding transfer status, source availability, trigger settings, and logs.

Collect Files from Many Devices When the Previous Transfer Ends With Follow-Up Actions

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 Files from Many Devices When the Previous Transfer Ends With Follow-Up Actions

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