Skip to main content

Connect Ramp to Zed

Give Zed governed access to Ramp’s 124 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Ramp to Zed in four steps

Admins approve the server once. Everyone in Zed then gets it through the same governed connection.

  1. 1

    Approve Ramp in Runlayer

    Add Ramp from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Zed to Runlayer

    Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Ramp’s 124 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Zed setup guide
  3. 3

    Sign in to Ramp

    Each user signs in to Ramp with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Ramp from Zed

    Ramp’s approved tools appear in Zed. Every call is checked against policy and recorded.

Tools

124 Ramp tools in Zed

Runlayer policy decides which of these Zed users can call.

  • Activate card

    Activate a card by its last four digits.

  • Add traveler loyalty program

    Compatibility route for callers that have not migrated to SetTravelerLoyaltyProgram.

  • Answer policy question

    Get an answer to a question about the expense policy or funds (amount, restrictions, etc).

  • Approve or reject bill

    Approve or reject a submitted bill that is pending approval.

  • Approve or reject reimbursement

    Approve or reject an employee reimbursement request for an out-of-pocket expense.

  • Approve or reject request

    Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval.

  • Approve or reject transaction

    Approve or reject a transaction awaiting your review.

  • Cancel reimbursement payment

    Cancel the payment on a reimbursement that has been approved but not yet paid out.

See all 124 Ramp tools

Control

What Runlayer can see and stop in Zed

Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.

  • Gateway policy (available)

    Every Ramp call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination