All templates
For payments operations, marketplace finance teams & fintech ops

Reconcile your Cashfree payout batches for you

Every morning, WebRun opens Cashfree Payments, checks yesterday's payout batch for how many payouts succeeded and how many failed, archives the payout report to Google Drive, and posts a reconciliation summary to Slack so your ops team starts the day knowing exactly what still needs attention.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:30 AM WebRun
1 Cashfree Payments check payout batch status
2 Google Drive archive the payout report
3 Slack post the reconciliation summary
Run a sample
In short

How do I reconcile my Cashfree payout batches each day?

WebRun checks Cashfree Payments every morning for yesterday's payout batch status, archives the full report to Google Drive, and posts a reconciliation summary to Slack. It never retries a payout or moves money itself, so your ops team starts the day with a clear read on what succeeded, failed, or is still pending.

  • Failed payouts get flagged the same morning they happen
  • A full payout batch archive builds up automatically in Drive
  • Ops teams start the day with a clear reconciliation, not a raw export

Built for payments operations · marketplace finance teams · fintech ops · gig platform finance

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 www.cashfree.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Cashfree Payments - check payout batch status
    cashfree.com
    WebRun in Cashfree Payments: check payout batch status
    WebRun opens Cashfree Payments to check payout batch status.
    • Open the Cashfree dashboard and check yesterday's payout batch
    • Count how many payouts succeeded, failed, or are still pending
    • Note the total amount in each status

    Done when Yesterday's payout batch is checked by status and amount.

  3. 2
    Google Drive - archive the payout report
    drive.google.com How to Automate Google Drive
    WebRun in Google Drive: archive the payout report
    WebRun opens Google Drive to archive the payout report.
    • Save the payout batch report to your finance folder
    • Append it to the running monthly archive
    • Keep prior reports untouched

    Done when Yesterday's payout report is archived in Drive.

  4. 3
    Slack - post the reconciliation summary
    slack.com How to Automate Slack
    WebRun in Slack: post the reconciliation summary
    WebRun opens Slack to post the reconciliation summary.
    • Post the count and total for succeeded, failed, and pending payouts
    • Call out failed payouts that need retrying
    • Leave it as a read only reconciliation summary

    Done when Slack has today's payout reconciliation summary.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.cashfree.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Payout summary · Slack
OutputWhat each run produces - A daily reconciliation summary of Cashfree payout batches by status, archived in Drive.
Summary
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 it retry a failed payout or move money itself?

No. WebRun never sends a payment, issues a refund, or transfers funds on its own. It only reads payout batch status and reports on it, leaving any retry or transfer to you in Cashfree.

Does it flag failed payouts separately?

Yes. Failed payouts are called out in the Slack summary so your team can see what needs retrying without scanning the full batch report.

Can I look back at past payout batches?

Yes. Every day's report is archived in Google Drive, so you have a searchable record beyond the Slack summary.

Put this on autopilot.

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