Mailhook and Knowledge: SOP Update Email to Q&A Template
When someone emails an updated standard-operating-procedure document to your Mailhook address, Spojit embeds it into a persistent Knowledge collection so staff always query the latest procedures.
What It Builds
A Mailhook trigger gives the workflow its own dedicated inbox address. When an updated SOP arrives, an Attachment node fetches the document bytes and a Knowledge node embeds it into a persistent SOP collection. From then on, any workflow or person querying that collection gets answers grounded in the newest version, no manual re-upload required.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow with a Mailhook trigger so people can email updated SOP documents to a dedicated address. When mail arrives, fetch the attached document with an Attachment node, then embed it into a persistent Knowledge collection named "SOPs" so staff can always query the latest procedures. Reply to the sender confirming the SOP was indexed.Connectors Used
- Mailhook trigger - a dedicated inbox address that starts a run whenever an SOP is emailed in.
- Attachment node - fetches the emailed document bytes for embedding.
- Knowledge node (Embed) - adds the document to a persistent, queryable SOP collection.
- Send Email node - confirms the update back to the sender.
Customize It
Change the collection name from SOPs to match your team, switch the Attachment node to Multiple if updates arrive as several files, or drop the confirmation reply if you do not need one. You can also tell Miraxa to only index attachments whose subject line contains a keyword.
Tips
- Use a persistent collection (not Transient) so embedded SOPs stay queryable across future runs.
- The Attachment node works only in Mailhook workflows; it reads from
{{ input }}. - Knowledge Embed handles common document types and OCR, so scanned PDFs index too.