Leanios icon

Leanios

Join our community

Actions24

Overview

This node integrates with the Leanios API to perform operations on various resources, including Workorders. Specifically, for the Workorder resource and the getById operation, it retrieves a single workorder by its unique identifier. This is useful when you need to fetch detailed information about a specific workorder from your Leanios account.

Common scenarios include:

  • Fetching the status or details of a particular workorder to display in dashboards.
  • Integrating workorder data into other systems or workflows.
  • Automating follow-up actions based on workorder attributes.

Example: Retrieve workorder with ID 123 from the Leanios system hosted at subdomain "dummy".

Properties

Name Meaning
Subdomain The Leanios account subdomain to target (e.g., "dummy"). Required for API endpoint URL.
id The unique numeric identifier of the workorder to retrieve.

Output

The node outputs a JSON array containing the retrieved workorder object as returned by the Leanios API. The structure corresponds directly to the API response for a single workorder, typically including fields such as workorder ID, status, dates, related entities, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Leanios API credential with username and password for authentication.
  • Needs network access to the Leanios API endpoint at https://{Subdomain}.leanios.com/api/v1/workorders/{id}.
  • The node expects the user to provide the correct subdomain and workorder ID.

Troubleshooting

  • Invalid Credentials: If authentication fails, verify that the provided API credentials are correct and have sufficient permissions.
  • Resource Not Found: If the specified workorder ID does not exist, the API may return a 404 error. Confirm the ID is valid.
  • Network Issues: Ensure the subdomain is correct and reachable from the n8n environment.
  • Missing Required Parameters: Both Subdomain and id must be provided; otherwise, the request will fail.
  • Error Messages: Errors thrown by the node will contain the message from the API or network layer. Review these messages to identify issues such as invalid input or server errors.

Links and References

Discussion