aiviemarketing/mautic-recaptcha

This plugin brings reCAPTCHA integration to Aivie and mautic.

Maintainers

Details

github.com/aiviemarketing/aivie-recaptcha

Source

Installs: 0

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 0

Forks: 37

Type:mautic-plugin

pkg:composer/aiviemarketing/mautic-recaptcha

6.0.6 2025-10-31 16:52 UTC

Requires

GPL-3.0-only 0c7cd4fa8b93dfb7899e92945388c2ac6c01540f

  • Adrian Schimpf <dev.woop@aivie.ch>

pluginintegrationMauticaivie

This package is auto-updated.

Last update: 2026-02-16 12:05:35 UTC

README

license Packagist mautic

This Plugin brings reCAPTCHA integration to mautic 3 and 4.

Installation

mautic 3 & 4

Supports reCaptcha v3.

Add this code to the plugins/ directory of your mautic installation.

Execute composer require google/cloud-recaptcha-enterprise in the main directory of the mautic installation.

@todo needs to be moved to the plugins composer.json, when we support composer v2. So we can install the https://github.com/mautic/composer-plugin.

Configuration

Navigate to the Plugins page and click "Install/Upgrade Plugins". You should now see a "reCAPTCHA" plugin. Open it to enable it.

Set the following ENV variables on your server:

  • GOOGLE_CLOUD_PROJECT
  • GC_RECAPTCHA_SITE_KEY
  • GOOGLE_APPLICATION_CREDENTIALS

The plugin relies on Google reCAPTCHA Enterprise. For it to work it needs Google Application Default Credentials.

Usage in a Mautic Form

Add "reCAPTCHA" field to the Form and save changes. mautic form

Score validation

reCAPTCHA v3 will rank traffic and interactions based on a score of 0.0 to 1.0, with a 1.0 being a good interaction and scores closer to 0.0 indicating a good likelihood that the traffic was generated by bots

score validation

Release Workflow

This project uses GitHub Actions for automated releases. To push to protected branches (like 6.x), you need to configure one of the following:

Option 1: Personal Access Token (Recommended)

  1. Create a Personal Access Token (PAT) with the following permissions:
    • Classic PAT: repo scope (full control of private repositories)
    • Fine-grained PAT:
      • Contents: Read and write
      • Metadata: Read-only (automatically included)
      • Releases: Write (if creating releases)
  2. Add it as a repository secret named RELEASE_TOKEN in Settings → Secrets and variables → Actions
  3. The workflow will use this token to bypass branch protection rules and push commits/tags to the protected branch

Option 2: Configure Branch Protection

  1. Go to Settings → Branches → Branch protection rules for 6.x
  2. Enable "Allow specified actors to bypass required pull requests"
  3. Add github-actions[bot] to the bypass list

Based on

https://github.com/KonstantinCodes/mautic-recaptcha

Contributers

Aivie