ServiceM8 triggers and actions are useful. n8n also has a nice layout. AI integration with Claude is a game changer; Claude can now craft the workflow directly. Setting up a workflow in n8n is now 10x easier than setting up the equivalent workflow in most other orchestration platforms. Exporting the n8n workflows as json for import into other systems also makes n8n workflows easier to port between instances.
The triggers are ‘expensive’ - unlike Zapier where you can trigger formResponse event based on the form and not incur a task if the form event was not for the desired form; in the n8n ServiceM8 trigger all form events need to be queried then filtered; which consumes an entire execution count. To reduce n8n executions I’m looking at using Zapier again to handle and filter the inbound event, then forwarding onto n8n to process the events that actually need to be processed.
Also, had to develop a webhook manager add-on to deal with n8n’s test webhook/production webhook shenanigans. For example, using the formResponse trigger in certain ServiceM8 systems will not reliably fire - not sure why ¯\_(ツ)_/¯
This n8n workflow triggers after a field staff checks out of a job.
It first checks a “Job Completion Form” to see if the the tech said “Yes” to the question “Send review SMS to customer”, and then waits 15 minutes before sending an SMS to the job contact asking for a Google Review.
The workflow also sends the event to a local n8n datastore, which is used to populate a custom dashboard add-on in the customer’s ServiceM8 system giving them a sense of how many customer review request SMS’s are being sent each day by the team.
