ramp-manage-vendors

Upload vendor documents and track bulk OCR and matching status in Ramp.

2|1|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/ramp-public/skills --skill ramp-manage-vendors-ramp-public
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ramp-manage-vendors
Source: https://github.com/ramp-public/skills/tree/main/plugins/ramp/skills/ramp-manage-vendors
Command: npx skills add https://github.com/ramp-public/skills --skill ramp-manage-vendors-ramp-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vendor onboarding requires collecting and attaching documents like W-9/W-8 tax forms, contracts, COIs, and payment instructions to the right vendor records, then verifying that OCR and vendor matching completed correctly. Doing this manually through a dashboard is slow and error-prone, especially for bulk uploads. ## Core Features & Use Cases - Single Document Upload: Attach a base64-encoded document to a confirmed vendor UUID with a specific document category, or omit the vendor UUID to route the file into Ramp's matching and triage flow. - Bulk Upload with Dry Run: Upload many vendor documents in one JSON request, validate the payload with a dry run first, and receive a batch ID for tracking. - Status Monitoring: Poll bulk upload status to see OCR progress, matched and unmatched document counts, and which files need attention, including W-form tax detail extraction. - Use Case: A finance team receives 20 vendor W-9s and contracts by email. They bulk upload all files, let Ramp match them to vendors, then check the batch status to identify the two documents needing manual review. ## Quick Start Ask the agent to upload a W-9 PDF for a specific vendor and confirm the returned document UUID.

Frequently Asked Questions about ramp-manage-vendors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload a W-9 form to a vendor in Ramp?

Base64-encode the PDF file, then run the ramp vendors attach-document command with the vendor UUID, filename, content type, encoded content, and document category W9. Run it with the dry-run flag first to validate the request before the real upload.

How do I bulk upload vendor documents to Ramp?

Use the ramp vendors bulk-upload command with a JSON body containing a rationale and a documents array of base64-encoded files. Validate with a dry run first, then repeat without it to receive a batch ID for status tracking.

What if I don't know the vendor UUID for a document upload?

Omit the vendor UUID parameter entirely and the document enters Ramp's matching and triage flow instead of attaching directly. Never guess a vendor UUID when the vendor identity is uncertain.

Can I upload vendor documents through the Ramp MCP connector?

Document upload operations are CLI-only and not available through MCP. However, checking bulk upload status works through both the CLI and the MCP bulk upload status tool.

Why does my Ramp vendor upload return HTTP 422?

The rationale field is required on every command and must be a non-empty string under 1024 characters. Omitting it returns HTTP 422 with DEVELOPER_INVALID_SCHEMA in both agent and human modes.

When should I not use this vendor document upload workflow?

Do not use it for card transaction receipts, which belong to expense completion, or for bill invoice attachments, which belong to bill management. It is specifically for vendor onboarding and compliance documents.