Ramp policy violation alerts in Slack with employee history

Build me a real-time policy violation triage workflow for Ramp transactions, with Slack as the human review surface.

Trigger: poll Ramp for new card transactions, filtered to ones with the policy violation flag set. Anchor the workflow on Ramp.

When a flagged transaction fires, the agent should:

1. Call Ramp Get Transaction with the transaction ID from the trigger to pull full detail (amount, merchant, category, which policy rule was violated, the cardholder user ID, memo, receipt status, time).

2. Call Ramp Get User on the cardholder to get their name, email, department, and role.

3. Call Ramp List Transactions filtered to that same cardholder over the last 30 days so we can see whether this is a one-off or a repeat pattern. Count how many of those prior transactions also had a policy violation flag and roll that up as the repeat-offender signal.

4. Write a concise summary in plain English that includes: employee name and department, transaction amount and merchant, which policy rule was violated, repeat-offender status (e.g. "3rd violation in 30 days" vs "first time"), and a suggested next step. The suggested next step should be one of: auto-approve as a reasonable exception, ask the employee to add a memo or receipt, or escalate to the finance lead. Pick based on amount, the specific rule violated, and the repeat count.

5. Use Slack Send a Message to post that summary into a dedicated #ramp-policy-flags channel. Include a link back to the transaction in Ramp.

6. If the cardholder has had 2 or more flagged transactions in the last 30 days (this one included), use Slack Open a Conversation to start a DM with them, then Slack Send a Message to send a polite, friendly reminder. The DM should reference the policy rule, the transaction, and ask them to add a memo or receipt. Keep the tone respectful, not punitive. Do not DM first-time offenders, only repeat offenders.

Inputs the user should configure when running this:

- Slack channel for the team-facing alerts (default #ramp-policy-flags).

- Repeat-offender threshold (default 2 flagged transactions in 30 days triggers the DM).

- Lookback window for history (default 30 days).

- Optional: dollar threshold above which the suggested next step is always "escalate" regardless of repeat count.

Skip and do nothing if the transaction does not actually have a policy violation flag set, or if the cardholder cannot be resolved to a Slack user (in that case still post to the channel, just skip the DM).

Additional information

What does this prompt do?

Watches Ramp for new card transactions that break a policy rule, in near real time.
Posts a clean summary to a Slack channel with the employee, amount, merchant, rule that was broken, and whether this is a repeat issue.
Suggests a next step for finance: auto-approve as an exception, ask for a memo or receipt, or escalate.
DMs repeat offenders directly with a polite reminder so finance does not have to chase people one by one.

What do I need to use this?

A Ramp account with permission to read transactions, users, and policy data.
A Slack workspace where you can post into a review channel (for example #ramp-policy-flags).
An idea of what counts as a repeat offender for your team (default is 2 or more flagged charges in 30 days).

How can I customize it?

Change the Slack channel that receives the flag summaries, or split into one channel per department.
Adjust the repeat-offender threshold and the 30 day lookback window to match how strict your finance team wants to be.
Set a dollar amount above which the workflow always escalates instead of suggesting auto-approval.
Edit the tone of the cardholder DM, from gentle reminder to firm warning, depending on your culture.

Frequently asked questions

Does this only work for the policy violation flag, or any Ramp transaction?

It is built for policy violations. The workflow watches Ramp specifically for transactions that come in with the policy violation flag set, so normal in-policy spend never reaches Slack.

Will my whole team see every flagged transaction?

Only people in the Slack channel you choose will see the summaries. Most finance teams use a private channel like #ramp-policy-flags so it stays scoped to reviewers.

Will employees be DMed every time they bend a rule?

No. By default only repeat offenders get a DM, defined as 2 or more flagged transactions in the last 30 days. First-time issues are posted to the review channel only.

What does the suggested next step look like?

For each flagged charge the workflow proposes one of three actions: auto-approve as an exception, ask the employee for a memo or receipt, or escalate to the finance lead. The choice is based on amount, the specific rule, and the employee's recent history.

Can I use this with my Ramp sandbox before going live?

Yes. Connect your Ramp sandbox first, run a few test transactions through it, and confirm the Slack messages look right before pointing it at production.