Actions21
Overview
This node interacts with the "People" resource of the Runn platform, specifically supporting the "Delete" operation among others. The Delete operation allows users to remove a person from their Runn account by specifying either the person's ID or email. This is useful for managing and cleaning up user data, such as removing former employees or contacts no longer relevant to ongoing projects.
A practical example would be automating the removal of people who have left an organization by feeding their IDs or emails into this node, ensuring the Runn system stays up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID or Email | The unique identifier (ID) or email address of the person to delete. At least one must be provided. |
| Dry Run | When enabled, simulates the deletion without making actual changes to the Runn account. Useful for testing. |
| Options | A collection placeholder for additional optional parameters (currently empty). |
Output
The node outputs an array of JSON objects representing the result of the delete operation for each input item. Each JSON object typically contains confirmation details about the deleted person or error information if the operation failed.
If the "Dry Run" option is enabled, the output will simulate the deletion results without affecting real data.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Runn API via an authenticated connection.
- Needs an API key or authentication token configured in n8n to authorize requests to the Runn service.
- The node depends on internal helper modules that handle API communication and operation execution for the People resource.
Troubleshooting
Common Issues:
- Providing neither ID nor email will cause the operation to fail because at least one identifier is required.
- Using invalid or non-existent IDs/emails will result in errors indicating the person could not be found.
- Network or authentication failures can prevent successful API calls.
Error Messages:
"Unsupported resource": Occurs if a resource other than "people", "projects", or "clients" is specified.- Errors returned from the Runn API will be passed through; these often indicate invalid input or permission issues.
Resolutions:
- Ensure the "ID or Email" field is correctly filled.
- Verify API credentials and network connectivity.
- Use the "Dry Run" mode to test inputs before actual deletion.
Links and References
- Runn API Documentation (for detailed API usage)
- n8n Documentation (for general node usage and credential setup)