Resend and HTTP: Appointment Confirmation Email Template
When your booking system posts a new in-store appointment to Spojit, this template confirms the details against your scheduling API and sends a branded confirmation email through Resend.
What It Builds
A Webhook trigger receives each new appointment from your booking system. A Connector node in Direct mode uses the http connector to call your scheduling system's REST API and confirm the time, location, and customer details. A second Connector node then sends a polished confirmation email through Resend from your own verified domain.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that triggers when my booking system posts a new in-store appointment to a webhook. Take the appointment id from the payload and call my scheduling system's REST API to look up the confirmed date, time, store location, and customer email. Then send a branded confirmation email through Resend with the customer's name, appointment date and time, and store address. If the API says the appointment is cancelled, skip the email.
Connectors Used
- Webhook trigger - starts a run when your booking system posts a new appointment.
- http - Miraxa connects to your scheduling system's REST API to confirm the appointment details.
- Resend - sends the branded confirmation email from your verified domain.
Customize It
Change the fields you pull from the API (add a confirmation code or pharmacist name), adjust the email subject and body copy, or add a reminder line for what to bring. To text instead of email, swap the Resend step for your SMS provider's API in the prompt.
Tips
- Verify your sending domain in Resend first so confirmations land in the inbox, not spam.
- Keep the API lookup in Direct mode for one exact call: it is fast and costs no AI usage.
- Add a Custom HMAC secret on the Webhook trigger so only your booking system can start runs.
- Keep this retail and admin only: confirm appointment logistics, not clinical details.