CiviCRMInstall

Summary

Delete a contact in CiviCRM by specifying its internal ID.

Inputs

• ID (required) — The internal CiviCRM ID of the contact to delete.
• Runtime Bearer Token (Optional) — A JWT for a specific real user, used as the Authorization Bearer header to enforce per-user permissions. When set, the node uses this token exclusively without falling back to the credential's API key.
• Base URL Override — Optionally override the credential's base URL to target a different CiviCRM instance.

Output shape

a single JSON object per input item indicating success, deleted contact ID, and API response.

The output JSON contains 'success' (boolean), 'message' (string confirming deletion), 'deleted_id' (the deleted contact ID), and 'api_response' (raw response from CiviCRM). The node emits one output item per input item processed. Errors during deletion can be handled with continueOnFail. The operation uses CiviCRM API v4 'Contact/delete' action via POST with filtering on the contact ID.

Examples

Example 1: Delete a contact with ID 123

Set Resource to 'Contact' and Operation to 'Delete', then provide '123' as the ID parameter.

Links

• n8n community nodes installation guide