ServiceM8 icon

ServiceM8

ServiceM8 Node
Join our community

Actions11

Overview

The node integrates with the ServiceM8 platform to send emails related to jobs or general communication. It allows users to compose and send emails with rich content, including HTML or plain text bodies, attachments, and specific email headers such as "To", "Cc", and "Reply To". Additionally, it supports linking the email to a particular job in ServiceM8 by specifying a job UUID, which helps organize correspondence within the job diary.

Common scenarios for this node include:

  • Sending job-related updates or notifications to clients or staff.
  • Dispatching quotes, invoices, or follow-up emails linked directly to a job.
  • Automating email communications with personalized signatures by impersonating staff members.

Practical example:

  • Automatically sending a job completion notification email with an attached invoice PDF to a client, including the staff member's signature.

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 the <platform-user-signature /> tag to insert a staff member's email signature at a specific location. Requires the x-impersonate-uuid header if used.
Plain Text Body Plain text email body. At least one of HTML Body or Plain Text Body must be provided. Supports the <platform-user-signature /> tag (converted to plain text). Requires the x-impersonate-uuid header if used.
Regarding Job UUID UUID of the job that this message is regarding. Linking the email to this job causes it to appear in the job diary. If omitted, the email will not be 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.

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 details about the sent email, such as status and identifiers returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the ServiceM8 API via an API key credential configured in n8n.
  • The node uses the ServiceM8 REST API endpoint https://api.servicem8.com/platform_service_email to send emails.
  • If using the <platform-user-signature /> tag in the email body, the x-impersonate-uuid header must be set to specify the staff member whose signature should be inserted.

Troubleshooting

  • Missing required fields: At least one of htmlBody or textBody must be provided; otherwise, the API may reject the request.
  • Invalid email addresses: Ensure that all email addresses (to, cc, replyTo) are validly formatted to avoid errors.
  • Attachments not found: Attachment UUIDs must correspond to existing attachments in ServiceM8; invalid UUIDs will cause failures.
  • Signature tag usage without impersonation UUID: Using <platform-user-signature /> without setting x-impersonate-uuid will result in errors because the system cannot determine which staff signature to use.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Job UUID linkage issues: If the regardingJobUUID is incorrect or does not exist, the email will not link to any job, potentially causing confusion in job diaries.

Links and References

Discussion