Knowledge and SMTP: Lease Clause Q and A Template

When a tenant emails a lease question to a monitored mailbox, Spojit looks up the answer in your embedded lease library and replies from your own office address.

What It Builds

An Email trigger watches a monitored mailbox for incoming tenant questions. A Knowledge node in Query mode searches your embedded lease library and returns a plain-language, cited answer drawn only from your documents. A Send Email step delivered through the SMTP connector replies from your real office address so the tenant sees a familiar sender.

The Prompt

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

Build a workflow that triggers when a tenant emails our leasing mailbox. Take their question, query our lease library knowledge collection for a clear answer with the relevant clause cited, and reply to the sender through our SMTP connection using our office email address with the cited answer and a note to contact the office for anything not covered.

Connectors Used

  • Email trigger - watches your leasing mailbox and starts a run on each new tenant question.
  • Knowledge - queries your embedded lease library and returns a cited answer.
  • SMTP - sends the reply from your own office address.

Customize It

Change the mailbox it watches, point the query at a different collection (for example a specific property or building), or adjust the reply wording and the office signature. You can also tell Miraxa to flag questions the library cannot answer for a human to handle.

Tips

  • Embed your lease documents into a persistent Knowledge collection first so the Query step has something to cite.
  • Use the SMTP connection (not the built-in mail service) when replies must come from your own domain.
  • A Knowledge Query answers from your documents only, so it will not invent clauses that are not in the library.

Related

Ready to build this?

Start on the free plan: 500 AI credits a month, no card needed.

Start free

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