Discussions

Whenever a webhook subscription is created for ServiceM8 the previous one is deleted - meaning I can only ever have 1 webhook running at a time.

This happens

When creating a scenario in

• Make.com(formerly Integromat) using the pre-built trigger modules (which create a webhook automatically).
• When creating a webhook via the ServiceM8 API in Postman.com
• When creating custom webhooks in Zapier.

If you run an API GET request in the Make.com ServiceM8 module to the ‘webhook_subscriptions’ endpoint then it only ever returns 1 result. (Which is always the last webhook you created in Make.com)

If you then create another webhook in another application (such as Postman) then run a GET request to the ‘webhook_subscriptions’ endpoint, it will only ever return 1 result (the last webhook created in Postman)

Neither application is able to see webhooks created in the other application (even though the GET request should return a list of ALL ‘webhook_subscrptions’

Both of these webhooks will actually now work if you point a separate scenario to each of them in Make.com But if you create a new webhook in either application, then the old webhook that you had created in that application will stop working.

The only application that you can create and use multiple webhooks seems to be Zapier. But even then, it only works if you create the webhooks via the pre-built trigger modules. If you create any custom webhooks, the same thing happens.

I have tried contacting ServiceM8 support, and their response was;

“I understand you came across an issue with our API. I'm afraid we cant provide solutions for the issue here. All information regarding our API is available online through our developer portal you should be able to find any information you need there - https://developer.servicem8.com

You might also be able to find the solutions to your issue on our developer forum (https://developer.servicem8.com/discuss ), or on StackOverflow (https://stackoverflow.com/questions/tagged/servicem8 )

If the solution is not there we recommend that you post the problem in the discussion board on either stack overflow or on our forum the developer community is usually very active and will respond it.”