Resend and HTTP: Inspection Report Delivery Template
When an inspection completes, a webhook fires and Spojit fetches the report from your inspection platform, then emails it to the buyer and seller from your own domain through Resend.
What It Builds
A Webhook trigger receives the completion event from your inspection platform. A Connector node in Direct mode uses HTTP to call the platform's API and pull the finished report, and a final Connector node sends a branded email through Resend to both the buyer and the seller. The result: every completed inspection lands in the right inboxes within seconds, no manual forwarding.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow triggered by a webhook from my inspection platform when an inspection is marked complete. Take the inspection ID from the webhook, call my inspection platform's API over HTTP to fetch the finished report, then use Resend to email the report from inspections@mydomain.com to both the buyer and the seller with the property address in the subject line.Connectors Used
- Webhook trigger - starts the run when an inspection is marked complete.
- HTTP - Miraxa connects to your inspection platform's API to fetch the report.
- Resend - sends the report email from your verified domain.
Customize It
Change the sender address and subject line to match your brand, swap the recipients to add an agent or coordinator, or adjust the prompt so it only sends when the report status is passed. You can also tell Miraxa which fields from the webhook payload to include in the email body.
Tips
- Verify your sending domain in Resend first so the report does not land in spam.
- Secure the webhook with an HMAC secret so only your inspection platform can trigger it.
- Keep the report-fetch node in Direct mode for a fast, predictable call with no AI cost.