Actions21
Overview
This node interacts with a service managing Clients, Projects, and People resources. Specifically for the Clients - Archive operation, it archives a client identified by its unique ID. Archiving typically marks the client as inactive or hidden without deleting their data, useful for maintaining historical records while keeping active client lists clean.
Common scenarios include:
- Temporarily disabling a client account without losing data.
- Cleaning up active client views by archiving clients no longer in use.
- Managing client lifecycle states in project management or CRM workflows.
Example: Automatically archive a client after project completion to keep the active client list focused on ongoing work.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client to archive. This is required to specify which client to archive. |
| Options | Additional optional parameters for the archive operation (currently no specific options defined). |
Output
The node outputs an array of JSON objects representing the result of the archive operation. Each item corresponds to the processed client data after archiving. The exact structure depends on the API response but generally includes confirmation of the archived status and client details.
No binary data output is indicated.
Dependencies
- Requires connection to the external service's API managing clients, projects, and people.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node relies on internal helper modules for executing operations per resource type.
Troubleshooting
- Error: Unsupported resource — Occurs if an invalid resource name is provided; ensure "clients" is selected.
- Missing ID error — The archive operation requires a valid client ID; verify the input property is set correctly.
- API authentication errors — Check that the API key or token is properly configured and has sufficient permissions.
- Network or timeout issues — Ensure connectivity to the external API endpoint and retry if transient failures occur.
If the node is set to continue on failure, errors will be returned inside the JSON output under an error field instead of stopping execution.
Links and References
- Refer to the external service’s API documentation for client management and archiving endpoints.
- n8n documentation on creating and configuring API credential nodes.
- General best practices for handling archive operations in CRM or project management systems.