Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
Overview
The node integrates with the ServiceM8 platform, specifically enabling operations on various resources such as Clients, Jobs, Emails, SMS, and Searches. The Send Job To Queue operation under the Job resource allows users to send a specific job to a designated job queue within ServiceM8. This is useful for automating workflow management by programmatically assigning jobs to queues, which can help in organizing tasks, prioritizing work, or triggering further processing based on queue membership.
Practical examples:
- Automatically sending newly created or updated jobs to a specific queue for dispatching.
- Moving jobs to a priority queue when certain conditions are met.
- Setting an expiry date on queued jobs to manage time-sensitive tasks.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the job to be sent to the queue. |
| Fields | A collection of additional parameters: |
| - Job Queue ID Or Name | The target job queue's ID or name where the job will be sent. |
| - Queue Expiry Date | Optional expiry date for the job in the queue, indicating when the job should expire. |
Output
The node outputs a JSON array containing the response from the ServiceM8 API after sending the job to the queue. This typically includes details about the job's new queue status or confirmation of the action performed.
If the operation succeeds, the output JSON reflects the updated job information related to its queue assignment.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the ServiceM8 API via an API key credential configured in n8n.
- The node depends on the ServiceM8 REST API endpoints for job and queue management.
- Proper permissions on the API key to modify jobs and access job queues are necessary.
Troubleshooting
Common issues:
- Missing or invalid UUID: The job identifier must be correctly provided; otherwise, the API call will fail.
- Invalid or non-existent queue ID/name: The specified queue must exist in ServiceM8; otherwise, the job cannot be assigned.
- Insufficient permissions: The API key used must have rights to update jobs and assign them to queues.
- Incorrect date format for queue expiry: The expiry date should follow the expected format (usually ISO 8601) to avoid errors.
Error messages:
- "No fields to update were added": This error occurs if no valid fields are provided for the update; ensure that at least the queue ID or expiry date is set.
- API authentication errors: Check that the API key credential is valid and has not expired.
- Resource not found: Verify that the job UUID and queue identifiers are correct and exist in your ServiceM8 account.