Stripe and Front: Refund Request Inbox Routing Template

This Spojit template turns a Stripe dispute or refund event into a ready-to-handle conversation in your finance team's Front inbox, with the context already drafted.

What It Builds

A Webhook trigger receives the Stripe dispute or refund event. An Agent-mode Connector node reads the charge, customer, and reason fields and drafts a short summary of what happened and what the team needs to decide. A Front Connector node then opens a conversation in your shared finance inbox so a teammate can reply to the client and process the refund without leaving Front.

The Prompt

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

Build a workflow that triggers on a Stripe webhook when a dispute is opened or a refund is requested. Use an AI agent step to pull the charge amount, customer email, and dispute reason and draft a short summary of the refund request. Then open a new conversation in our Front "Finance" inbox addressed to the customer's email, with the summary as the first message so the finance team can review and respond.

Connectors Used

Webhook trigger - receives the Stripe dispute or refund event.
Stripe - the charge, customer, and dispute data the agent reads.
Front - opens the conversation in your shared finance inbox.

Customize It

Change the Front inbox name to match yours, swap the Stripe event to refunds only or disputes only, and adjust what the agent includes in the summary, for example order reference, payment method, or a suggested next step. You can also set a tag or priority on the new conversation by naming it in the prompt.

Tips

Secure the Stripe Webhook trigger with HMAC verification so only genuine Stripe events start a run.
Use Agent mode for the drafting step since it picks the right Stripe lookups, but switch the Front step to Direct mode for predictable, no-AI conversation creation.
Confirm your Front connection has access to the target inbox before going live.