ServiceM8 Smart Job Creation icon

ServiceM8 Smart Job Creation

Create or update ServiceM8 jobs with intelligent client/contact deduplication

Actions2

Create Job

AI-generated

Summary

Create a new job in ServiceM8 with associated client and contact information, including optional configurations like category, badges, queue assignment, attachments, notifications, and custom notes.

Inputs

  • firstName — Contact's first name, required unless a business name is provided.
  • lastName — Contact's last name.
  • email — Contact email address, used as a primary lookup identifier for deduplication.
  • phone — Landline phone number for the contact.
  • mobile — Mobile phone number for the contact.
  • businessName — Business name; if provided, the client is created as a business, otherwise as an individual.
  • clientAddress — Client's physical address (street, city, state, postcode, country).
  • jobAddressSameAsClient — Boolean to use the client address as the job site address.
  • jobAddress — Job site address if different from client address.
  • jobDetails — Description or notes about the job.
  • jobStatus — Initial status of the job (Quote, Work Order, Completed, Unsuccessful).
  • enableCategory — Whether to assign a category to the job.
  • categoryDynamic — Use an expression for dynamic category name instead of fixed dropdown.
  • category — Category to assign to the job (selected from dropdown).
  • categoryName — Category name string to look up dynamically (case-insensitive).
  • enableBadges — Whether to assign badges to the job.
  • badgesDynamic — Use dynamic badge names from an expression.
  • badges — Badges to assign to the job from dropdown.
  • badgeNames — Comma-separated badge names to assign dynamically.
  • enableQueue — Whether to assign the job to a queue.
  • queueDynamic — Use a dynamic queue name from an expression.
  • queue — Queue to assign the job from dropdown.
  • queueName — Queue name string to lookup dynamically (case-insensitive).
  • enableNotifications — Whether to send SMS/email notifications about the new job.
  • notificationRecipients — List of recipients for notifications, specifying type (email or SMS), contact info, message format, subject, and message content with placeholders.
  • enableAttachments — Whether to upload and attach files to the job.
  • attachmentMode — Method to specify attachments: all binary data from previous node, URL list, or manual input.
  • attachmentUrlList — Comma-separated URLs to download and attach.
  • attachments — Manually specified attachments with source type (binary or URL), filename, and file type.
  • enableCustomNote — Whether to add a custom note to the job.
  • customNoteContent — Content of the custom note.
  • additionalOptions — Extra options including client name format ('First Last' or 'Last, First' for individual clients) and whether to return full UUIDs of created records in output.

Output shape

A single record containing details of the created job and optionally the UUIDs of created records (client, contact, job contact, notes, attachments) if requested.

Includes an internal system report note with creation details and logs any encountered issues. Notifications, attachment uploads, category, badges, and queue assignments occur as configured. Deduplication uses client name and contact email where possible. Supports placeholders in notification messages for dynamic content.

Examples

Example 1: Creating a job for a new individual client with notification emails and attachments.

Set firstName, lastName, and email for the contact; provide clientAddress; enableAttachments with mode 'allBinary'; enableNotifications with recipient email configured; provide jobDetails and jobStatus.

Example 2: Creating a job for an existing business client with assigned category, badges, and queue.

Provide businessName to create or match an existing business client; enableCategory with fixed category selection; enableBadges with selected badges or dynamic badgeNames; enableQueue with selected queue or dynamic queueName; include jobDetails.

Links

Discussion