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.

Creates a token (contributions.itemized) that shows a contact's contributions within the past year.
Current Usage: 5
The functional requirement for this extension is that the funding customer (https://www.domusmedica.be/) has a lot of situations where an individual becomes a member or registers for an event but wants his/her company to pay for this. Partially this is possible in core CiviCRM using soft credits (for memberships) but it is somewhat confusing. The user does not see the actual payer of the membership on the membership screens, and the invoice does not show the name of the actual member.

This extension allows another contact than the member to pay for a membership and another contact then the participant to pay for an event registration. The extension will show the actual contact paying in the membership and participant screens and will also add the name of the participant or member on the invoice.
Current Usage: 4
The focus of this extension is to facilitate the initial import and continuous update of the following data:

Committees - e.g. parliaments
Contacts, along with address, email, phone and website - e.g. members of parliament
Committee memberships
For that will find the importer in Contact menu with the "Import/Synchronise Committees" item. There you'll have to select:

an importer module suitable for your data source, e.g. the German Kürschner list.
a syncer module that defines the way the data is represented in your CiviCRM instance.
If the existing modules don't really work for you, you can contact us for new/adjusted modules at info@systopia.de.
Current Usage: 4
Use Nextcloud to store your CiviCRM files, or use CiviCRM to find your Nextcloud files. Creates for every contact, case or expense a Nextcloud folder, and adds a button on the interface, so you can access this folder.
Current Usage: 4
Example implementation of `hook_civicrm_alterPaymentProcessorParams()`

Includes the following examples:
- For Drupal9 Webform and Stripe Checkout: Restrict the available payment method types depending on the webform that is used.
Current Usage: 4
On forms that allow the creation of a user, always use the email as the username (do not let users select their own username).
Current Usage: 4
Triggers a zap configured on zapier.com from CiviCRM
Current Usage: 4
Prevent emailing of reports that contain no rows in the output.
Current Usage: 4
Combines the flexibility of Smart Groups with the utility of Static Groups.
Current Usage: 4
Allow participants to edit a pending event registration, and also allows partial payments on a public form.
Current Usage: 4
Allows donors to set the financial type of a donation from a drop-down menu on a contribution page.
Current Usage: 4
Adds case field to activity creation form.
Current Usage: 4
This extension provides a search that shows financial aging of overdue contributions such as recurring contributions and pledge payments.
Current Usage: 4
Integrates CiviCRM with Sharepoint
Current Usage: 4