ServiceM8 icon

ServiceM8

ServiceM8 Node
Join our community

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 HTML or plain text bodies, specify recipients (To, Cc), set reply-to addresses, include attachments, and link the email to a specific job in ServiceM8. The node supports impersonating a staff member to include their email signature dynamically.

Common scenarios where this node is beneficial include:

  • Sending job-related updates or notifications directly from an automation workflow.
  • Communicating with clients or team members with customized email content.
  • Automatically attaching files stored in ServiceM8 to outgoing emails.
  • Including staff signatures automatically by impersonation for personalized communication.

Example: An automation that triggers when a job status changes, sending an email update to the client with job details and attaching relevant documents.

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 at a specific location. Requires impersonation 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 <platform-user-signature /> tag (converted to plain text). Requires impersonation UUID header if used.
Regarding Job UUID UUID of the job that this message is regarding. Links the email to the job diary in ServiceM8. 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 containing the response body from the ServiceM8 API after sending the email. This typically includes confirmation details about the sent email such as message ID or status.

No binary data output is produced by this operation.

Dependencies

  • Requires an active ServiceM8 account with API access.
  • Needs an API key credential configured in n8n for authentication with ServiceM8.
  • When using the <platform-user-signature /> tag in the email body, the x-impersonate-uuid property must be set to specify which staff member's signature to use.

Troubleshooting

  • Missing required fields: At least one of "HTML Body" or "Plain Text Body" must be provided; otherwise, the API call will fail.
  • Invalid or missing job UUID: If linking the email to a job, ensure the "Regarding Job UUID" is valid; otherwise, the email won't appear in the job diary.
  • Incorrect attachment UUIDs: Attachment UUIDs must reference existing attachments; invalid UUIDs will cause errors.
  • Impersonation errors: Using the signature tag without setting the impersonation UUID will result in failure.
  • API request failures: Network issues or invalid credentials will cause the node to throw errors. Verify API key validity and network connectivity.

Links and References

Discussion