Automated Teampay Approval Chasing
Every morning, WebRun opens Teampay, finds purchase requests that have sat waiting on approval for more than a day, logs each one in Airtable with the requester and amount, and creates a follow-up task in Notion for the approver so spend requests stop stalling in the queue.
How do I chase pending Teampay purchase approvals?
WebRun checks Teampay every morning for purchase requests pending approval for more than a day, logs each one in Airtable with the requester and amount, and creates a follow-up task in Notion for the approver. It never approves a request or moves money itself, so spend requests get chased instead of stalling silently in the queue.
- Stalled purchase requests get chased instead of sitting silent
- Every aging request has an owner and a follow-up task
- Approvers see exactly how long a request has been waiting
Built for finance teams · procurement managers · businesses using Teampay · department approvers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.teampay.coin a real browser with your saved login - no setup, no API keys. -
1
Teampay - find pending purchase requests
teampay.co
WebRun opens Teampay to find pending purchase requests. - Open Teampay and review requests awaiting approval
- Filter to requests pending for more than one business day
- Capture the requester, amount, and reason for each
Done when Every request pending more than a day is captured with its details.
-
2
Airtable - log aging requests
airtable.com
WebRun logs aging requests in Airtable. - Add a row for each aging request with days pending
- Update the days pending on requests already logged
- Mark a row resolved once the request is approved or declined
Done when The Airtable base lists every aging request with its current age.
-
3
Notion - create the follow-up task
notion.so
WebRun creates the follow-up task in Notion. - Create a follow-up task for the approver on each aging request
- Include the requester, amount, and days pending
- Leave the approval decision to them
Done when Every aging request has a follow-up task assigned in Notion.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun approve the purchase request or move money?
No. WebRun never sends a payment, issues a refund, or transfers funds on its own. It only tracks how long a request has been pending and reminds the approver, leaving the decision to a human.
What counts as an aging request?
Any Teampay purchase request still awaiting approval for more than one business day, not requests that were just submitted.
Does a request get chased twice?
No. It updates the same Airtable row and Notion task on each run rather than creating a new one, so the requester only sees one active follow-up.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.