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
Processes AWS SES bounces and complaint notifications in CiviCRM. Uses native AWS bounce and complaint types instead of trying to match them to out of the box CiviCRM bounce types.
This provides a simple, modern theme for CiviCRM (based on the theme supplied in CiviCRM Admin Utilities for Wordpress).
Transforms a checkbox custom field into a grid for selecting availabilities in the week.
Displays a warning when there are pending mailings and gives an approximation of the start time. Also provides a shortcut to run the Scheduled Job manually.
Provides membership new and renewal statistics based on CiviCRM historical data (so you can also generate membership reports for previous years).
Converts the activity 'duration' field so that users can enter time in hours, instead of minutes.
This extension provides a generic way creating a message queue. This message queue could then be used
by other systems to retrieve changes from CiviCRM.
For example we can have a change message queue for submitting changes to an Outlook 365 address book. Every time a name of
a contact or its e-mail address is changed. A message is added to queue. Outlook 365 can then read message by message to process the
changes.
For developers it good to know that the queue used could be extended so that for example you can push the messages to RabbitMQ.
(RabbitMQ is an implementation of a message queue).
By default this extension comes with a CiviCRM Database Queue. This queue could be read with the API ChangeMessageQueue.get
by other systems to retrieve changes from CiviCRM.
For example we can have a change message queue for submitting changes to an Outlook 365 address book. Every time a name of
a contact or its e-mail address is changed. A message is added to queue. Outlook 365 can then read message by message to process the
changes.
For developers it good to know that the queue used could be extended so that for example you can push the messages to RabbitMQ.
(RabbitMQ is an implementation of a message queue).
By default this extension comes with a CiviCRM Database Queue. This queue could be read with the API ChangeMessageQueue.get
Define conditional rules of allowed field values based on the value selected in another field.
The Entity Construction Kit (ECK) provides a user interface and an API for creating and managing custom CiviCRM entities.
Blocks a configurable list of message templates emails (such as contribution receipts) and optionally records them as an activity.
Graph and list your last 6 months' CiviMail mailing performance statistics: deliveries, bounces, open/click rate, unsubscribes. View aggregate stats by day/week/month and optionally for a set of mailings (filtering on subject/mailing name).
Shows how your group has grown (or shrunk!) over time in a chart.
This extension 'fixes' some configuration options that may have been set in English during the initial installation before you decided to switch to another language (or before improving/updating the translation files).
This extension provides a lot of additional features to CiviCRM's events. In particular, you will be able to configure events in CiviCRM, display/use that information in other remote systems and submit registrations for those events back to CiviCRM.
The general idea is that your organization's staff can do all relevant event configurations in CiviCRM. CiviCRM will then make this information available via its REST API. The extension's API also has built in logic and actions to receive and update registrations.
Any external system can interact with the API and display event calendars, detailed event information, registration forms etc. (this could be a remote system or the CMS your CiviCRM runs on) and also submit information entered by your constituents back to CiviCRM.
All of this requires that you have or set up an external system to act as a frontend for your event listings, registration forms etc. In case you would like to build your system based on Drupal 8 you will most likely want to have a look and/or use the CiviRemote Drupal module which includes a lot of pre-built features (https://github.com/systopia/civiremote).
Note that this extension may be used alongside regular CiviCRM event registrations - you can choose whether you would like to use the remote features or not for each event.
The general idea is that your organization's staff can do all relevant event configurations in CiviCRM. CiviCRM will then make this information available via its REST API. The extension's API also has built in logic and actions to receive and update registrations.
Any external system can interact with the API and display event calendars, detailed event information, registration forms etc. (this could be a remote system or the CMS your CiviCRM runs on) and also submit information entered by your constituents back to CiviCRM.
All of this requires that you have or set up an external system to act as a frontend for your event listings, registration forms etc. In case you would like to build your system based on Drupal 8 you will most likely want to have a look and/or use the CiviRemote Drupal module which includes a lot of pre-built features (https://github.com/systopia/civiremote).
Note that this extension may be used alongside regular CiviCRM event registrations - you can choose whether you would like to use the remote features or not for each event.
