Actions21
Overview
This node interacts with the "People" resource of the Runn platform, specifically supporting the "Archive" operation among others. The Archive operation allows users to mark a person as archived in their Runn account, effectively deactivating or hiding that person's record without deleting it permanently. This is useful for managing personnel records by keeping historical data intact while removing inactive individuals from active workflows.
Common scenarios include:
- Archiving former employees or contractors who no longer participate in projects.
- Temporarily disabling access or visibility of a person without losing their associated data.
- Cleaning up active lists while preserving audit trails.
Example: A project manager wants to archive a team member who has left the company so they no longer appear in active assignments but their past contributions remain recorded.
Properties
| Name | Meaning |
|---|---|
| ID or Email | The unique identifier or email address of the person to archive. At least one must be provided. |
| Dry Run | When enabled, simulates the archive operation without making actual changes to the Runn account. |
| Options | Additional optional parameters (currently empty, reserved for future use). |
Output
The node outputs an array of JSON objects representing the result of the archive operation on the specified person(s). Each object typically contains details about the archived person, such as their ID, status, and any metadata returned by the Runn API.
If the Dry Run option is enabled, the output reflects what would happen without applying changes.
No binary data output is involved.
Dependencies
- Requires an active connection to the Runn API via an API key or authentication token configured in n8n.
- The node depends on internal helper modules for handling API requests specific to the People resource.
- No additional external services beyond Runn are required.
Troubleshooting
- Error: Unsupported resource — Occurs if a resource other than "people", "clients", or "projects" is specified. Ensure the Resource parameter is set correctly.
- Missing ID or Email — The operation requires at least one identifier; ensure this property is filled.
- API Authentication Errors — Verify that the API credentials are valid and have sufficient permissions.
- Dry Run Misunderstanding — Remember that enabling Dry Run will not change any data; use it only to simulate operations.
- If the node returns an error message in the output JSON under
error, check the message for details and adjust inputs accordingly.
Links and References
- Runn API Documentation — Official API reference for understanding available endpoints and data structures.
- n8n Documentation — Guides on configuring credentials and using custom nodes.