Mailhook and FTP: Emailed Supplier Catalog Attachment to FTP Archive Template

When a supplier emails a catalog attachment, this Spojit template grabs the file and uploads it to a dated folder on your FTP archive automatically.

What It Builds

A Mailhook trigger gives the workflow its own inbound email address. When a supplier sends their catalog to that address, an Attachment node fetches the attached file bytes, and a Direct-mode FTP connector node uploads it into a date-stamped archive folder. Every catalog that lands in the inbox is filed away without anyone touching it.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow with a Mailhook trigger so suppliers can email catalogs to it. When mail arrives, fetch the attached file and upload it to our FTP server into a folder named by today's date, keeping the original filename. If there is no attachment, skip the upload.

Connectors Used

  • Mailhook trigger - the workflow's own inbound address; any email to it starts a run.
  • Attachment node - fetches the emailed file bytes (Mailhook workflows only).
  • FTP connector (Direct mode) - uploads the file to your archive server.

Customize It

Change the folder naming in the prompt (for example by supplier name instead of date), point it at a specific remote path, or set it to handle multiple attachments per email. You can also add a filename prefix so archived catalogs are easy to spot.

Tips

  • The Attachment node only works in Mailhook-triggered workflows, so keep that trigger in place.
  • Use Direct mode on the FTP node here: the action is fixed (upload), so there is no need for AI to pick the tool.
  • Confirm your FTP connection has write access to the target archive path before going live.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.