CiviCRM
Interact with CiviCRM API v4 (Civi-Go compatible).
Supports Contact, Membership, Group, Relationship and Activity entities.
Includes dynamic mapping of email, phone, address and location types.
Includes birth_date validation and JSON filters for GET MANY.
Actions30
Overview
This node interacts with the CiviCRM API v4 to manage Membership entities, specifically supporting the deletion of a membership record by its ID. It is useful in scenarios where automated workflows need to remove membership records from CiviCRM, such as when a membership expires or is canceled. For example, a user can configure this node to delete a membership by providing the membership ID, streamlining membership management within an automation process.
Use Case Examples
- Deleting a membership record by specifying its ID to keep the CRM data up to date.
- Automating membership cleanup tasks by removing memberships that meet certain criteria via workflow triggers.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the membership record to delete. This is a required numeric input used to specify which membership to remove. |
Output
JSON
success- Indicates whether the deletion was successful (true/false).message- A confirmation message indicating the membership ID that was deleted.deleted_id- The ID of the membership that was deleted.api_response- The raw response from the CiviCRM API after the delete operation.
Dependencies
- Requires an API key credential for authenticating with the CiviCRM API v4.
Troubleshooting
- Ensure the provided membership ID exists in the CiviCRM system; otherwise, the delete operation will fail or have no effect.
- Verify that the API credentials are valid and have sufficient permissions to delete membership records.
- Common error messages may include invalid ID format or authorization errors; check the ID input and API token validity to resolve these.
Links
- CiviCRM API v4 Documentation - Official documentation for the CiviCRM API v4 used by this node.