Discussions

Hello,

Why does the 100% prepayment option always end up with a 0.01 rounding error?

I have been using Make.con with the serviceM8 integrations for some time.
the automation I have set up is triggered by webhook when a job status changes.
it has suddenly stopped working.
I have tried re-authorizing, I have tried a new automation that watches for job status changes.

Apologies if I've missed this in the docs. I did have a good look.

We are experiencing an issue with our application that connects ServiceM8 to HubSpot. After running successfully for some time, the app started failing during the Access Token generation, resulting in a CloudFront 504 Gateway Timeout error. The error message states:

Recently, I integrated an add-on in ServiceM8 that uses webhooks to trigger a function in my backend whenever a job is created, updated, or modified. However, there’s a significant delay in triggering the webhook. Sometimes, it takes 30 seconds to minutes, and in some cases, even up to 20 minutes. What could be causing this issue, and how can we resolve it?

Hey team,

When a new add-on user initiates the OAuth flow by pressing 'Connect' where is the recommended place for me to redirect them back to within servicem8?

I've been reading up on creating "Web Service Hosted Add-ons" and "External Integrations" with a view to integrating an app which I've written. I think I understand the authentication flow. Just one question. When someone activates the add-on by pressing "Connect", the OAuth process is kicked off and my app gets granted an access and refresh token. I assume this process of connection is only envisaged to be performed once (apologies if this is a basic question, but I am quite new to servicem8 and haven't actually activated any add-ons myself). I'm just trying to work out what happens in the edge case that no one uses the add-on for over a month and the refresh token expires? The OAuth process has to be initiated again I assume. Do they press 'Connect' again, or would I provide a menu item button which allowed them to 'Re-connect' the app with their servicem8 account. Obviously, the add-on wouldn't be very useful if it wasn't used for so long! but nevertheless, the question is bugging me!

Currently, I created a developer account in my ServiceM8 account. In that, I created an item and received the Client ID and Secret ID. Using these credentials, I requested an authorization code and successfully received the code in the URL parameter of the redirect URL.