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.

Improved reports on mailing statistics
Current Usage: 1
Current Usage: 1
Current Usage: 1
Current Usage: 1
processor plugin but no longer recommended
Current Usage: 1
This extension adds two extra custom fields to the FinancialTrxn and a scheduled job "Stripe fill charge amount" which is used to fill those fields with data.

If you install this extension and take payments online the fields "Charge amount" and "Charge currency" will populate automatically.
They are normally the same as the amount / currency for the financial trxn.

## So why do I need this extension?

If you import the payments from another system and record them in the "payout" currency then this extension allows
you to record the charge amount and currency and use it in reports.

Make sure that imported FinancialTrxn records have the trxn_id = Stripe Charge ID.
Current Usage: 0
This is alpha. Use at own risk.

It's a sledgehammer to disable all payment processors and notify admins when it sees 5 consecutive failed transactions.
Current Usage: 0
This extension provides a simple mechanism for other extensions to include functional Markdown documents in their user interface. As a demonstration, while also providing a useful feature, this extension will embed the README.md of an extension on management pages; i.e. install, enable, disable, uninstall, update. This extension also demonstrates how to provide an alternative README for each action
Current Usage: 0
This extension allows an administrator to link a 'parent' civievent and a 'child' civievent. This pairing allows for an implementation of
"group" registration, by separating a payment in the 'parent' event for a group of participants, from the individual participants' registration process
in the 'child' event.
Current Usage: 0
This extension provides a set of Actions for CiviRules. These Actions enable integration to a process engine capable of executing long running business processes. Process "flows" may orchestrate both the internal CiviCRM APIs and also external APIs to loosely coupled systems.

The initial Alpha release will provide REST Actions to a Python container within the same docker environment (for security reasons). A fully functional Docker image for each CMS will be available for download from the repo, to make evaluation as simple as possible. For production environments, additional steps will be required to ensure security. You are strongly advised to seek help from a CiviCRM partner or cyber security expert before running this in a live environment.

Eventually we plan to provide some example Python flows, admin forms to view audit trails and manage Running, Completed, Faulted and Archived process instances.

For more help, ping us an email: support@encircle.co.uk.
Current Usage: 0
The sole purpose of this CiviCRM extension is to adjust a contribution activity's date if the receive date of the contribution has changed.

See also: https://issues.civicrm.org/jira/browse/CRM-17961
Current Usage: 0
A provider for the civirepresent, making use of http://represent.opennorth.ca/
Current Usage: 0
A provider agnostic storage and api for data relating to boundaries and representatives.
Current Usage: 0
This is work-in-progress towards getting CiviCRM able to run without a CMS.

We'd love help with this, so please join the standalone channel on Mattermost at chat.civicrm.org
Current Usage: 0