Actions5
Overview
The node "FieldProxy" interacts with the FieldProxy API to manage work orders and their associated custom fields, messages, and other related data. Specifically, the "Update Custom Field" operation allows users to update the value of a specific custom field on a given work order.
This node is beneficial in scenarios where automated workflows need to modify metadata or additional information attached to work orders dynamically. For example, after completing certain checks or receiving external input, a workflow can update a custom field such as "Inspection Status" or "Priority Level" on a work order without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Work Order ID | The unique identifier of the work order whose custom field you want to update. |
| Custom Field ID | The unique identifier of the custom field that you want to update on the work order. |
| Custom Field Value | The new value to assign to the specified custom field. |
Output
The node outputs JSON data representing the result of the update operation. This typically includes confirmation details such as the updated custom field's ID, the new value, and possibly metadata about the work order or the update status.
If the node supports binary data output (not indicated here), it would represent any file or media content returned by the API, but for this operation, the output is purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the FieldProxy API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the FieldProxy API endpoints for work orders and custom fields.
Troubleshooting
- Invalid Work Order ID or Custom Field ID: If these IDs are incorrect or do not exist, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
- API Rate Limits or Network Issues: Temporary network problems or hitting API rate limits may cause errors. Retry after some time or check network connectivity.
- Incorrect Custom Field Value Format: If the custom field expects a specific format or type, providing an incompatible value might cause the update to fail. Validate the value according to the custom field's requirements.
Links and References
- FieldProxy API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes