mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #116] Feature Request: Queue Actions from CloudRadial/webhook #72
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @scubes13 on GitHub (Oct 25, 2021).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/116
When using a portal such as CloudRadial, allow a webhook associated with a Service Request/Service Ticket connected to a queue-able action. Display a list of these queued actions for an MSP technician to execute/approve.
Queued Actions could be predesigned. For example, you could go through a wizard to select the type of queued action you want to generate (new user, remove user, etc.). Once you created the queued action, you would be given a webhook URL specific to the queued action to plug into your portal/tool.
Example:
A client goes to CloudRadial and submits a request for onboarding a new employee.
Upon submission, a ticket is generated in the MSP's PSA and a preconfigured action is queued within CIPP.
The technician that is assigned the ticket visits the CIPP site.
From a list of queued actions, they select the one for their ticket.
They review the action to verify the details for accuracy. They make any adjustments and submit the action to be processed.
Thought - You could also create a "Pod" for a PSA so that the technician could directly interact with the Queued Action that would be listed on the Ticket detail screen.
@KelvinTegelaar commented on GitHub (Oct 25, 2021):
Out of scope. We will not integrate with any vendor directly until at least version 2.0. This is to prevent favoritism and doing the work for vendors that have lagged behind for free.
Do feel free to make a new FR when 2.0 gets released.