An Agent Compute node runs a command on one of your On-Premise Agents for each incoming file and passes the command's result on as data. Use it to run a program that exists only inside your network, for example a validation tool, a legacy format converter, or a script that registers each file in an internal system, as one node of an Automation.

Agent Compute accepts file items, and it accepts data items by writing each one to a .json file first.

Settings

Remote Server selects the Agent that runs the command. Command is the name of an entry in the Agent configuration file's commands setting, matched exactly, including capitalization. The entry defines the executable and its command-line arguments on the Agent host. Command is static text and does not accept a TransformScript template.

Arguments supplies names and values for the entry's commands.schema parameters. Each value accepts a TransformScript template. For example, an argument named InputPath with the value {{ attributes.path }} supplies the incoming Files.com path to the Agent template {{.InputPath}}.

The command definitions are yours to maintain on the Agent host. This keeps approval of local programs with the host administrator, while Automation authors select the approved work and supply its inputs. Restart the Agent after editing its configuration file. The Agent checks the command name when the command runs. Because that approval list is maintained on the host, Files.com cannot check the command when the Automation is saved; a command that is not on the list fails at run time rather than at save.

What the Next Node Receives

Agent Compute passes on one data item for each command it ran, containing the command's exit code as payload.exit_code, its standard output as payload.stdout, and its standard error as payload.stderr. A Transform node after it can parse payload.stdout. Because a nonzero exit code fails the item, every item that continues on the main path has an exit code of 0.

Errors

A command that is not approved on the Agent, or that exits with a nonzero code, fails that item. Error Handling rules on the node determine what happens to a failed item.