All templates

Automated Tamara Refund and Dispute Alerts

Every few hours, WebRun opens the Tamara merchant portal, checks for new refund and dispute requests, logs each one in Airtable with the order and amount, and creates a review task in Notion so nothing sits unresolved past Tamara's response window.

Runs on WebRun · Strict Lockdown policy
Every 4 hours WebRunorchestrates each step
1 Tamara check refund and dispute requests
2 Airtable log each request
3 Notion create the review task
In short

How do I track and review Tamara refund and dispute requests?

WebRun checks your Tamara merchant portal every few hours for new refund and dispute requests, logs each one in Airtable with its order, amount, and deadline, and creates a review task in Notion. It never approves a refund or moves money itself, so every request reaches a human reviewer well before its response window closes.

  • Refund and dispute requests get a reviewer well before the deadline
  • Every open request is tracked in one place instead of the portal alone
  • Nothing lapses unanswered past Tamara's response window

Built for merchants using Tamara · ecommerce customer service teams · BNPL merchant partners · finance operations

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens tamara.co in a real browser with your saved login - no setup, no API keys.

  2. 1
    Tamara - check refund and dispute requests
    tamara.co
    WebRun in Tamara: check refund and dispute requests
    WebRun opens Tamara to check refund and dispute requests.
    • Open the Tamara merchant portal and check for new refund or dispute requests
    • Capture the order reference, amount, and reason given
    • Note the deadline Tamara shows for responding

    Done when Every new refund or dispute request is captured with its deadline.

  3. 2
    Airtable - log each request
    airtable.com
    WebRun in Airtable: log each request
    WebRun logs each request in Airtable.
    • Add a row for each new request with the order, amount, and deadline
    • Leave a status column open for the outcome
    • Skip any request already logged from an earlier check

    Done when The Airtable base lists every open refund and dispute request.

  4. 3
    Notion - create the review task
    notion.so
    WebRun in Notion: create the review task
    WebRun opens Notion to create the review task.
    • Create a review task for each new request with its deadline
    • Link back to the Airtable row for full detail
    • Leave the decision on the refund or dispute to the reviewer

    Done when Every open request has a review task in Notion.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
tamara.co
ScheduleRuns automatically on this cadence
Every 4 hours
DeliveryHow each run's result reaches you
Dispute log · Airtable
OutputWhat each run produces - A logged list of open Tamara refund and dispute requests with deadlines, each with an assigned Notion task.
List
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will WebRun approve the refund or move money?

No. WebRun never sends a payment, issues a refund, or transfers funds on its own. It only logs the request and assigns it for review, leaving the refund decision to a human.

Does it track the deadline for responding?

Yes. It captures the response deadline Tamara shows for each request and includes it in both the Airtable row and the Notion task so nothing lapses unanswered.

Will a request get logged twice?

No. It checks the Airtable base before adding a row, so a request already logged from an earlier check is skipped.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.