Actions795
- X Type Role Actions
- View Filter Actions
- View List Group Actions
- View Lists Actions
- Virima Details Actions
- Virtual Agent Actions
- VM Workspace Details Actions
- Webhook Actions
- Webhook Event Actions
- Webhook Repository Actions
- Wordpress Details Actions
- Wordpress Org Details Actions
- Workdays Actions
- Workflow Target Actions
- Xero Details Actions
- Xtype Actions
- X Type Mapping Actions
- To Do Group Actions
- T Outcome Actions
- Tree Actions
- T Status Actions
- Twilio Whats App Details Actions
- Twitter Details Actions
- Type Info Actions
- Uname Actions
- Uname Event Subscription Actions
- Uname Notification Actions
- Uname Presence Subscription Actions
- Unsub Email Service Users Actions
- User Change Actions
- User Roles Actions
- Users Actions
- Version Actions
- View Columns Actions
- Snipe IT Details Actions
- Snow Details Actions
- SQL Import Actions
- Std Request Actions
- Stream One Ion Details Actions
- Supplier Order Header Actions
- Synnex Details Actions
- Tabname Actions
- Tag Actions
- Tanium Details Actions
- Tax Actions
- Tax Rule Actions
- Team Image Actions
- Teams Chat Message Actions
- Tech Data Reseller Details Actions
- Tenable Actions
- Tenable Details Actions
- Ticket Area Actions
- Timesheet Actions
- Timesheet Event Actions
- Timeslot Actions
- Schedule Occurrence Actions
- Screen Layout Actions
- Script Header Actions
- Search Actions
- Section Detail Actions
- Security Question Actions
- Security Question Validate Actions
- Service Availability Actions
- Service Category Actions
- Service Request Details Actions
- Service Restriction Actions
- Serv Site Actions
- Serv Status Actions
- Setup Tab Actions
- Setup Tab Group Actions
- Shopify Details Actions
- Site Actions
- Slack Details Actions
- Sla Head Actions
- Quotation Header Actions
- Recurring Invoice Header Actions
- Release Actions
- Release Branch Actions
- Release Component Actions
- Release Note Group Actions
- Release Pipeline Actions
- Release Product Actions
- Release Type Actions
- Remote Session Data Actions
- Remote Session Teams Actions
- Report Data Actions
- Report Repository Actions
- Request Type Actions
- Request Type Field Actions
- Request Type Group Actions
- Roadmap Actions
- Sage Business Cloud Details Actions
- Sales Mailbox Actions
- Sales Mailbox Detail Actions
- Schedule Actions
- Outgoingemail Actions
- Pager Duty Mapping Actions
- Parts Lookup Actions
- Parts Lookup Confirmation Actions
- Pdf Template Actions
- Pdf Template Repository Actions
- Policy Actions
- Power Shell Script Actions
- Power Shell Script Criteria Actions
- Power Shell Script Processing Actions
- Prepay History Actions
- Projects Actions
- PRTG Details Actions
- Publish Profiles Actions
- Qualification Actions
- Quick Books Details Actions
- Message Content Actions
- Microsoft Subscription Mapping Actions
- Microsoft Teams Mapping Actions
- Module Setup Actions
- MYOB Details Actions
- N Central Details Actions
- NHD Device Info Actions
- NHD Identity Application Actions
- NHD Roles Actions
- NH Server Config Actions
- Notification Content Actions
- Online Status Actions
- Opps Actions
- Order Head Actions
- Organisation Actions
- Outbound Integration Actions
- Outbound Integration Method Actions
- Outbound Integration Repository Actions
- Outgoing Actions
- Outgoing Attempt Actions
- Kandji Details Actions
- Kashflow Details Actions
- KB Entry Actions
- Language Pack Actions
- Language Pack Translations Custom Actions
- LDAP Connection Actions
- Licence Actions
- Licence Change Actions
- Licence Info Actions
- Licence Role Actions
- Live Chat Header Actions
- Live Chat Msg Actions
- Login Token Actions
- Lookup Actions
- Mailbox Actions
- Mail Campaign Actions
- Mail Campaign Email Actions
- Manage Engine Details Actions
- Marketing Open Actions
- Marketing Unsubscribe Actions
- Mattermost Details Actions
- Integration Configuration Actions
- Integration Data Actions
- Integration Error Actions
- Integration Export Actions
- Integration Field Data Actions
- Integration Field Mapping Actions
- Integration Look Up Actions
- Integration Request Actions
- Integration Runbook Variable Group Actions
- Integration Site Mapping Actions
- Integrator Log Actions
- Integrator Schedule Actions
- Invoice Change Actions
- Invoice Header Actions
- Invoice Payment Actions
- Item Actions
- Item Group Actions
- Item Stock Actions
- Item Stock History Actions
- Item Supplier Actions
- Jamf Details Actions
- Jira Details Actions
- Journey Actions
- Fault To Do Actions
- Feed Actions
- Feedback Actions
- Field Actions
- Field Group Actions
- Field Info Actions
- Flow Detail Actions
- Flow Header Actions
- Formatted Email Actions
- Fortnox Details Actions
- Generic Actions
- Google Business Details Actions
- Halo News Actions
- Holidays Actions
- Impersonation Request Actions
- Import Csv Actions
- Incoming Email Actions
- Incoming Event Actions
- Ingram Micro Details Actions
- Ingram Micro Reseller Details Actions
- Instance Actions
- Device Applications Actions
- Device Change Actions
- Device Meter Reading Actions
- Distribution Lists Actions
- Distribution Lists Log Actions
- Downtime Actions
- Dynatrace Details Actions
- Ecommerce Order Actions
- Email Address Book Actions
- Email Rule Actions
- Email Store Actions
- Esc Msg Actions
- Event Actions
- Event Rule Actions
- Exact Details Actions
- External Link Actions
- Facebook Details Actions
- FAQ List Head Actions
- Fault Approval Actions
- Fault Forecasting Actions
- Faults Actions
- Contactgroup Actions
- Contactgroupcontacts Actions
- Contract Actions
- Contract Header Actions
- Contract Rule Actions
- Contract Schedule Actions
- Contract Schedule Plan Actions
- Contract Template Header Actions
- Control Actions
- Costcentres Actions
- CSV Template Actions
- Currency Actions
- Custom Button Actions
- Custom Query Actions
- Custom Table Actions
- Dashboard Links Actions
- Datto Commerce Details Actions
- Device Actions
- Booking Type Actions
- Bookmark Actions
- Budget Type Actions
- Bulk Email Actions
- Business Central Details Actions
- Cab Header Actions
- Call Log Actions
- Canned Text Actions
- Category Detail Actions
- Certificate Actions
- Charge Rate Actions
- Chat Flow Actions
- Chat Profile Actions
- Company Actions
- Config Commit Actions
- Confirm Closure Actions
- Confluence Details Actions
- Connected Instance Actions
- Consignment Header Actions
- Amazon Seller Details Actions
- Analyzer Profile Actions
- Appointment Actions
- Approval Process Actions
- Approval Process Rule Actions
- Approval Store Actions
- Area Actions
- Area Azure Tenant Actions
- Area Item Actions
- Area Note Actions
- Area Popup Actions
- Area Request Type Actions
- Attachment Actions
- Audit Actions
- Audit Password Field Actions
- Autoassign Actions
- Automation Actions
- Avalara Details Actions
- AWS Details Actions
- Azure AD Connection Actions
- Azure AD Mapping Actions
- Azure Delta Actions
- Azure Dev Ops Actions
- Background Task Actions
- Actions Actions
- Addressbook Actions
- Address Store Actions
- Adobe Acrobat Details Actions
- Adobe Commerce Details Actions
- Agent Check In Actions
- Agent Image Actions
- Ai Suggestion Actions
Field Info → Get One Field Info
AI-generatedOverview
This node integrates with the Halo PSA API to retrieve detailed information about a specific field within the system. The "Get One Field Info" operation under the "Field Info" resource fetches metadata and optionally additional details related to a single field identified by its ID.
Typical use cases include:
- Fetching metadata about custom or standard fields in Halo PSA for dynamic form generation.
- Retrieving lookup values associated with a field to populate dropdowns or selection lists.
- Obtaining detailed descriptions or configurations of fields for reporting or automation purposes.
For example, a user might want to get all relevant information about a custom field on an entity to display it in a dashboard or validate input data before submission.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the field to retrieve information for. (Required) |
| Entityid | Optional query parameter specifying the entity ID related to the field. |
| Getlookupvalues | Optional query parameter indicating whether to include lookup values associated with the field. |
| Includedetails | Optional query parameter to specify if detailed information about the field should be included. |
| Livecustomfields | Optional string query parameter, possibly used to specify live custom fields to consider. |
| Userid | Optional query parameter specifying the user ID context for the request. |
Output
The node outputs a JSON object containing the response from the Halo PSA API for the requested field. This typically includes:
- Field metadata such as name, type, label, and configuration.
- Lookup values if requested, which are possible selectable options for the field.
- Additional details depending on the parameters set, like validation rules or dependencies.
If the API returns binary data (not indicated here), it would be provided in the binary output; however, this operation appears to return only JSON data.
Example output structure (simplified):
{
"id": 123,
"name": "CustomField1",
"type": "string",
"label": "Custom Field 1",
"lookupValues": [
{"id": 1, "value": "Option A"},
{"id": 2, "value": "Option B"}
],
"details": {
"description": "Detailed info about the field",
"required": true
}
}
Dependencies
- Requires an active connection to the Halo PSA API via an API key credential.
- The node expects credentials providing base URL, tenant identifier, client ID, and client secret for authentication.
- No other external services or environment variables are explicitly required.
Troubleshooting
No credentials returned!
This error occurs if the node cannot find or access the required API credentials. Ensure that valid credentials are configured in n8n before running the node.Resource or Operation not found
If the specified resource or operation is invalid or misspelled, the node will throw an error. Verify that "Field Info" and "Get One Field Info" are correctly selected.API request errors
Network issues, incorrect parameters, or insufficient permissions can cause API request failures. Check the error message returned in the node output for details. Enabling "Continue On Fail" allows processing subsequent items despite errors.Invalid or missing required parameters
The "Id" property is mandatory. Omitting it or providing an invalid value will result in errors.
Links and References
- Halo PSA API Documentation (general reference for API endpoints and parameters)
- n8n Documentation - Creating Custom Nodes
- n8n HTTP Request Node (for understanding underlying request mechanics)
This summary is based solely on static analysis of the provided source code and property definitions.