Start Free

Send Matching Files to One Device When an External Request Arrives With Follow-Up Actions

Combine request-triggered execution, file matching criteria, and post-transfer actions in a single-destination workflow.

  • Send files
  • Matching files only
  • When an external request arrives
  • Follow-up actions

Start conditions

When should it start?

File options

After transfer

You can add more than one action.

What should happen after the transfer?

Your example is ready.

Download the generated example

Download a runnable example for the transfer you configured.

Choose a language

Transfer Example, JavaSource code, run configuration, README (a complete project generated for your configuration)ZIP

or Download from Git

No sign-up needed to download.

Run the example

Set it up in QuickConnect the devices and download the .env file
Run the example locallyApply the .env file, then follow the README

Running a real transfer needs an INNORIX Platform account.

Frequently asked questions

Find answers to the most common questions about this configuration.

  • How do I configure request-triggered matching-file transfers with follow-up actions?

    Configure the request mechanism, file selection criteria, destination, and supported follow-up actions.

  • What happens when a request matches no files?

    Verify the product's empty-selection behavior and the resulting workflow status.

  • How do I troubleshoot failed request-triggered transfers?

    Check request validation, access permissions, matching rules, transfer status, and execution logs.