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.

Online Worldpay Payment Processor using API to generate tokens and authorise payment. Once installed just set-up the payment processor and this will be available for using in CiviCRM.
Current Usage: 7
This gives address block and current date tokens which will suppress blank lines in the address block and will give currnet date in mailing.
Current Usage: 7
Current Usage: 7
Provides some basic fields and functionality to assist with compliance for Canadian Anti-Spam Legislation.
Current Usage: 6
Provides SMS integration for RingCentral / Telus.
Current Usage: 6
This extension makes the checksum of the contact available for exporting.
Current Usage: 6
Provides form validation to prevent negative values from being entered in Text / Numeric Quantity fields in Price Sets.
Current Usage: 6
Extension introduces the InvoiceAddress Get API, getting several invoice addresses for a contact based on valid relationships.
Current Usage: 6
This very tiny extension enables validating a checksum (combination of contact_id and checksum) with an API.
Current Usage: 6
This extension add the nationality field to individuals. The option group is filled from a text file in the extension.
Current Usage: 6
Displays a contact’s Job Title with their current employer on the Contact Relationships tab.
Current Usage: 5
Add ability to use USAePay as a payment processor for Credit Cards and ACH/EFT.
Current Usage: 5
Current Usage: 5
This extension causes the "county" field on addresses to automatically be populated when an address is created or updated.
Current Usage: 5
Current Usage: 5