Skip to main content
Question

How can I attach the workspace output (ZIP file) to an email in FME Flow instead of just sending a download URL?

  • October 30, 2025
  • 1 reply
  • 50 views

mda
Contributor
Forum|alt.badge.img+7

Hi everyone,

I have a workspace in FME Flow that generates a ZIP file as output (stored in the default EngineResults folder). After the workspace finishes, an email is sent via a Topic and Email Subscription to notify the user. Currently, the email includes a ${fme_job_download_url}, which works for internal users but not for external users since they don’t have access to FME Flow.

I’d like to attach the generated ZIP file directly to the email instead of sharing the download link. Has anyone implemented this before? What’s the best way to configure FME Flow so the email automatically includes the output file as an attachment?

Thanks for your help!

1 reply

zoe.forbes
Safer
Forum|alt.badge.img+5
  • Safer
  • November 6, 2025

Hi ​@mda,

Sorry your question has gone unanswered until now! Here’s one way you could do this:

In these steps, Workspace A is the main workspace (the one which generates the Data Download zip) and Workspace B is a second, new workspace.

  1. Create a webhook to run Workspace A with the Data Download service. 
  2. Create the new Workspace B. Add a Creator.
  3. Add a HTTPCaller. Have it call the Workspace using the previously-created URL with &opt_reponseformat=json appended:
    https://<hostname>/fmedatadownload/<repo>/<workspace>.fmw?opt_showresult=false&opt_servicemode=sync&opt_responseformat=json
    Authenticate the request with a token or Web Connection.
  4. Add a JSONFragmenter with JSON Query json["serviceResponse"]["url"], and a FilenamePartExtractor to obtain the name of the zip file.
  5. Add an AttributeManager to create the filepath from the filename. This will look something like:
    $(FME_SHAREDRESOURCE_SYSTEM)/temp/engineresults/@Value(zip_file_name)
  6. Use an Emailer Transformer to send the email with the zip file attached.

I’ve attached a workspace to this message which performs this workflow - you just need to fill out necessary fields in the HTTPCaller (step 3) and the Emailer (step 6).

Please let me know if you have any questions!