How was this made with CiviCRM?

Introduction #

This page contains videos that explain how the setup was done for the Fundraising videos. It assumes you are familiar with Drupal 9 and CiviCRM. If you are neither, the videos may be difficult to follow. The videos showing functionality from the user perspective may be your best option for now.

We do not claim to show you the best or only solution for the required functionality in the videos. There are likely to be plenty of other options available to achieve the same goals, and probably even better ones. The videos intend to give an impression how different requirements can be achieved through the use of CiviCRM and other tools.

Modules and Extensions #

CiviCRM Extensions

  • Form processor – to process data that come in through a donation form
  • Action provider – to enables actions the formprocessor
  • CiviSepa – to process a direct debit process along European Union SEPA regulation
  • Mosaico – to create and style the confirmation email

Drupal Modules

  • Drupal webform – to create the donation form
  • Webform CiviCRM – to integrate the donation form with CiviCRM data
  • CiviMcRestface – to enable communication between the website and CiviCRM in its own separate install.
  • Mollie – to enable webform integration with the Mollie payment processor

Fundraising with the Formprocessor #

General introduction of form processor #

After the data from the webform has been sent to CiviCRM it is being processed by the Form Processor you have created before. Before we have a look at this specific Form Processor, first a brief introduction of the Form Processor in general. 

The aim of the extension is to create a framework to enable swift development (increasingly without coding) of forms that are used on the public website and communicate with CiviCRM.

Next to the Form Processor you also need the Action Provider extension. The Action Provider provides predefined actions that can be used to do things in CiviCRM with the data entered on the form. For example: the form processor accepts the field ‘email’ and adds that to a contact card, the Action Provider can add an action that sends an email to that contact. 

Secondly the Action Provider offers retrieval methods to provide default data to the form, in other words: the form will be prefilled with data already known in CiviCRM. 

Formprocessor Inputs #

Formprocessor Actions #

Formprocessor Existing Data #

Fundraising SEPA Mandates #

The video introduces how to use SEPA Mandates to direct debit the money that was promised to your organisation through the SEPA mandates.

Mailing Templates #

The video shows how to set up different mailing templates that confirm to a donor what was donated and what will happen next.

Activity Type #

The video shows how to define and store the constituent’s approval with your privacy policy so that you can prove GDPR’s requirements have been met by your organisation. In this use case, that is done with an activity type that is triggered by the submission of the donation form.

Webform #

The video show how the donation form was set up to accomodate the different payment options.

The video shows how the call to action “Donate Now” is linked to the webform with prefilled donor data.