Daily Ramp spend digest in Slack

By General Input

Every weekday morning, get a clean Slack summary of yesterday's Ramp spend with top transactions, policy flags, department rollups, and new vendors.

Integrations

  • Ramp
  • Slack

Type

Agentic Task

Categories

  • Finance
  • Operations

Build me a daily Ramp spend digest that posts to Slack every weekday morning. The trigger is a cron schedule that runs Monday through Friday at 8am Eastern.

When it runs, the agent should pull data from Ramp covering the prior business day. Use Ramp's List Transactions to get card transactions, List Reimbursements for any new employee reimbursements, and List Bills for any new bills. Also use List Vendors so the agent can detect vendors that appeared for the first time yesterday compared to recent history.

Then summarize the day into a clean Slack message with these sections:

1. A short executive commentary line at the very top, two or three sentences max, that calls out anything unusual versus the prior week. Examples: a category that roughly doubled, a one-off large purchase, an unusual concentration in one department, or a brand new high-spend vendor. If nothing is unusual, say so plainly.

2. Total spend yesterday across card transactions, reimbursements, and bills, with each component broken out.

3. Top 5 largest transactions, with merchant or vendor, amount, cardholder or submitter, and department.

4. Anything flagged for policy violations or missing receipts, listed individually with cardholder and amount so finance can chase them.

5. Spend rolled up by department, sorted highest to lowest, with the prior week's same-day amount next to it for quick comparison.

6. Any new vendors that appeared yesterday for the first time, with the amount and what was purchased.

Format the output as a Slack message using sections, bold headers, and bullet lists so it scans cleanly on desktop and mobile. Use Slack's Send a Message action to post it to a finance Slack channel that I will specify, like #finance-pulse. Post as a single threaded message, not multiple messages.

On weekends and US bank holidays, do not run. If yesterday had zero activity, still post a short 'no activity yesterday' note so the team knows the workflow is healthy.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes