Mailhook to MySQL: Emailed CSV Loader Template

A Mailhook trigger receives an emailed CSV attachment, parses it with the csv connector, and inserts the rows into a MySQL table without any mailbox setup.

What It Builds

This template starts with a Mailhook trigger, so any system that can email a CSV to your unique Spojit address kicks off a run within seconds. An Attachment node fetches the CSV bytes, a Connector node on the csv connector parses them into structured rows, and a Connector node on the mysql connector inserts those rows into your table. The result is a hands-off pipeline that loads emailed exports straight into your database.

The Prompt

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

Build a workflow that triggers on a Mailhook, fetches the emailed CSV attachment, parses it into rows with the csv connector, and inserts those rows into the customers table in MySQL.

Connectors Used

  • Mailhook trigger - generates a unique address; any email with a CSV attached starts a run.
  • Attachment node - fetches the CSV attachment bytes referenced by the trigger.
  • csv connector - parses the file into structured rows you can map to columns.
  • mysql connector - inserts the parsed rows into your target table.

Customize It

Change the table name in the prompt to your own target, and name the columns you want loaded so the rows map cleanly. To restrict who can feed the workflow, add a From allowlist or Subject regex on the Mailhook trigger. If the file needs cleanup first, ask Miraxa to dedupe or filter rows with the csv connector before the MySQL insert.

Tips

  • The Attachment node only saves on a Mailhook workflow, and the default size limit is 10 MB per attachment.
  • Use the mysql connector's insert-rows action in Direct mode for predictable, no-AI-cost loads.
  • Run a small test file first and check the inserted row count in the execution log before pointing the real export at the address.

Related

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