ServiceM8

ServiceM8 Node

Actions14

Overview

This node integrates with the ServiceM8 platform to send emails related to jobs or general communication. It allows users to compose and send emails with options for recipients, subject, body content in HTML or plain text, attachments, and linking the email to a specific job within ServiceM8. This is useful for automating client communications, sending job updates, or dispatching notifications directly from workflows.

Practical examples include:

Sending a job update email to a client with job details linked automatically.
Dispatching marketing or informational emails with custom HTML content and staff signatures.
Sending emails with attachments such as quotes, invoices, or photos related to a job.

Properties

Name	Meaning
To	Recipient email address.
Cc	Carbon copy recipient email address.
Reply To	Reply-to email address.
Subject	Email subject line.
HTML Body	HTML-formatted email body. At least one of HTML Body or Plain Text Body must be provided. Supports `<platform-user-signature />` tag to insert a staff member's email signature (requires impersonation header).
Plain Text Body	Plain text email body. At least one of HTML Body or Plain Text Body must be provided. Supports `<platform-user-signature />` tag (converted to plain text) and requires impersonation header if used.
Regarding Job UUID	UUID of the job that this message is regarding. Linking the email to a job causes it to appear in the job diary in ServiceM8. If omitted, the email is not linked to any job.
Attachments	Array of attachment UUIDs to include with the email. Each UUID must reference an existing attachment in the system.
x-impersonate-uuid	UUID of the staff member to impersonate when using the `<platform-user-signature />` tag. This header is required if the signature tag is included in the email body to correctly render the staff signature.

Output

The node outputs a JSON array where each item corresponds to the response from the ServiceM8 API after sending an email. The structure typically includes confirmation details about the sent email, such as status or identifiers returned by the API.

No binary data output is produced by this operation.

Dependencies

Requires an API key credential for authenticating with the ServiceM8 API.
The node makes HTTP POST requests to the ServiceM8 email service endpoint (https://api.servicem8.com/platform_service_email).
If using the <platform-user-signature /> tag in the email body, the x-impersonate-uuid header must be set to specify which staff member’s signature to use.

Troubleshooting

Missing Email Body: At least one of the HTML Body or Plain Text Body fields must be provided. Omitting both will cause the request to fail.
Signature Tag Usage: If the <platform-user-signature /> tag is included in the email body but the impersonation UUID header is not set, the API call will likely fail or the signature will not render correctly.
Invalid Attachment UUIDs: Providing attachment UUIDs that do not exist or are invalid will cause errors when sending the email.
Job UUID Linking: If the Regarding Job UUID is incorrect or does not correspond to an existing job, the email will not link properly in the job diary.
API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to send emails via ServiceM8.