Mailhook and Knowledge: Brand-Deal Contract Archive Template

Forward every sponsorship contract to a Mailhook address and Spojit embeds the PDF into a searchable Knowledge collection so you can ask about past deal terms anytime.

What It Builds

This template uses a Mailhook trigger to give your workflow its own email address. When a brand emails you a PDF contract, an Attachment node fetches the file bytes and a Knowledge node in Embed mode adds it to a persistent collection. Over time you build a private archive of every deal, queryable in plain language so you never lose track of exclusivity windows, payment terms, or usage rights.

The Prompt

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

Create a workflow with a Mailhook trigger so brands can email me sponsorship contracts. When a PDF attachment arrives, fetch the attachment and embed it into a persistent Knowledge collection called "Brand Deals" along with the sender's email and the subject line, so I can later ask questions about past deal terms.

Connectors Used

  • Mailhook - the trigger; gives the workflow its own @mailhook.spojit.com address that starts a run on every email.
  • Attachment - fetches the PDF bytes from the incoming email (Mailhook workflows only).
  • Knowledge - embeds each contract into the reusable "Brand Deals" collection you query later.

Customize It

Change the collection name to match how you organize deals, or rename it per client. You can add the {{ input }} subject and sender to the embedded metadata, or extend the prompt to also email yourself a one-line confirmation once a contract is archived.

Tips

  • Knowledge embed handles OCR, so scanned or image-based PDFs are still searchable.
  • Use one persistent collection for the archive rather than Transient mode, which discards after a single run.
  • Filter the Mailhook so only mail from known brand domains starts a run, keeping junk out of the archive.

Related

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