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 job management workflows, such as prioritizing jobs, organizing them by queues, or triggering downstream processes based on queue placement.
Practical examples include:
- Automatically sending newly created or updated jobs to a particular queue for dispatching.
- Moving jobs to different queues based on status changes or external triggers.
- Setting expiry dates on queued jobs to manage workflow timing.
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, specifying when the job should expire. |
Output
The node outputs an array of JSON objects representing the response from the ServiceM8 API after sending the job to the queue. Each object corresponds to the API's response data for the processed job, typically including confirmation details about the job's queue assignment.
If the operation involves binary data (not indicated here), it would represent associated files or attachments related to the job, but this node primarily deals with JSON data.
Dependencies
- Requires an active connection to the ServiceM8 API via an API key credential configured in n8n.
- The node uses the ServiceM8 REST API endpoints to perform actions.
- The "Job Queue ID Or Name" options are dynamically loaded from the ServiceM8 job queues endpoint.
- Proper permissions on the ServiceM8 account to modify jobs and access queues are necessary.
Troubleshooting
- Missing or invalid UUID: If the job UUID is not provided or incorrect, the API call will fail. Ensure the UUID corresponds to an existing job.
- Invalid queue ID or name: Providing a non-existent queue identifier will cause errors. Use the dynamic options or verify queue existence in ServiceM8.
- API authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Empty fields error: If no fields are provided for update, the node may throw an error indicating missing required data.
- Network or API downtime: Temporary connectivity issues can cause request failures; retry or check ServiceM8 status.
Common error messages usually relate to invalid parameters or authentication failures. Reviewing the input parameters and credentials typically resolves these issues.