Actions15
Person → Delete
AI-generatedOverview
This node integrates with the RogerRoger API to manage "Person" resources, among others. Specifically, the Delete Person operation allows users to remove a person record from the RogerRoger system by specifying the person's unique identifier.
Common scenarios for this node include:
- Automating cleanup of outdated or incorrect person records.
- Integrating with workflows that synchronize contact data and need to delete persons when they are removed from another system.
- Managing contacts programmatically in bulk via n8n workflows.
Example use case:
- A workflow triggers when a user is deleted from a CRM, then uses this node to delete the corresponding person in RogerRoger by their ID.
Properties
| Name | Meaning |
|---|---|
| Person ID | Select the person to delete by either entering their UUID directly or searching from a list. |
The "Person ID" property supports two modes:
- ID: Enter a valid UUID string (e.g.,
0197cb13-ae93-7368-a3d6-ad8b6ba808db). - List: Search and select a person from a searchable dropdown list populated dynamically from RogerRoger.
Output
The output JSON contains at least the following fields:
resource: The resource type, here always"person".operation: The operation performed, here"delete".- Additional fields returned by the RogerRoger API upon deletion, typically confirmation details or status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the RogerRoger API.
- The node expects the API base URL and key to be configured in the credentials.
- Uses HTTP DELETE requests to the endpoint
/persons/{personId}on the RogerRoger API.
Troubleshooting
- Invalid UUID error: If the Person ID does not match the UUID format, the node will reject it. Ensure the ID is a valid UUID.
- Person not found: If the specified person ID does not exist, the API may return a 404 error. Verify the ID is correct and exists in RogerRoger.
- Authentication errors: If the API key is missing or invalid, the node will fail with an authentication error. Check the configured credentials.
- Network issues: Connectivity problems to the RogerRoger API will cause request failures. Confirm network access and API availability.
If the node is set to continue on failure, errors will be included in the output JSON under an error field.
Links and References
- RogerRoger API Documentation (generic link, replace with actual if available)
- n8n Expressions Documentation - for using expressions in properties like IDs
- UUID Format Reference