PipedreamHQ / PipedreamHQ/pipedream
[Components] current_rms
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 101
Description
# current_rms
## URLs
- https://api.current-rms.com/doc
## Webhook Sources
### new-opportunity-instant
#### Description
Emit new event when a new opportunity is created in Current RMS. Users can filter by opportunity status (optional).
### new-contact-instant
#### Description
Emit new event when a new contact is added to Current RMS. Users can optionally filter by contact type (e.g., customer, supplier).
### new-order-instant
#### Description
Emit new event when a new order is created in Current RMS. Users can filter by order status (optional).
## Actions
### create-opportunity
#### Description
Create a new opportunity in Current RMS. Requires an opportunity name, account ID, and optional details such as value and status.
### create-contact
#### Description
Create a new contact in Current RMS. Requires a name, email, and contact type. Optional fields include phone number and address.
### update-order-status
#### Description
Update the status of an existing order in Current RMS. Requires an order ID and new status value.
Contributor guide
Research direction
Start with the Current RMS API documentation at https://api.current-rms.com/doc and review the requested webhook sources and actions in the issue. Implement the three event sources and three actions with their required fields and optional filters or details. Done means the listed Current RMS events and operations are available and behave according to the descriptions.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100