Front and Resend: Conversation-Resolved Follow-Up Email Template

When a Front conversation is marked resolved, this Spojit template sends the customer a branded follow-up email through Resend that invites feedback and closes the loop on the support interaction.

What It Builds

A Webhook trigger fires when Front signals that a conversation has been resolved. A Connector node on the front connector looks up the conversation and its contact so you have the customer name and email, then a Connector node on the resend connector uses send-email to deliver a short follow-up from your own verified domain. The result is a consistent post-resolution touch on every closed ticket without anyone remembering to send it.

The Prompt

Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow, connecting the tools for you:

Build a workflow with a Webhook trigger that fires when a Front conversation is resolved. Use the Front connector to fetch the conversation and its contact so I have the customer's name and email address. Then use the Resend connector to send that customer a short, friendly follow-up email from my verified domain thanking them for reaching out, confirming their issue is resolved, and inviting them to reply with feedback. Skip sending if no email address is found.

Connectors Used

  • Webhook trigger - receives the resolved-conversation event from Front and exposes its JSON body as {{ input }}.
  • front - reads conversation and contact details with tools such as get-conversation and get-contact so the email is addressed to the right person.
  • resend - sends the branded follow-up with send-email from your own verified sending domain.

Customize It

Change the email copy in the prompt to match your tone, add a link to a one-question survey or review page, or tell Miraxa to include the conversation subject so the message references the exact issue. You can also adjust which Front event counts as resolved (for example only conversations in a specific inbox) by naming that condition in the prompt before you generate the workflow.

Tips

  • Verify your sending domain in Resend before going live so follow-ups land in the inbox rather than spam. Spojit reads the verified domain through the resend connection you add under Connections.
  • Keep the two Front lookups in Direct mode: picking get-conversation and get-contact explicitly is deterministic and spends no AI credits, which is ideal for a predictable single-tool call.
  • If you would rather draft a personalized message per customer, switch the email-writing step to an Agent-mode Connector node so the agent can tailor the wording to the conversation subject.

Related

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