Actions8
Overview
This node integrates with PocketBase, a backend service for managing collections and records. Specifically, the Record Delete operation allows users to delete a record from a specified collection in their PocketBase instance. This is useful when you want to programmatically remove outdated or unwanted data entries.
Common scenarios include:
- Cleaning up user-generated content that no longer applies.
- Removing test or temporary records after processing.
- Automating data lifecycle management by deleting records based on workflow logic.
Example: Deleting a user profile record by its ID from the "users" collection after account deactivation.
Properties
| Name | Meaning |
|---|---|
| Collection | The name of the PocketBase collection (table) from which the record will be deleted. |
| Record ID | The unique identifier of the record to delete within the specified collection. |
Output
The output JSON contains a confirmation of the deletion:
{
"success": true,
"id": "<recordId>"
}
success: Boolean indicating if the deletion was successful.id: The ID of the record that was deleted.
No binary data is output by this operation.
Dependencies
- Requires an active PocketBase instance accessible via URL.
- Requires credentials for authentication, either:
- Email and password for admin authentication, or
- An API token for token-based authentication.
- The node uses the official PocketBase JavaScript SDK internally.
- Credentials must be configured in n8n prior to use.
Troubleshooting
- Authentication errors: If the node throws errors about failed authentication or missing tokens, verify that the provided email/password or API token is correct and has sufficient permissions.
- Record not found: If the record ID does not exist in the specified collection, the PocketBase API may return an error. Ensure the record ID is valid.
- Collection name issues: Make sure the collection name matches exactly the one defined in your PocketBase instance.
- Network issues: Connectivity problems to the PocketBase server will cause failures; check network access and URL correctness.
- Permission errors: The authenticated user must have rights to delete records in the target collection.
If the node is set to continue on fail, errors will be returned as JSON objects with an error field instead of stopping execution.