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 program to run, and it is static text, because the Agent accepts only commands that are approved in its configuration file. Arguments is a list of names and values passed to the command, and each value accepts a TransformScript template, so {{ attributes.path }} passes the incoming file's path.

The approved-command list is yours to maintain on the Agent host, and the Agent enforces it when the command runs. Files.com cannot check the command when the Automation is saved, so 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.