A Send via AS2 node sends each incoming file to an AS2 Partner through one of your AS2 Stations. Use it to deliver EDI documents to a partner as the last node of a workflow that transformed, validated, or encrypted them.

Send via AS2 accepts file items, and it accepts data items by writing each one to a .json file first, so the output of a Transform node can be sent directly.

Settings

The node takes the AS2 Station, the AS2 Identity that sends the message, and the AS2 Partner, the trading partner that receives it, both selected from the AS2 configuration on your site, and both must belong to the same site or Workspace as the Automation, because the Automation runs with its owner's permissions. The Subject of the AS2 message defaults to AS2 EDI Transaction and can be set on the node, so a partner that routes on the subject receives the value they expect.

What the Next Node Receives

Send via AS2 sends one message per file and passes its items on unchanged, with the outcome recorded on each item, including the outgoing message's identifier. A Move File node after it can move each sent file to a sent folder of your own.

Errors

A message the partner did not accept fails that item with the error processing-failure/as2-delivery. Error Handling rules on the node determine what happens to a failed item. A Send Email node on the Error path can notify your team. The Message Disposition Notification and transmission information for each message are recorded in the AS2 Logs.

Send via AS2 vs. the AS2 Outbox Folder

Files.com also sends a file to an AS2 Partner when the file is written to that partner's outbox folder under as2_home. Use the outbox folder when a process already writes files there and every file goes to that one partner. Use a Send via AS2 node when sending is one node of a workflow, when different branches of the same run deliver to different partners, or when the message subject is set for that workflow.