Early access

Handle a Refund Request End to End

For refund requests that need three tabs. DuckyHelper reads the request in Intercom, finds the charge in Stripe, checks it against your refund policy, sets up the refund and drafts the reply. Money only moves when you slide to approve.

YOU SAY

“Handle this Intercom refund request: find the Stripe charge, check our 30-day policy, and prepare the refund and the reply.”

Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud.

DUCKYHELPER DOES

01
Learn the web APIs of Intercom and Stripe, first time onlyBuilt from each site's own buttons, forms and requests. Kept on your device and reused next time.getConversation(id)createDraft(conversation, body)findCharge(email)createRefund(charge, amount)
02
Read the request
03
Find the charge in Stripe
04
Check it against your policy
05
Set up the refund for your slide to approve
06
Draft the reply

You getFair, fast refunds. Every refund is checked against your policy, and it's built to wait for your OK before money moves.

Handle a Refund Request End to End

A run, drawn from this page · early access on Mac

WHERE IT ASKS FIRST

It's built to wait for your OK.

It does the work, then stops with the refund ready for you. You see exactly what it wrote, then Send, Edit or Deny.

If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.

StripeRefundNeeds your OK

For your slide to approve.

MAKE IT ALWAYS ON

Do it once. Then let it repeat.

When it's done, it offers to keep doing it: whenever a new one comes in. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.

Always-on automations are in early access on Mac.

Make this automatic?Trigger

Handle a Refund Request End to End

WhenWhenever a new one comes in

DoesDuckyHelper checks the charge and your policy, sets up the refund in Stripe and drafts the reply. The money waits for your OK.

ThenAsks you before anything goes out

FAQ

Before you ask it.

What do I say?

Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Handle this Intercom refund request: find the Stripe charge, check our 30-day policy, and prepare the refund and the reply."

Why is the second time faster?

The first time, it writes small JavaScript tools for Intercom and Stripe and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.

Will it send anything without me?

It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.

Why not just do it by hand?

Refunds mean finding the charge, checking the policy and writing back, each in a different tool.

Can it keep doing this on its own?

Yes. When it's done it offers to make it automatic (whenever a new one comes in). Each run goes the same way and is still built to ask before it sends or pays.

Can I use this today?

Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.

MORE JOBS LIKE THIS

Every use case →