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.

Current Usage: 14
Current Usage: 14
This extension forms the basis for funding application management in CiviCRM: It supports processes for application submission, application review, approval, call for funds, payment instruction and proof of use.
Current Usage: 13
With this extension you can give constituents access to their CiviCRM data without them needing a Drupal account.

This extension has been created with the following use case in mind: Let people read and change their contact data in a drupal webform. To access the data, people need to enter their email address. A link to the prefilled webform will be sent to that email address if and only if the email address exists within CiviCRM.
Current Usage: 13
RFM = Recency, Frequency, Monetary value

https://en.wikipedia.org/wiki/RFM_(market_research)
Current Usage: 13
This extension doesn't offer any new features to CiviCRM, but it provides replacements for deprecated CiviCRM core functions with the same signature. This aims at making it easier to adjust your extensions to a new CiviCRM version, if you run into issues with deprecation warnings or purged deprecated functions.
Current Usage: 13
When event self-service cancellation is enabled, do not allow to transfer a registration.
Current Usage: 13
A CiviCRM extension to help you manage different funding pipelines, e.g. grant applications, partnerships, consultancy, that builds on CiviCase.
Current Usage: 13
This extension allows to find and export payment(s) for contribution(s).
Current Usage: 13
This extension allows you to choose a set of groups which will be added to new contacts if the logged in contact is also in that group.
Current Usage: 13
Allows points to be allocated to contacts.
Current Usage: 13
Payment processor using the omnipay functionality for connecting to payment processors. Such as Mollie
Current Usage: 12
Provides extra options to translate receipts generated by the cdntaxreceipt extension.
Current Usage: 12
Allows the admin to set the `From` email address that matches the "Sending Domain" for all emails being sent from CiviCRM, while still allowing users to select the `Reply-To` email addresses.
Current Usage: 12
This is a front-end theme with three-purposes:
- stops Bootstrap3 from loading on FormBuilder & SearchKit pages (by overwriting with a blank file). This is useful if you have a Bootstrap theme in your front-end that's trying to do things differently and there's clashes.
- removes most of CiviCRM's CSS beyond a few essential bits.
- uses CSS variables to style those 'essential bits' with goal of making it quick to style CiviCRM elements (buttons, input boxes, tables, etc) to match your front-end theme.

NB - this is a work-in-progress, tested only on the few specific front-end pages I needed it for. Please use at your own risk (and feel free to PR more 'essentials bits').
Current Usage: 12