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 extension extends ckeditor5, adding custom bundles with specific editor plugins and custom configurations
Provides the latest version of the API (Application Programming Interface) for CiviCRM. Api4 has been moved to CiviCRM core as of CiviCRM 5.19. This extension is now archived and will receive no further updates.
This extension deletes mailings that are unscheduled after a period of days specified.
Adds image resizing capability for contact and custom field images. It handles all types of images and will put the images into the directory.
If you theme is already based on boostrap, civisualize works fine out of the box.
If you don't, enable this extension that will add the missing stylesheets so the default datavisualisations look better
If you don't, enable this extension that will add the missing stylesheets so the default datavisualisations look better
A simple extension to provide a set of "Opt-in" communication preferences for use on forms (instead of the built-in "Opt-Out" fields).
Provides a page with information about your installation and server that can be helpful for diagnosing problems.
Provides an API for providing a wide range of custom content and forms for external websites regardless what technology the external site uses.
This extension saves old emailaddresses, phone numbers and addresses for contacts in a specific tab (custom group).
When mailings are archived, compile stats and tidy up the database details.
Adds Open Graph Protocol (OGP) meta tags to some CiviCRM pages, which provides a better experience when sharing pages on social media.
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
