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.

Adds Paypal Complete Payments support for FormBuilder.
Current Usage: 1
This extension adds an api to generate and validator one time passwords. This password is send to the users email address and the user can then sign in with this password at a portal.
Current Usage: 1
Book a meeting (or reserve something online) using CiviBooking.
Current Usage: 1
Receive messages from external sources and process them within CiviCRM (either as an API or a form processor).
Current Usage: 1
This CiviCRM extension modifies the API permissions to allow it to be called with just the "Access AJAX API" permission instead of requiring the more restrictive default permissions. This extension modifies permissions on the following:

- ContributionRecur::getActions
- Contact::getActions
- Membership::getActions
- Membership::get
- Membership::getFields
- Membership::getLinks

Making these changes allows this data to utilized frontend-facing Formbuilder search displays.
Current Usage: 1
Provides a workflow to request refunds.

A "Refund Request" activity and links are added to Contributions/Payments to "Request Refund".
Then a "Find Refund Requests" search is provided which allows someone with "Refund Contributions" permissions
to find and process those refunds.
Current Usage: 1
If you create employee relationships using the API, it can result in contacts having an employee relationship but an empty employer_id field.

This extension provides a couple of functions to rectify that by populating the employer_id field from employee relationships.
Current Usage: 1
Developer-oriented extension that makes it possible to embed Drupal (10+) blocks or entities in a CiviCRM Smarty template file. Requires the Twig Tweak module.
Current Usage: 1
The com.skvare.reminderpreview extension is a tool developed by Skvare for CiviCRM, designed to enhance the management of scheduled reminders.

This extension allows users to preview which contacts will receive scheduled reminders at a specified date and time. By generating a CSV file, it provides a clear list of recipients, enabling administrators to verify and adjust reminder settings before they are dispatched.

Key Features:
Scheduled Reminder Preview: Simulate and review the list of contacts set to receive reminders at a chosen date and time.
CSV Export: Download the prepared list of contacts in CSV format for easy analysis and record-keeping.
Current Usage: 1
Provides a better experience when we click on the print icon of CiviCRM modal popups.
Current Usage: 1
3CX PBX integration for CiviCRM. Makes it possible to log calls and lookup contacts in CiviCRM.
Current Usage: 1
Deletes the linked CMS User when permanently deleting a CiviCRM Contact.
Current Usage: 1
The "Manage Extensions" screen provides an option to download upgraded extensions. In CiviCRM 5.x, this mechanism is prone to sporadic errors -- such errors are usually invisible to developers but obvious to site-builders. This hotfix is aimed at site-builders. It has been spot-tested on a mix of versions+platforms, including:

* CiviCRM v5.45 (Backdrop)
* CiviCRM v5.75 (WordPress)
* CiviCRM v5.81 (Drupal 7)

This simply fixes the behavior. It does not create any new screens or configuration-options.

NOTE: This hotfix is only intended for past versions of CiviCRM. As of v6.1+, a similar fix is built into CiviCRM.
Current Usage: 1
A provider for the civirepresent extension, making use of the geocodio.io service.
Current Usage: 1
A very simple extension to allow permissioned users to access a set of static HTML + other resources.

This is useful if you want to provide restricted access to a static HTML site for users authenticated to CiviCRM. It is not (yet 😅) a CMS or CMF or page builder etc. It may be useful if, for example, you have just gotten rid of a Drupal 7 intranet type site in favour of CiviCRM Standalone and now have nowhere to keep all that old content.
Current Usage: 1