Start with the destination. A person reading a brief summary may want plain text or Markdown; a spreadsheet may need CSV; an API usually expects structured JSON; a document to print or share may need PDF. Do not choose a format solely because a workflow node makes it easy to produce.
Ask what the next step needs: field names, ordering, character encoding, layout, or editability. Test one realistic output in the receiving app. Include an empty result and a malformed input in your test, and define whether a retry should overwrite or create another output.
The workflow is finished only when its recipient can use the result without manual repair.