Search the Community

Showing results for tags 'connectwise'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • From LogicMonitor
    • Product Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 4 results

  1. I have come across this issue a few times now, and feel it's worth bringing up. A major roadblock to making our integrations (with major platforms like ConnectWise) work the way we want them to is the limitation of only being able to make a single API request per event/status change/etc. One example - we want to be able to insert the "Acknowledged" notes when an alert (or several) are ack'ed in LogicMonitor as a service note to the corresponding tickets in ConnectWise AND update the status of the ConnectWise ticket to 'In progress'. That requires 2 API calls: one (which is the default for your builtin ConnectWise integration) to update the ticket priority/status/etc (HTTP PATCH -> https://{connectwiseSite}/v4_6_release/apis/3.0/service/tickets/{id}) and another to add a note to the ticket (HTTP POST -> https://{connectwiseSite}/v4_6_release/apis/3.0/service/tickets/{id}/notes). Another example - our RMM tool does not support the usual API Key method of authentication. It requires that one go through a slightly obtuse algorithm to send credentials, save a generated session token that is returned as part of the response body, and then submit that session token in the headers of future requests as a bearer token. I don't want to just leave these sessions open all the time, even though all traffic is submitted through HTTPS, the session token grants access as the API user from anywhere. So without going bonkers in complexity and asking for the world - it would be good enough to just be able to execute multiple API requests : 1 - Authenticate and save part of the response body, 2 - Submit one or more requests using the session token, 3 - Logout. We /really/ need the ability to get information from LM into ConnectWise and other platforms to make this solution shine.
  2. PropertySource to retrieve the ID of a matching Configuration (CI) in ConnectWise. LM Locator: YR77GF
  3. I would like to request the ability to utilize a token to pass the Acknowledgement Comment for an alert to a ConnectWise ticket. Ideally we would like it so that when a ConnectWise ticket's status is updated because the alert has been acknowledged in LogicMonitor, the comment set for the acknowledgement is passed and included in the ticket. Currently we are able to use the ##ALERTSTATUS## token to display the current status of the alert, but the ability to utilize the acknowledgement comment would greatly improve ticket handling. Thank you, Chris Czuhanich
  4. Hello, Would it be possible to add another field under ConnectWise Priorities for something like "Informational"? You have Critical, Error and warning. It would be nice if there was a fourth called something like Informational. Even if it was down the road.