Mailhook and NetSuite: Vendor Bill Email Intake Template
Forward a vendor-bill email to a dedicated Mailhook address and Spojit reads the attached PDF, extracts the line items, and creates a NetSuite record ready for AP review.
What It Builds
A Mailhook trigger gives the workflow its own inbox address, so any vendor bill forwarded there starts a run. An Attachment node fetches the PDF bytes, an Agent-mode Connector node reads the document and returns the vendor, totals, and line items as structured JSON, and a NetSuite Connector node creates a vendor bill record for your accounts-payable team to review and approve.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
When a vendor bill email arrives at a Mailhook address, fetch the attached PDF, extract the vendor name, bill number, bill date, due date, line items, and total amount, then create a draft vendor bill in NetSuite with those details for AP to review.
Connectors Used
- Mailhook - the trigger; a unique
@mailhook.spojit.comaddress that starts a run on every forwarded email. - Attachment node - fetches the PDF attachment bytes for extraction.
- NetSuite - creates the vendor bill record for AP review.
Customize It
Change the extracted fields to match your chart of accounts (add memo, subsidiary, or a department code), set the NetSuite record to post directly instead of staying a draft, or route bills over a threshold to a Human approval step before the NetSuite record is created.
Tips
- Give the Agent-mode Connector node a Response Schema so the extracted vendor, totals, and line items come back as reliable structured JSON.
- The Attachment node only works inside Mailhook workflows; set it to Single when each email carries one bill PDF.
- Make sure your NetSuite connection has permission to create vendor bills before going live.