Destinations

Destination nodes deliver workflow results to an external system, storage location, database, or communication channel. They are normally placed at the end of a workflow path, but many destination nodes also emit a small status object or URL that can be used by later nodes.

Use destination nodes when a workflow needs to:

• Send email through SMTP, Gmail, or Outlook.
• Write a DataFrame to a database with automatic or mapped table handling.
• Copy generated files to the B2Win Suite server, a B2Win Suite Client, FTP, SFTP, Windows Share, SharePoint, or Infor IDM.
• Return delivery metadata such as copied-file details, database result data, or an uploaded document URL.

Existing Destination Pages

• Send Email (SMTP)
• Send Email (Gmail)
• Send Email (Outlook)
• DB Table Push
• DB Push
• Copy File (B2WS Server)
• Copy File (FTP)
• Copy File (SFTP)
• Copy File (Win Share)
• Copy File (SharePoint)
• Copy File (IDM)

Terminology

• Service configuration: A reusable connection record, such as SMTP, Microsoft Graph, FTP, SSH, Windows Share, B2Win Client, or Infor ION.
• NodeFile: A file produced or read by an upstream node. Copy and email destination nodes usually use the file's computed name when writing attachments or uploaded files.
• DataFrame: Tabular workflow data used by database destination nodes.
• Output metadata: The object, URL, or properties emitted by a destination node after the external action completes.