RedPlanetHQ / RedPlanetHQ/core
New Integration: Ramp
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 194
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
Description
Add Ramp integration to sync corporate card transactions, expense data, reimbursements, and card management into CORE.
Reference Implementations
Existing Integrations (use as templates)
integrations/hubspot/- Similar business data systemintegrations/linear/- Project management integrationintegrations/slack/- For reference
Required Files Structure
integrations/ramp/
├── src/
│ ├── index.ts # Main entry, OAuth spec
│ ├── schedule.ts # Sync logic
│ ├── utils.ts # Ramp API utilities
│ ├── account-create.ts # OAuth setup
│ └── create-activity.ts # Activity formatting
├── package.json
├── tsup.config.ts
└── README.md
Ramp API Integration
OAuth Setup
- Use OAuth 2.0 authorization
- Create a developer app in Settings > Developer to obtain API credentials (requires admin access)
- OpenAPI spec available at:
https://docs.ramp.com/openapi/developer-api.json - Base documentation: https://docs.ramp.com/
Key Endpoints
GET /transactions- List transactionsGET /cards- List cardsGET /users- List usersGET /reimbursements- List reimbursementsGET /receipts- List receiptsGET /departments- List departmentsGET /locations- List locationsGET /vendors- List vendorsGET /accounting/connections- Accounting connections
Events to Track
- Transactions - New card transactions, transaction updates, merchant categorization
- Expenses - Expense submitted, receipt uploaded, memo added
- Reimbursements - Reimbursement requested, approved, paid
- Cards - Card issued, card locked, card terminated, limit changed
- Users - User invited, user activated, role changed
Implementation Tasks
- Set up basic integration structure following
integrations/github/src/index.tspattern - Implement OAuth 2.0 flow in
account-create.ts - Create API utilities in
utils.tsfor Ramp API calls - Implement sync logic in
schedule.tsfor transactions, cards, and users - Convert expense events to CORE activity format
- Add error handling and rate limiting
- Create integration documentation
- Add to
integrations/README.md
Technical Notes
- Machine-readable OpenAPI spec available for code generation
- Developer Assist (AI-powered) is built into the docs for real-time help
- Support available at developer-support@ramp.com for API issues
- Plain text docs available at
https://docs.ramp.com/llms.txt
Resources
- Ramp API Documentation
- Ramp Developer Tools
- Ramp Technology Partnerships
- Accessing the Developer API
Labels
enhancement, integration, new-feature
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing integrations/github/src/index.ts with integrations/hubspot/, integrations/linear/, and integrations/slack/. Then review the Ramp OpenAPI specification and map the required work across integrations/ramp/src/index.ts, schedule.ts, utils.ts, account-create.ts, and create-activity.ts. Done means OAuth, transaction/card/user sync, activity formatting, error handling, documentation, and the integrations README entry are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100