Actions21
Overview
This node interacts with the "People" resource of the Runn platform, specifically supporting the Unarchive operation among others. The Unarchive operation restores a previously archived person record in your Runn account, making it active and available again.
Typical use cases include:
- Reinstating a person who was mistakenly archived.
- Reactivating a former team member or contact for new projects.
- Managing personnel lifecycle by toggling archive status without deleting data.
For example, if you accidentally archived a person's profile, using this node's Unarchive operation allows you to reverse that action seamlessly.
Properties
| Name | Meaning |
|---|---|
| ID or Email | The unique identifier or email address of the person to unarchive. At least one must be provided. |
| Dry Run | When enabled, simulates the unarchive operation without making actual changes to the Runn account. |
| Options | Additional optional parameters (currently no specific options defined for this operation). |
Output
The node outputs an array of JSON objects representing the result of the unarchive operation on the specified person(s). Each object typically contains the updated person data as returned by the Runn API after unarchiving.
If the operation is run in dry-run mode, the output will simulate the response without changing any data.
No binary data output is produced by this node.
Dependencies
- Requires access to the Runn API via an authenticated connection using an API key or token.
- The node depends on internal helper modules managing API calls for people operations.
- Proper configuration of credentials within n8n is necessary to authenticate requests.
Troubleshooting
- Error: Unsupported resource — This occurs if the resource parameter is set to something other than supported values like "people". Ensure the resource is correctly set to "people".
- Missing ID or Email — The operation requires at least one identifier; ensure you provide either the person's ID or email.
- API Authentication Errors — Verify that the API key/token credential is valid and has sufficient permissions.
- Dry Run Confusion — If no changes appear after running, check if Dry Run is enabled; disable it to perform actual unarchive.
- Network or API Errors — Check network connectivity and Runn API status if requests fail unexpectedly.
Links and References
- Runn API Documentation (for detailed API endpoints and data models)
- n8n Documentation (for general usage of custom nodes and credentials setup)