Actions21
Overview
This node interacts with a service managing Clients, Projects, and People resources. Specifically for the Clients resource with the Unarchive operation, it restores previously archived client records to an active state. This is useful in scenarios where clients were archived (soft-deleted or hidden) but need to be reinstated for further processing or communication.
Practical examples:
- A user accidentally archived a client and wants to restore their data without re-entering all information.
- Reactivating a client account that was temporarily suspended or archived.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client to unarchive. This is required to specify which client record to restore. |
| Options | Additional optional parameters for the operation (currently no specific options defined). |
Output
The node outputs an array of JSON objects representing the results of the unarchive operation on the specified client(s). Each output item corresponds to one input item processed.
The json field contains the response data from the API after unarchiving the client, typically including updated client details reflecting the active status.
If an error occurs and "Continue On Fail" is enabled, the output will contain an object with an error property describing the failure message.
No binary data output is involved.
Dependencies
- Requires access to the external Runn API service.
- Needs an API authentication token or key configured within n8n to authorize requests.
- The node depends on internal helper modules handling API calls for clients, projects, and people operations.
Troubleshooting
Common issues:
- Providing an invalid or non-existent client ID will cause the operation to fail.
- Missing or incorrect API credentials will result in authentication errors.
- Attempting to unarchive a client that is not archived may return an error or no change.
Error messages:
"Unsupported resource <resource>": Occurs if the resource parameter is set incorrectly.- API error messages returned from the external service are passed through; check the message for details.
Resolutions:
- Verify the client ID is correct and exists in the system.
- Ensure API credentials are properly configured and valid.
- Confirm the client is currently archived before attempting to unarchive.
Links and References
- Runn API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes