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
This Extensions aims to provide tools for a "European" interpretation of the "membership" concept. In the Anglo-Saxon countries (CiviCRM's native land) a membership is regarded as a service. If you don't pay anymore, you won't get the service - that's it. In a lot of other countries the conception is different: it's more like a indeterminate binding contract.
Cron Plus adds new features to the Schedule Jobs. It can be set the exactly date / time when a job must be executed
This extension integrates CiviCRM events with Zoom meetings. As people register for events in CiviCRM they will be added as registrants to the linked Zoom meeting. When canceled from within CiviCRM, they will be removed from the Zoom meeting.
Provides an API for providing a wide range of custom content and forms for external websites regardless what technology the external site uses.
Integrate Direct Debit payments using SmartDebit (https://www.smartdebit.co.uk/) with CiviCRM
Sync contact names, emails, groups, interest groups, tags with Mailchimp. Can be extended with custom code to send more data to Mailchimp. Designed to cope with big lists. Aims to give verbose overview of sync issues/status.
This extension extends ckeditor5, adding custom bundles with specific editor plugins and custom configurations
Payment Processor for Spain's Payment Gateway called Redsys.
This extension offers a modular and flexible alternative to CiviCRM's built-in deduplication system. It is designed to be
* fast and scalable: CiviCRM's built-in solution tends to run into problems with large data sets
* highly configurable: you have almost 60 modules to be used for your configuration, and there's new ones being added all the time.
* automated: once you have worked out a configuration that is rock solid, you can schedule it to be executed automatically on a regular basis
* offers automated conflict resolution modules
* fast and scalable: CiviCRM's built-in solution tends to run into problems with large data sets
* highly configurable: you have almost 60 modules to be used for your configuration, and there's new ones being added all the time.
* automated: once you have worked out a configuration that is rock solid, you can schedule it to be executed automatically on a regular basis
* offers automated conflict resolution modules
Data Explorer aims to provide an easy to use interface that can generate custom visualizations of CiviCRM data. The visualizations can then be added to the CiviCRM Dashboard, shared to external people without access to CiviCRM (using a secret key), or (eventually) as an HTML snippet that can be embedded in website content.
Define conditional rules of allowed field values based on the value selected in another field.
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.
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
Transforms a checkbox custom field into a grid for selecting availabilities in the week.