Actions11
- Client Actions
- Job Actions
- Email Actions
- SMS Actions
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 rich HTML or plain text content, specify recipients (To, Cc), set reply-to addresses, attach files, and link the email to a specific job in ServiceM8 for tracking purposes. The node supports impersonating a staff member to include their email signature dynamically.
Common scenarios where this node is beneficial include:
- Automatically sending job-related updates or notifications to clients.
- Dispatching quotes, invoices, or follow-up emails linked directly to a job record.
- Sending personalized emails on behalf of different staff members using their signatures.
- Attaching relevant documents or images stored in ServiceM8 to outgoing emails.
Example: After a job is completed, automatically send a thank-you email with the job details and an attached invoice PDF, linking the email to the job diary for future reference.
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 in ServiceM8 so it appears in the job diary. 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. |
Output
The node outputs a JSON array containing the response from the ServiceM8 API after sending the email. This typically includes details about the sent email such as its ID, status, and metadata returned by the platform.
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_emailto send emails. - If using the
<platform-user-signature />tag in the email body, thex-impersonate-uuidheader must be provided 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 will reject the request.
- Invalid or missing job UUID: If you want the email linked to a job diary, ensure the "Regarding Job UUID" is correct; otherwise, the email won't appear in the job's diary.
- Signature tag usage without impersonation UUID: Using
<platform-user-signature />without providing the impersonation UUID header will cause the API to fail. - Attachment UUIDs invalid or missing: Ensure all attachment UUIDs exist in the system; otherwise, attachments won’t be included.
- API errors: Network issues or invalid credentials will cause the node to throw errors. Verify API keys and network connectivity.
- Handling errors: The node supports continuing on failure per item; enable this option to process multiple inputs even if some fail.