Resend and Knowledge: Auto-Acknowledge with Cited Answer Template

This Spojit template turns every inbound support email into an instant, branded acknowledgement that already contains a cited self-service answer plus a ticket reference.

What It Builds

A Mailhook trigger gives the workflow its own inbox address, so any email sent there starts a run. A Knowledge node in Query mode searches your help docs for the best match to the customer's question, and a Resend node sends a polished reply from your own verified domain. The result quotes the matched help-doc answer, links the source, and stamps a ticket reference for follow-up.

The Prompt

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

Build a workflow with a Mailhook trigger that receives inbound support emails. Use a Knowledge node in Query mode to find the best matching answer from my help-doc collection for the email subject and body. Then use Resend to email the customer back from my own domain with a friendly acknowledgement that includes the cited answer, a link to the source doc, and a generated ticket reference.

Connectors Used

  • Mailhook trigger - gives the workflow a dedicated inbox; each incoming email starts a run.
  • Knowledge node (Query mode) - searches your help-doc collection and returns a cited answer.
  • Resend - sends the branded acknowledgement from your verified sending domain.

Customize It

Tune the prompt to change the from name and reply-to address, the help-doc collection queried, the ticket reference format, or the tone of the acknowledgement. You can also ask for a fallback line when no confident match is found, so customers still get a courteous holding reply.

Tips

  • Verify your domain in Resend first so replies land in the inbox, not spam.
  • Embed your help docs into a persistent Knowledge collection before running, so Query mode has content to cite.
  • Keep the Knowledge node in Query mode (not Embed) for this lookup-only path.

Related

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