What does this automation do?
A payment event is matched to its customer, checked against your refund window, and borderline cases go to a person.
What can you do with it?
- Settle the clear-cut refunds without a queue
- Send the borderline cases up with the policy reasoning
- Keep one written record of every refund decision
The Steps
This automation runs in 4 steps:
- When Stripe — New Payment
- Then Stripe — Retrieve Customer
- Then Taskade AI — Ask an agent ("Refund Reviewer")
- Then Taskade — Add Task
What makes this different from a Zapier-style flow?
The "Refund Reviewer" step is not a one-off model call. It is a Taskade AI agent that knows your refund window and exception rules, remembers every refund decision it has made, so every run builds on the last one instead of starting from an empty prompt.
A stateless "ask the model" step forgets everything the moment it returns. An agent keeps its knowledge and its memory between runs, carries its own tools, and can be handed work by other automations.
Who is this automation for?
Built for support and finance teams handling refunds. A payment event is matched to its customer, checked against your refund window, and borderline cases go to a person.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New Payment" from Stripe.
- Add the action "Retrieve Customer" from Stripe.
- Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Refund Reviewer".
- Add the action "Add Task" from Taskade.
- Enable the toggle in the top-right corner to activate the automation.
Prefer to describe it instead? Click Build this flow with AI above and Taskade wires the trigger, the steps, and the agent for you.