Actions5
Overview
The node named "FieldProxy" interacts with the FieldProxy API to perform various operations related to work orders, custom fields, and messages. Specifically, the "Get Work Order" operation retrieves detailed information about a specific work order by its ID. This node is useful in scenarios where you need to integrate FieldProxy data into your workflows, such as fetching work order details for reporting, updating, or triggering other automation steps based on work order status or content.
Practical examples include:
- Automatically retrieving work order details when a new work order is created.
- Fetching work order information to update an external system or database.
- Using work order data to trigger notifications or further processing in n8n.
Properties
| Name | Meaning |
|---|---|
| Work Order ID | The unique identifier of the work order to retrieve. This is a required string property. |
Output
The output of the "Get Work Order" operation contains a JSON object representing the detailed data of the requested work order. This typically includes all relevant fields returned by the FieldProxy API for a work order, such as identifiers, status, dates, assigned personnel, and any other metadata associated with that work order.
If the node supports binary data output (not indicated explicitly here), it would represent attachments or files related to the work order, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authenticating with the FieldProxy API.
- The base URL for the API is configured via credentials and sanitized to remove trailing slashes.
- The node depends on the FieldProxy API being accessible and responsive.
Troubleshooting
- Common issues:
- Invalid or missing Work Order ID will cause the API call to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent reaching the FieldProxy API.
- Error messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Work order not found" errors suggest the provided Work Order ID does not exist; double-check the ID.
- Timeout or network errors require checking internet connection and API availability.
Links and References
- FieldProxy API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes