Update a card limit in Ramp from an approved request
Automatically update a Ramp card limit from an approved Slack request with Stepwork. Find the employee’s card and apply the new limit for its effective period.
- Use case
- Helpdesk & requestsOps
- Best for
- Finance Operations Manager, Accountant
- Applications used
Ramp
Slack
- Business outcome
- Time savings
The problem
The bump is approved in a thread. The card still declines.
Limit increases get approved in Slack threads, then finance copies each one into Ramp by hand. The employee waits, and sometimes the card declines at the worst moment.
Temporary increases are the easiest to get wrong. The new limit goes on without an end date, and a short-term bump quietly becomes permanent.
The outcome
Limit changes apply within minutes of approval
Stepwork finds the employee’s card in Ramp and applies the approved limit with its effective period. The run records who asked, the old and new limits, and which approval it came from.
- The request names the approved limit and its effective period.
- A card that does not belong to the employee stops the run.
- The Slack reply shows the old and new limits.
The process
From approved request to a new card limit
Finance posts the approved limit change in Slack. Stepwork applies it in Ramp, in the same order every time.
- Step 1
Request it in Slack
A finance teammate posts the approved change: the employee, the card’s last four digits, the new limit, and its effective period. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the card
Stepwork signs in to Ramp and opens the employee’s card with those last four digits. If the card does not belong to that employee, the run stops.
- Step 3
Apply the new limit
Stepwork sets the approved limit and its effective period, the same edit finance makes by hand.
- Step 4
Confirm and reply in Slack
Stepwork checks the saved limit against the request, then posts the old and new limits back in Slack.
Why Stepwork
The limit matches the approval, end date included
A deterministic agent runs the limit change path you recorded in Ramp. It applies the limit and period from the approved request, and it does not approve anything on its own.
Similar use cases
Similar use cases
- Issue a virtual card for an approved purchase in RampCreates a Ramp virtual card with the approved limit, category lock, and expiry for the requesting employee.
- Suspend cards for a departed employee in RampSuspends all physical and virtual cards for the departing employee and notes open subscriptions tied to them.
Create a purchase order in NetSuite from an approved requestCreates the PO in NetSuite with vendor, lines, cost coding, and delivery terms from the approved purchase request.
FAQ