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 allows updating (patching) user information within a Public Administration system. It is useful for scenarios where you need to modify existing user details such as name, contact info, role, or access restrictions without replacing the entire user record. For example, you might update a user's phone number after they change it, assign them to different companies, or adjust their role and permissions.
Properties
| Name | Meaning |
|---|---|
| Username | The unique identifier of the user to be patched (required). |
| X Fields | Optional fields mask to specify which fields should be returned in the response. |
| First Name | User's first name. |
| Last Name | User's last name. |
| Phone | User's phone number. |
| Role | User's role within the system. Options: Accountant, User, Confidential User, Supplier. |
| Title | User's title or position. |
| Restricted | Boolean flag indicating if the user has restricted access. |
| Limited | Boolean flag indicating if the user has limited access. |
| Companies Id | JSON array listing company IDs to assign the user to. |
Output
The node outputs JSON data representing the updated user resource after the patch operation. This typically includes the user's updated fields as accepted by the API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Dokka API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP PATCH requests with JSON bodies to update user data.
Troubleshooting
- Missing required Username: The patch operation requires the username to identify which user to update. Ensure this field is provided.
- Invalid JSON in Companies Id: The companies_id property expects a valid JSON array. Invalid JSON will cause request failures.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Field validation errors: Some fields like role have limited options; providing unsupported values may cause errors.
- Empty patch body: If no fields are provided to update, the API may reject the request or perform no action.
Links and References
- Dokka API Documentation (hypothetical link)
- n8n HTTP Request Node documentation for understanding PATCH requests and routing options.