starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #277] Feature Request: Custom URL actions on clients #2124

New issue

Closed

opened 2026-03-14 02:39:17 +03:00 by kerem · 6 comments

kerem commented

2026-03-14 02:39:17 +03:00

Owner

Originally created by @nr-plaxon on GitHub (Feb 16, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/277

Originally assigned to: @sadnub on GitHub.

Custom URLs that accept values from custom fields could allow integration of other tools such as TeamViewer.

Example: A custom field named TeamViewerID could be created and assigned to a client by using the local command

tacticalrmm.exe --fieldname TeamViewerID --fieldvalue "123456789"

This field (and all other custom fields) should be visible (ie. as a table, exportable as CSV) in a separate tab on the client in TRMM.

Next, we should be able to create custom URLs for web actions. These could be listed in a separate submenu on a right click on the client name, just like the "Run Favorited Scripts" menu:

A custom URL could be defined by using the custom variable created earlier:

https://start.teamviewer.com/{{TeamViewerID}}

which would result in

https://start.teamviewer.com/123456789

Having this as a clickable link in the a "Open Custom URL" submenu would allow integration of many tools that allow for URL schemas to run certain actions.

As a further enhancement, this could be modified to allow for calling REST APIs with GET and POST request and displaying / processing the results.

Custom field feature request: https://github.com/wh1te909/tacticalrmm/issues/155

Originally created by @nr-plaxon on GitHub (Feb 16, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/277 Originally assigned to: @sadnub on GitHub. Custom URLs that accept values from custom fields could allow integration of other tools such as TeamViewer. Example: A custom field named **TeamViewerID** could be created and assigned to a client by using the local command `tacticalrmm.exe --fieldname TeamViewerID --fieldvalue "123456789"` This field (and all other custom fields) should be visible (ie. as a table, exportable as CSV) in a separate tab on the client in TRMM. Next, we should be able to create custom URLs for web actions. These could be listed in a separate submenu on a right click on the client name, just like the "Run Favorited Scripts" menu: <img width="288" alt="Bildschirmfoto 2021-02-16 um 10 06 15" src="https://user-images.githubusercontent.com/75976239/108042174-c24cdd80-703f-11eb-8855-57166d66f705.png"> A custom URL could be defined by using the custom variable created earlier: `https://start.teamviewer.com/{{TeamViewerID}}` which would result in `https://start.teamviewer.com/123456789` Having this as a clickable link in the a "Open Custom URL" submenu would allow integration of many tools that allow for URL schemas to run certain actions. As a further enhancement, this could be modified to allow for calling REST APIs with GET and POST request and displaying / processing the results. Custom field feature request: https://github.com/wh1te909/tacticalrmm/issues/155

kerem closed this issue

2026-03-14 02:39:22 +03:00

kerem commented

2026-03-14 02:39:28 +03:00

Author

Owner

@Omnicef commented on GitHub (Feb 16, 2021):

I agree as long as it can be generic. TeamViewerID is a good example. But I need it ffor other things such as osTicket and Connectwise Control.

@Omnicef commented on GitHub (Feb 16, 2021): I agree as long as it can be generic. TeamViewerID is a good example. But I need it ffor other things such as osTicket and Connectwise Control.

kerem commented

2026-03-14 02:39:33 +03:00

Author

Owner

@Omnicef commented on GitHub (Feb 16, 2021):

As far as placement... I'd be okay with it down in the Summary section as a clickable link.

@Omnicef commented on GitHub (Feb 16, 2021): As far as placement... I'd be okay with it down in the Summary section as a clickable link.

kerem commented

2026-03-14 02:39:38 +03:00

Author

Owner

@nr-plaxon commented on GitHub (Feb 16, 2021):

I agree as long as it can be generic. TeamViewerID is a good example. But I need it ffor other things such as osTicket and Connectwise Control.

This is meant to be configurable, so it could call any web link, be it osTicket, Connectwise Control, etc.

@nr-plaxon commented on GitHub (Feb 16, 2021): > I agree as long as it can be generic. TeamViewerID is a good example. But I need it ffor other things such as osTicket and Connectwise Control. This is meant to be configurable, so it could call any web link, be it osTicket, Connectwise Control, etc.

kerem commented

2026-03-14 02:39:43 +03:00

Author

Owner

@Omnicef commented on GitHub (Feb 16, 2021):

Got it. This would be great.

@Omnicef commented on GitHub (Feb 16, 2021): Got it. This would be great.

kerem commented

2026-03-14 02:39:48 +03:00

Author

Owner

@sadnub commented on GitHub (May 7, 2021):

This will be possible in the next release with url actions.

@sadnub commented on GitHub (May 7, 2021): This will be possible in the next release with url actions.

kerem commented

2026-03-14 02:39:53 +03:00

Author

Owner

@wh1te909 commented on GitHub (May 12, 2021):

released in 0.6.9 https://wh1te909.github.io/tacticalrmm/functions/url_actions/

@wh1te909 commented on GitHub (May 12, 2021): released in 0.6.9 https://wh1te909.github.io/tacticalrmm/functions/url_actions/

kerem referenced this issue

2026-03-14 07:00:21 +03:00

[GH-ISSUE #2124] Expose configurable admin timeout in settings #3266