Mailhook and Knowledge: Supplier Datasheet Intake Template

Turn supplier product datasheets emailed to your store into a searchable Knowledge collection your staff can look up on demand.

What It Builds

This Spojit template gives you a dedicated Mailhook address that suppliers email their product datasheets to. Each inbound message fires a workflow that pulls the attached files with an Attachment node and feeds them into a Knowledge node in Embed mode. The documents land in a persistent collection, so a staff member can later run a Knowledge query and get retail product details like ingredients, pack sizes, and storage guidance without digging through their inbox.

The Prompt

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

Create a workflow with a Mailhook trigger so suppliers can email product datasheets to a dedicated address. When mail arrives, fetch every attachment and embed the documents into a persistent Knowledge collection called "Supplier Datasheets" so staff can search retail product details later.

Connectors Used

  • Mailhook - the trigger; gives the workflow its own email address that suppliers send datasheets to.
  • Attachment - fetches the attached datasheet files from the inbound email.
  • Knowledge - embeds the documents into a reusable collection your team can query.

Customize It

Change the collection name in the prompt to match your store, or point datasheets from different suppliers into separate collections. You can also add a step that only embeds PDF and image attachments, or that sends a confirmation email back to the supplier once their datasheet is indexed.

Tips

  • The Attachment node only works in Mailhook workflows; use Multiple mode to capture every file on a message.
  • A persistent collection is best here so the same datasheets stay searchable across runs; reserve Transient mode for one-off lookups.
  • Knowledge supports OCR, so scanned datasheets and image attachments still become searchable text.

Related

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