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.
Further resources:
This listing displays CiviCRM extensions that work on all Content Management Systems (CMS). You can also browse directories of plugins or modules that are made specifically for Backdrop, Drupal, Joomla and WordPress. View newest extensions.
This extension adds address verification to anyform. Once a user starts to type in a street address they will be presented with 10 standardized address options from smartystreets. This list will filter the more they type. Once they select an address it will check if the address is verified. In order to use this you need an account at smartystreets.com which is free for non-profits.
Allows a contact's Do Not Contact preferences to be marked with dates when that preference will expire.
This is a CiviCRM extension that automatically creates a new Activity, Credit Card Expired based on the Credit Card Expiry Date for a stored credit card token.
The Activity Date for the Activity is set to the 1st day of the month after the Credit Card Expiry Date.
The Credit Card Expired, Activity can then be used to set up Scheduled Reminders to notify the Contact that their credit card is about to expire or has expired.
The Activity Date for the Activity is set to the 1st day of the month after the Credit Card Expiry Date.
The Credit Card Expired, Activity can then be used to set up Scheduled Reminders to notify the Contact that their credit card is about to expire or has expired.
Embed forms in any remote website, providing inputs to a Form Processor. Invisible anti-spam measure included. This is an "Inlay" and therefore requires that extension, see https://lab.civicrm.org/extensions/inlay
This is a CiviCRM extension that enables a single Contribution page to have options for multiple recurring Contributions, each with different recurring payment schedules (frequency). Such that you can provide donation frequency options or membership renewal of daily, weekly, monthly or yearly with varying intervals. This is implemented by adding two new fields to each Priceset Option within a Priceset:
1. Recurring Contribution Unit: Which determines if this option should generate a recurring Contribution. Options: no recurrence, day, week, month, year
2. Recurring Contribution Interval: Which determines the interval of the recurrence. Integer field.
When the Contribution page is processed, each Priceset Option with a defined Recurring Contribution Unit will result in the creation of a recurring Contribution according to the options selected.
1. Recurring Contribution Unit: Which determines if this option should generate a recurring Contribution. Options: no recurrence, day, week, month, year
2. Recurring Contribution Interval: Which determines the interval of the recurrence. Integer field.
When the Contribution page is processed, each Priceset Option with a defined Recurring Contribution Unit will result in the creation of a recurring Contribution according to the options selected.
CiviContact is a mobile application for Android and iOS which enables users to manage Contacts, Groups, Activities (and more!) when connected to a CiviCRM integrated website. Find out more about about CiviContact at https://civicontact.com.au
This is a CiviCRM extension required for the CiviContact mobile application for iOS and Android. Find out more about about CiviContact at https://civicontact.com.au
Allows Admins to set up a 'main/parent' event with some 'related/child' events, such that registering for the 'main/parent' event also registers the participant to all the 'related/child' events.
Set up involves specifying the Event ID of the 'main/parent' event in the custom field on the 'related/child' events.
Such registrations can then be overridden if necessary by admin, eg if a user signs up for an event series E1, E2, E3 etc, but are then unable to attend E3, they can be instead registered for F3 for example
Set up involves specifying the Event ID of the 'main/parent' event in the custom field on the 'related/child' events.
Such registrations can then be overridden if necessary by admin, eg if a user signs up for an event series E1, E2, E3 etc, but are then unable to attend E3, they can be instead registered for F3 for example
