Ramp Connector
Description
Ramp is a spend management platform focused on automating accounts payable and procurement processes.
Use the Ramp component to manage transactions related to vendors, bills, reimbursements and more.
API Documentation:
This component was built using the Ramp REST API V1 Reference.
Connections
OAuth 2.0
key: ramp-oauth2Prerequisites
A Ramp account with developer or admin access is required to register an application.
Setup Steps
Registering an application in the Ramp developer dashboard is the first step of building an integration based on Ramp API:
- From the Ramp developer settings page, click on Create new app to register a new application.
- Once the application is registered, click into it and configure the following parameters:
- Client ID and client secret: Credentials for the application; store securely.
- App name and description
- Grant types: A list of grant types that the application may use to get access token. See authorization guide for more information.
- Scopes: Defines scopes that may be granted to access token.
- Redirect URIs: Enter
https://oauth2.prismatic.io/callback.
Configure the Connection
Supply the following values to the OAuth 2.0 connection:
- Authorize URL: Select the target environment, Production or Sandbox, for the OAuth 2.0 authorization endpoint
- Token URL: Select the target environment, Production or Sandbox, for the OAuth 2.0 token endpoint. This must match the environment selected for Authorize URL
- Client ID
- Client Secret
- Scopes
- Recommended Scopes (space delimited):
bills:read bills:write accounting:read accounting:write transactions:read reimbursements:read departments:read departments:write entities:read locations:read locations:write
- Recommended Scopes (space delimited):
| Input | Notes | Example |
|---|---|---|
| Authorize URL | The OAuth 2.0 Authorization URL for Ramp | |
| Client ID | ||
| Client Secret | ||
| Scopes | A comma-delimited set of one or more scopes to get the user's permission to access. Refer to https://docs.ramp.com/developer-api/v1/authorization/scopes | accounting:read accounting:write bills:read business:read cards:read cards:write cashbacks:read departments:read departments:write entities:read leads:read leads:write limits:read limits:write locations:read locations:write memos:read merchants:read receipt_integrations:read receipt_integrations:write receipts:read reimbursements:read spend_programs:read spend_programs:write statements:read transactions:read transfers:read users:read users:write |
| Token URL | The OAuth 2.0 Token URL for Ramp |
Triggers
New and Updated Records
Retrieves existing and ongoing records for a selected Ramp resource type. Load history once, check for changes on a schedule, or both. | key: pollChangesTrigger
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Look-back Date | The date the initial sync starts from, in YYYY-MM-DD format. Cannot be a future date. Leave empty to start from the first recurrence with no backfill. On resources without timestamps (Departments, Locations, Business Entities), the first poll always emits all current records regardless of this setting. | 2026-01-01 |
| Resource Type | The type of resource to poll for new and updated records. | |
| Show New Records | Include newly created records in trigger results. | true |
| Show Updated Records | Include updated records in trigger results. | true |
This trigger polls the Ramp API for new and updated records on a scheduled basis.
How It Works
- The trigger runs on the configured schedule
- It fetches every record of the selected resource type from Ramp. Timestamp-based resources are filtered client-side by their creation and update timestamps relative to the last poll time; ID-based resources are compared against the known ID set
- Records are categorized as created or updated based on their timestamps relative to the last poll time, or as created only for ID-based resources where update detection is not supported
- The trigger updates its internal state after each poll
Initial Sync
An initial sync seeds a starting state from history. Inputs that narrow which changes are reported would leave gaps in that state, and this trigger does not suppress them: Show New Records and Show Updated Records still gate the created and updated arrays. For timestamp-based resources the sync begins on the first recurrence, when the trigger has no stored position and a Look-back Date (YYYY-MM-DD) is set, and delivers each record created or updated after that date. Transactions and Bills carry no update timestamp, so only records created after that date are included. ID-based resources (Departments, Locations, Business Entities) ignore Look-back Date: their first recurrence delivers every current record as created, with or without it.
The window has no fixed upper bound and no per-recurrence cap: the trigger lists every record of the resource and filters client-side, so the sync completes in one recurrence whether batching is on or off. The position is then set to the wall-clock time at which that recurrence started, not to the newest record received, and the first incremental recurrence resumes from there. A record updated after that time but before the listing finished is delivered again on the next recurrence. Nothing in the payload marks the handoff.
Resource Type still applies. The trigger has no page-size or field-selection input.
Batching
Batching is enabled per flow on this trigger: each changed record is dispatched as its own execution, or grouped by the configured batch size. Batch size and batch concurrency can both be overridden per instance. Raising concurrency increases the request volume sent to Ramp.
To turn it on, select the flow's trigger, open the Flow control tab, and switch on Enable Batching. Under Batch Size, keep Trigger default or choose Custom batch size. Batch Concurrency is optional; leave it blank for no batch-level limit.
With batching off a downstream step reads body.data.created and body.data.updated. With batching on those fields do not exist: each execution receives one { "changeType": ..., "record": ... } item, or an array of them when the batch size is greater than 1. Any step reading the older shape must be updated before batching is enabled. Because batching is enabled per flow, that change is scoped to the flow rather than to the component or to other flows using the same trigger.
Returned Data
The trigger returns an object with two arrays: created for new records and updated for modified records.
Example Response
{
"data": {
"created": [
{
"id": "txn_01H9ZQ2KBCDEF12345",
"amount": 4250,
"currency_code": "USD",
"merchant_name": "Acme Supplies",
"user_transaction_time": "2024-01-16T10:30:00Z"
}
],
"updated": [
{
"id": "reimb_01H9ZQ2KBCDEF67890",
"amount": 125,
"currency_code": "USD",
"created_at": "2024-01-10T09:00:00Z",
"updated_at": "2024-01-16T14:22:00Z"
}
]
}
}
Fields shown are representative. The full response object includes additional properties.
Notes
- Departments, Locations, and Business Entities use ID-based change detection: the Show Updated Records toggle has no effect for these resource types, as update detection is not supported
- Reimbursements, Vendors, General Ledger Accounts, and Custom Accounting Fields support both new and updated record detection. Transactions and Bills expose only a creation timestamp, so they support new record detection only
- Refer to the Ramp API documentation for rate limit details and available fields per resource type
Data Sources
Select Bill
Select a Bill from a dropdown menu. | key: selectBill | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Bill⤓
Select Business Entity
Select a Business Entity from a dropdown menu. | key: selectBusinessEntity | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Business Entity⤓
Select Custom Accounting Field
Select a custom accounting field from a dropdown menu. | key: selectCustomAccountingField | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Custom Accounting Field⤓
Select Custom Accounting Field Option
Select a custom accounting field option from a dropdown menu for the specified field. | key: selectCustomAccountingFieldOption | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field ID | The ID of the custom accounting field to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Select Custom Accounting Field Option⤓
Select Department
Select a Department from a dropdown menu. | key: selectDepartment | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Department⤓
Select General Ledger Account
Select a General Ledger Account from a dropdown menu. | key: selectLedgerAccount | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select General Ledger Account⤓
Select Location
Select a Location from a dropdown menu. | key: selectLocation | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Location⤓
Select Reimbursement
Select a reimbursement from a dropdown menu. | key: selectReimbursement | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Reimbursement⤓
Select Transaction
Select a transaction from a dropdown menu. | key: selectTransaction | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Transaction⤓
Select Vendor
Select a Vendor from a dropdown menu. | key: selectVendor | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection |
Example Payload for Select Vendor⤓
Actions
Create Custom Accounting Field
Create a custom accounting field | key: createCustomAccountingField
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field ID | The ID of the custom accounting field to create | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Input Type | The input type could be SINGLE_CHOICE, BOOLEAN or FREE_FORM_TEXT | |
| Is Splittable | If set to True, the accounting field can be used to annotate split line items | |
| Name | The name of the custom accounting field to create | Amazon |
Example Payload for Create Custom Accounting Field⤓
Create Department
Create a new department | key: createDepartment
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Name | The name of the department | Amazon |
Example Payload for Create Department⤓
Create Location
Create a new location | key: createLocation
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Entity ID | The ID of the business entity to associate with the location | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Name | The name of the location | Amazon |
Example Payload for Create Location⤓
Delete Custom Accounting Field
Delete a custom accounting field | key: deleteCustomAccountingField
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field ID | The ID of the custom accounting field to delete | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Delete Custom Accounting Field⤓
Delete Custom Accounting Field Option
Delete a custom accounting field option | key: deleteCustomAccountingFieldOption
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field Option ID | The ID of the custom accounting field option to delete | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Delete Custom Accounting Field Option⤓
Delete General Ledger Account
Delete a general ledger account | key: deleteGeneralLedgerAccount
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| General Ledger Account ID | The ID of the general ledger account to delete | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Delete General Ledger Account⤓
Delete Vendor
Delete a vendor | key: deleteVendor
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Vendor ID | The ID of the vendor to delete | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Delete Vendor⤓
Get Bill
Retrieve a bill by ID | key: getBill
| Input | Notes | Example |
|---|---|---|
| Bill ID | The ID of the bill to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Connection |
Example Payload for Get Bill⤓
Get Business Entity
Retrieve a business entity by ID | key: getBusinessEntity
| Input | Notes | Example |
|---|---|---|
| Business Entity ID | The ID of the business entity to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Connection |
Example Payload for Get Business Entity⤓
Get Custom Accounting Field
Retrieve a custom accounting field by ID | key: getCustomAccountingField
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field ID | The ID of the custom accounting field to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Custom Accounting Field⤓
Get Custom Accounting Field Option
Retrieve a custom accounting field option by ID | key: getCustomAccountingFieldOption
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field Option ID | The ID of the custom field option to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Custom Accounting Field Option⤓
Get Department
Retrieve a department by ID | key: getDepartment
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Department ID | The ID of the department to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Department⤓
Get General Ledger Account
Retrieve a general ledger account by ID | key: getGeneralLedgerAccount
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| General Ledger Account ID | The ID of the general ledger account to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get General Ledger Account⤓
Get Location
Retrieve a location by ID | key: getLocation
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Location ID | The ID of the location to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Location⤓
Get Reimbursement
Retrieve a reimbursement by ID | key: getReimbursement
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Reimbursement ID | The ID of the reimbursement to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Reimbursement⤓
Get Transaction
Retrieve a transaction by ID | key: getTransaction
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Transaction ID | The ID of the transaction to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Transaction⤓
Get Vendor
Retrieve a vendor by ID | key: getVendor
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Vendor ID | The ID of the vendor to retrieve | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Get Vendor⤓
List Bills
Retrieve a list of all bills | key: listBills
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Bills⤓
List Business Entities
Retrieve a list of all business entities | key: listBusinessEntities
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Business Entities⤓
List Custom Accounting Field Options
List options for a given custom accounting field | key: listCustomAccountingFieldOptions
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field ID | The ID of the custom accounting field to list options for | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Custom Accounting Field Options⤓
List Custom Accounting Fields
List custom accounting fields | key: listCustomAccountingField
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Custom Accounting Fields⤓
List Departments
Retrieve a list of all Departments | key: listDepartments
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Departments⤓
List General Ledger Accounts
Retrieve a list of all general ledger accounts | key: listGeneralLedgerAccounts
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List General Ledger Accounts⤓
List Locations
Retrieve a list of all locations | key: listLocations
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Locations⤓
List Reimbursements
Retrieve a list of all reimbursements | key: listReimbursements
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Reimbursements⤓
List Transactions
Retrieve a list of all transactions | key: listTransactions
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Transactions⤓
List Vendors
Retrieve a list of all vendors | key: listVendors
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Query Params | Custom query parameters to be included in the request | { "from_date": "2024-01-01" } |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page size and starting point for paginated results. |
Example Payload for List Vendors⤓
Post Sync Status
Notify Ramp of a list of accounting sync results | key: postSyncStatus
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Failed Syncs | A list of objects that failed to be synced | |
| Idempotency Key | An idempotency key is a unique value generated by the client which the server uses to recognize subsequent retries of the same request. To avoid collisions, we encourage clients to use random generated UUIDs | d471d830-2e73-4082-8a75-68540f83e86e |
| Successful Syncs | A list of objects that were successfully synced | |
| Sync Type | The type of object to sync | TRANSACTION_SYNC |
Raw Request
Send raw HTTP request to Ramp API | key: rawRequest
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Data | The HTTP body payload to send to the URL. | {"exampleKey": "Example Data"} |
| File Data | File Data to be sent as a multipart form upload. | [{key: "example.txt", value: "My File Contents"}] |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Form Data | The Form Data to be sent as a multipart form upload. | [{"key": "Example Key", "value": new Buffer("Hello World")}] |
| Header | A list of headers to send with the request. | User-Agent: curl/7.64.1 |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Method | The HTTP method to use. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Timeout | The maximum time that a client will await a response to its request | 2000 |
| URL | Input the path only (/departments), The base URL is already included (https://api.ramp.com/developer/v1/). For example, to connect to https://api.ramp.com/developer/v1/departments, only /departments is entered in this field. e.g. /departments | /departments |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
Update Custom Accounting Field
Update an existing custom accounting field | key: updateCustomAccountingField
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field ID | The ID of the custom accounting field to update | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Is Splittable | If set to True, the accounting field can be used to annotate split line items | |
| Name | The name of the custom accounting field | Amazon |
Example Payload for Update Custom Accounting Field⤓
Update Custom Accounting Field Option
Update an existing custom accounting field option | key: updateCustomAccountingFieldOption
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field Option ID | The ID of the custom accounting field option to update | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Reactivate | Reactivate a deleted custom field option | |
| Value | The value of the custom accounting field option | Sales & Marketing |
Example Payload for Update Custom Accounting Field Option⤓
Update Department
Update a department by ID | key: updateDepartment
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Department ID | The ID of the department to update | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Name | The updated name of the department | Amazon |
Example Payload for Update Department⤓
Update General Ledger Account
Update an existing general ledger account | key: updateGeneralLedgerAccount
| Input | Notes | Example |
|---|---|---|
| Code | The code of the general ledger account; provide an empty string to reset the remote code. | 19566 |
| Connection | ||
| General Ledger Account ID | The ID of the general ledger account to update | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Name | Name of the general ledger account | Amazon |
| Reactivate | Reactivate a deleted general ledger account | |
| Subsidiaries | IDs of a list of subsidiaries which a general ledger account can be used with. The Ramp-assigned IDs should be used here. Provide an empty list to reset the subsidiaries list for this general ledger account. |
Example Payload for Update General Ledger Account⤓
Update Location
Update an existing location | key: updateLocation
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Entity ID | The ID of the entity to update the location | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Location ID | The ID of the location to update | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Name | The updated name of the location | Amazon |
Example Payload for Update Location⤓
Update Vendor
Update an existing vendor | key: updateVendor
| Input | Notes | Example |
|---|---|---|
| Code | Code of the vendor; provide an empty string to reset the remote code. | 19566 |
| Connection | ||
| Name | Name of a vendor | Amazon |
| Reactivate | Reactivate a deleted vendor | |
| Subsidiaries | IDs of a list of subsidiaries associated with the vendor. The Ramp-assigned IDs should be used here. Provide an empty list to reset the subsidiaries list. | |
| Vendor ID | The ID of the vendor to update | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
Example Payload for Update Vendor⤓
Upload Custom Accounting Field Option
Upload a new custom accounting field option | key: uploadCustomAccountingFieldOption
| Input | Notes | Example |
|---|---|---|
| Connection | ||
| Custom Accounting Field Option ID | The ID of the custom accounting field option for which to upload options | 96bb7007-eec5-430f-8d09-e033cbc000c2 |
| Options | A list of field options for a given custom accounting field |
Example Payload for Upload Custom Accounting Field Option⤓
Changelog
2026-10-13
- Added opt-in batching to the New and Updated Records trigger, dispatching each changed record individually or in configured batches; enabling it changes the shape a downstream step receives
- Added an optional Look-back Date input for performing an initial sync of records. The initial sync begins on the first recurrence and backfills every record created or updated after the specified date, seeding each once; departments, locations, and business entities ignore the date and always sync in full. Later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
2026-08-13
Restructured list action pagination inputs, added output schemas, and enabled inline action calling:
- Grouped the Start and Page Size inputs into a Pagination structured object across all list actions (List Vendors, List Transactions, List Bills, List Reimbursements, List Departments, List Locations, List Business Entities, List General Ledger Accounts, List Custom Accounting Fields, and List Custom Accounting Field Options); Fetch All stays a top-level toggle
- Added output schemas to 38 actions for improved field mapping during configuration
- Added inline action calling support across all actions so the app builder can show example output during configuration
- Documented the Authorize URL and Token URL environment selection on the OAuth 2.0 connection
- List actions run without Fetch All now use the Ramp server-side default page size instead of 50
2026-05-20
Applied automated security patches and code formatting updates
2026-04-30
Updated spectral version
2026-04-21
Added New and Updated Records polling trigger that checks for new and updated transactions, bills, reimbursements, vendors, and other financial records in Ramp on a configured schedule
2026-03-13
Removed the Debug Request input from all action inputs. Debug logging is now controlled internally and no longer appears as a configurable field in actions.
2026-03-05
Added inline data sources for transactions, reimbursements, custom accounting fields, and custom accounting field options to enhance data selection capabilities