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
Clone any existing contribution to a new contribution, optionally omitting some properties, and optionally changing the value of some properties.
Provides some basic fields and functionality to assist with compliance for Canadian Anti-Spam Legislation.
Provides SMS integration for RingCentral / Telus.
This extension makes the checksum of the contact available for exporting.
This extension allows you to specify specific defaults for API fields for a contact.
This very tiny extension enables validating a checksum (combination of contact_id and checksum) with an API.
This extension causes the "county" field on addresses to automatically be populated when an address is created or updated.
Integrates SparkPost to CiviCRM, so email can be sent out over the SparkPost service and bounces can be processed in CiviCRM.
This extension add the nationality field to individuals. The option group is filled from a text file in the extension.
Provides a way to categorise contacts by a set of priority groupings; a contact only ever has one category, which is the most important one that applies.
How categories are defined and their priority will depend on your organisation's needs, though a standard scheme(s) is(are) provided to get you started. For example, you might have a way to identify Major Donors, and decide that if someone is a Major Donor, this is the most important category that would apply to them; they may also be One off donors, or Activists or Subscribers or such, but it's helpful to your organisation to prioritise the Major Donor category.
Please see the project repository for fuller examples.
How categories are defined and their priority will depend on your organisation's needs, though a standard scheme(s) is(are) provided to get you started. For example, you might have a way to identify Major Donors, and decide that if someone is a Major Donor, this is the most important category that would apply to them; they may also be One off donors, or Activists or Subscribers or such, but it's helpful to your organisation to prioritise the Major Donor category.
Please see the project repository for fuller examples.
Extension to print the Member Book according to the Italian law for Associations an Co-operatives.
The focus of this extension is to facilitate the initial import and continuous update of the following data:
Committees - e.g. parliaments
Contacts, along with address, email, phone and website - e.g. members of parliament
Committee memberships
For that will find the importer in Contact menu with the "Import/Synchronise Committees" item. There you'll have to select:
an importer module suitable for your data source, e.g. the German Kürschner list.
a syncer module that defines the way the data is represented in your CiviCRM instance.
If the existing modules don't really work for you, you can contact us for new/adjusted modules at info@systopia.de.
Committees - e.g. parliaments
Contacts, along with address, email, phone and website - e.g. members of parliament
Committee memberships
For that will find the importer in Contact menu with the "Import/Synchronise Committees" item. There you'll have to select:
an importer module suitable for your data source, e.g. the German Kürschner list.
a syncer module that defines the way the data is represented in your CiviCRM instance.
If the existing modules don't really work for you, you can contact us for new/adjusted modules at info@systopia.de.
