Delivery & files

A workflow that produces something useful should hand it to you. Catalyst gives a workflow two ways to deal with files: sending results out by email, and taking files in that it uses on every run.

Emailing the result

Add an Email node to send a workflow’s output to an inbox.

Recipient — defaults to you (the workflow’s owner); set specific addresses to send elsewhere.
Body — write it as Markdown (Catalyst renders it to a clean formatted email), HTML (sent as-is), or plain text. Assemble the body from earlier nodes with a template.
Attachments — attach files the workflow produced, such as a generated report or a spreadsheet a Python node wrote.

Combined with scheduling, this is how a workflow becomes a recurring report that simply shows up.

Files a workflow produces

When a Python node writes a file, Catalyst uploads it and exposes it on that node as {{ node.files }} — a list of the files with their names and links. Later nodes use that directly: attach {{ build_report.files }} to an Email node and the report goes out, no manual link-wrangling in between.

Files a workflow consumes

Some workflows need the same input every run — a reference list, a price sheet, a template document. Attach those to the workflow itself with the Files button in the editor toolbar. On every run, Catalyst places them where your Python node can read them, so you upload once and every run has them.