Extensions Directory

Extensions are installable packages which give CiviCRM new functionality, and this directory provides a centralized list of extensions which the CiviCRM community has created. This listing displays CiviCRM extensions that work on all Content Management Systems (CMS).

The newest extensions · Create an extension · Add an extension to this directory

Platform integrations

As well as extensions that install within CiviCRM and work on all CMSs listed below, you can browse directories of integrations that are made specifically for Backdrop, Drupal, Joomla and WordPress.

This extension adds a "Clone" action to SearchKit Displays which list Cases. When a Case is cloned, all its fields, including custom fields, are copied to the clone, along with copies of Case Roles and Case Activities.
Current Usage: 1
Campaign Manager (Next Generation) is an upgraded version from the original extension de.systopia.campaign.
Current Usage: 1
Membership "Behaviours" (Rules) for FormBuilder
Current Usage: 1
Import counties for various countries. Depends on advimport.
Current Usage: 1
This is just another CiviCRM extension which integrates with Zoom. Provides the following features:

CiviRule to create Zoom Webinar from Event and create Zoom Meeting from Event
CiviRule to update Zoom details
CiviRule to delete a Zoom
CiviRule to add an Event Participant to a Zoom
CiviRule to delete a Participant from a Zoom
Scheduled Job to import Zoom Webinars and Zoom Events as CiviCRM Events
Scheduled Job to check CiviCRM Events linked to Zoom and import the Zoom registrations, attendees and absentees. Record as CiviCRM Participants and update Participant Status.
Current Usage: 1
Restricts payment methods to specific domains. For multisite CiviCRM instances.

This is especially helpful with accounting integration to ensure that your different sites all use payment methods tied to specific bank accounts.
Current Usage: 1
Allows generating CDN Tax Receipts via a CiviRules action.
Current Usage: 1
This extension provides a set of Actions for CiviRules. These Actions enable integration to a process engine capable of executing long running business processes. Process "flows" may orchestrate both the internal CiviCRM APIs and also external APIs to loosely coupled systems.

The initial Alpha release will provide REST Actions to a Python container within the same docker environment (for security reasons). A fully functional Docker image for each CMS will be available for download from the repo, to make evaluation as simple as possible. For production environments, additional steps will be required to ensure security. You are strongly advised to seek help from a CiviCRM partner or cyber security expert before running this in a live environment.

Eventually we plan to provide some example Python flows, admin forms to view audit trails and manage Running, Completed, Faulted and Archived process instances.

For more help, ping us an email: support@encircle.co.uk.
Current Usage: 1
This is work-in-progress towards getting CiviCRM able to run without a CMS.

We'd love help with this, so please join the standalone channel on Mattermost at chat.civicrm.org
Current Usage: 1
Use employer relationship description to store the job title and then synchronize the contact summary job title with the primary employer relationship.
Current Usage: 1
This extension is intended to anonymize your database, so you can share your CiviCRM database more readily.
Current Usage: 1
This extension allows searching for names in any order. It also handles searching for duplicate names (where someone has been given the same name twice).

This is very useful for Arabic or other such names that consist of several words that may be presented in any order and thus do not conform to the firstname lastname convention.
Current Usage: 1
Provides ability to search activities by case filters
Current Usage: 1
When you get a receipt for a recurring contribution/membership you also get some links for self-service cancel, update and billing. This extension provides those links as tokens that can be used in any messagetemplate when the renderer gets a contribution, membership ID or recurring contribution ID.
Current Usage: 1
Filters the mailing recipients using the Preferred Language on their contact record.
Current Usage: 1