Discussions
Addon Activation URL
Where can get Addon Activation URL
Pipedrive and ServiceM8 API Intergration
Hi. We are currently doing integration between Pipedrive and ServiceM8. We are trying to make it happen when updates are made in ServiceM8, it will also update back it Pipedrive. Like closed job and update as Won in Pipedrive.
ServiceM8Trigger when a new quote is generated, sending job data to Google Sheets
We have developed a custom integration between ServiceM8 and Google Sheets. A webhook is set to trigger when a new quote is generated, sending job data to Google Sheets. However, the webhook is causing issues, and the integration stopped due to an "Invalid Token" error.
Webhook Issue
Hello ServiceM8 Team,
API integration with 3CX phone system
Is ServiceM8 compatible with 3CX
platform_feed_post returns 500 error
Hey ya'll,
API for downloading Videos
Is there any integration or API that able to be linked with SM8 that will search for and download pictures and videos from jobs without having to go into each individual job?
API Request limit 180 per minute
Hi, we have many users using our CRM system to push jobs through to ServiceM8. The issue is, because of the sync constraint of 180 per minute our queue is not going down, in fact it's getting bigger at 50,000 pending update in the queue. We need help to solve this problem as our installers are not seeing jobs for days. Any suggestions?
How can I identify where the add-on is added.
When an Add-on is added to any account, we authorize it by generating the access token and refresh token.
{
"access_token": "your_access_token_here",
"expires_in": 3600,
"token_type": "bearer",
"scope": "read_customers read_jobs",
"refresh_token": "your_refresh_token_here"
}
We receive this output, but we cannot identify where our Add-on is added as we do not receive any location ID or anything similar.
How can I identify where the add-on is added.
When an Add-on is added to any account, we authorize it by generating the access token and refresh token.
{
"access_token": "your_access_token_here",
"expires_in": 3600,
"token_type": "bearer",
"scope": "read_customers read_jobs",
"refresh_token": "your_refresh_token_here"
}
We receive this output, but we cannot identify where our Add-on is added as we do not receive any location ID or anything similar.