Actions27
- Public Administration Actions
- Public Actions
- Public Transactions Actions
- Get Indexes Account
- Post Indexes Account
- Get Indexes Categories
- Post Indexes Categories
- Get Indexes Customer
- Post Indexes Customer
- Get Invoices
- Patch Invoices
- Get Orders
- Post Orders
- Get Payments
- Patch Payments
- Get Indexes Status
- Post Indexes Status
- Get Indexes Tax Rate
- Post Indexes Tax Rate
- Get Indexes Vendor
- Post Indexes Vendor
Overview
This node interacts with a Public Administration API to retrieve detailed information about a specific user resource. It is useful in scenarios where you need to fetch user data from a government or public administration system, such as verifying user identity, retrieving user profiles, or integrating public sector user data into workflows.
For example, you might use this node to:
- Get detailed user information by username for validation purposes.
- Fetch selective fields of user data by specifying a custom fields mask.
- Integrate public administration user data into an internal CRM or database.
Properties
| Name | Meaning |
|---|---|
| Username | The unique identifier (username) of the user whose information you want to retrieve. |
| X Fields | An optional string to specify a fields mask, allowing you to limit which user fields are returned. |
Output
The node outputs JSON data representing the user resource retrieved from the Public Administration API. This JSON typically contains user details such as name, contact information, roles, and other relevant attributes depending on the API's response structure.
If the "X Fields" property is used, the output JSON will include only the specified fields, enabling more efficient data handling.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating requests to the Public Administration API.
- The base URL for the API must be configured in the node credentials.
- The node uses standard HTTP headers including
Accept: application/jsonandContent-Type: application/json. - The optional
X-Fieldsheader can be set dynamically based on input parameters.
Troubleshooting
- Missing or invalid username: Since the username is required, ensure it is provided and correctly formatted; otherwise, the API call will fail.
- Invalid or missing API credentials: Authentication errors may occur if the API key or token is not set up properly.
- Incorrect fields mask in X Fields: Providing an invalid fields mask may result in incomplete or error responses from the API.
- Network or connectivity issues: Ensure that the base URL is reachable and there are no firewall restrictions blocking the request.
Common error messages might include authentication failures, 404 not found if the username does not exist, or 400 bad request if parameters are malformed.
Links and References
- Refer to the Public Administration API documentation for details on available user fields and valid values for the fields mask.
- n8n documentation on how to configure API credentials and use HTTP headers in nodes.