HubSpot Icon

HubSpot

Statamic HubSpot Documentation

Table of Contents

Overview

Statamic HubSpot is an addon that connects your Statamic forms to HubSpot. When a form is submitted, the addon automatically creates or updates a contact in HubSpot and maps custom contact properties.

Editions

The addon is available in two editions:

Lite (default):

  • Connect any Statamic form to HubSpot
  • Automatic contact creation and updating
  • Map form fields to HubSpot contact properties
  • GDPR consent field support

Pro (requires Statamic Pro):

  • Everything in Lite
  • Per-site HubSpot configurations
  • Site-specific routing
  • Localized form configurations per locale

Requirements

  • PHP 8.3+
  • Laravel 12.0+
  • Statamic 6.0+
  • A HubSpot account with a Private App access token

For Statamic 4.x/5.x support, use version 1.x of this addon.

Installation

Via Statamic Control Panel

  1. Go to Tools > Addons
  2. Search for "HubSpot"
  3. Click Install

Via Composer

composer require lwekuiper/statamic-hubspot

The addon auto-registers via Laravel's package discovery. The configuration file is published automatically on install.

Configuration

API Credentials

Add your HubSpot access token to your .env file:

HUBSPOT_ACCESS_TOKEN=your-private-app-token-here

You can create a Private App in your HubSpot account under Settings > Integrations > Private Apps. The access token requires the following scopes:

  • crm.objects.contacts.read
  • crm.objects.contacts.write
  • crm.schemas.contacts.read

Configuration File

The configuration file is published to config/statamic/hubspot.php during installation. You can also publish it manually:

php artisan vendor:publish --tag=statamic-hubspot-config

The config file contains:

return [
    'access_token' => env('HUBSPOT_ACCESS_TOKEN'),
];

Enabling Pro Edition

To use multi-site features, enable the Pro edition in config/statamic/editions.php:

'addons' => [
    'lwekuiper/statamic-hubspot' => 'pro',
],

Usage

Step 1: Create a Form

Create a Statamic form with the fields you want to send to HubSpot. At minimum, you need an email field. Example blueprint:

title: Newsletter Signup
fields:
  - handle: email
    field:
      type: email
      display: Email Address
      validate: required|email
  - handle: first_name
    field:
      type: text
      display: First Name
  - handle: last_name
    field:
      type: text
      display: Last Name
  - handle: consent
    field:
      type: toggle
      display: I agree to receive marketing emails
      validate: required|accepted

Step 2: Configure the Integration

  1. Navigate to Tools > HubSpot in the control panel
  2. Click on the form you want to configure
  3. Fill in the configuration:
    • Email Field (required): Select the form field containing the contact's email address
    • Consent Field (optional): Select a boolean/toggle field for GDPR consent
    • Contact Properties (optional): Map form fields to HubSpot contact properties

Step 3: Use the Form in Templates

Use the form in your Antlers templates as usual. No special markup is needed for the HubSpot integration:

{{ form:newsletter_signup }}
    {{ if errors }}
        <div class="alert alert-danger">
            {{ errors }}
                <p>{{ value }}</p>
            {{ /errors }}
        </div>
    {{ /if }}
 
    {{ if success }}
        <p>Thank you for subscribing!</p>
    {{ /if }}
 
    <div>
        <label for="email">Email Address</label>
        <input type="email" name="email" id="email" required>
    </div>
 
    <div>
        <label for="first_name">First Name</label>
        <input type="text" name="first_name" id="first_name">
    </div>
 
    <div>
        <label>
            <input type="checkbox" name="consent" value="1" required>
            I agree to receive marketing emails
        </label>
    </div>
 
    <button type="submit">Subscribe</button>
{{ /form:newsletter_signup }}

Field Mapping

Use contact properties to map your Statamic form fields to HubSpot contact properties. Both standard properties (firstname, lastname, phone) and custom properties from your HubSpot account are available in the contact properties dropdown.

Multi-select fields (checkboxes, multi-select, etc.) are automatically converted to semicolon-separated strings, matching HubSpot's expected format. Fields with empty or null values are filtered out and not sent to HubSpot.

The consent field provides GDPR compliance by requiring explicit opt-in before sending data to HubSpot.

How it works:

  • If a consent field is configured, the submission is only sent to HubSpot when the field has a truthy value
  • If consent is not given, the Statamic form submission is still saved, but no data is sent to HubSpot
  • If no consent field is configured, all submissions are processed

Multi-Site Support (Pro)

With the Pro edition and Statamic's multi-site enabled, you can configure different HubSpot integrations per site. Each site gets its own form configuration with separate contact property mappings.

The control panel shows a site selector on both the listing and edit pages. When a form is submitted, the addon automatically detects which site it belongs to.

Permissions

Access to the HubSpot control panel section requires one of:

  • Super admin status
  • The configure forms permission

The navigation item is visible to users who can index forms.

Troubleshooting

Submissions not appearing in HubSpot

  1. Check API credentials: Verify HUBSPOT_ACCESS_TOKEN in your .env file
  2. Check the form configuration: Navigate to Tools > HubSpot and verify the form has a configuration with the email field set
  3. Check consent: If a consent field is configured, ensure it resolves to a truthy value in the submission
  4. Check logs: Look for error messages in storage/logs/laravel.log

Configuration not saving

  1. Ensure the resources/hubspot/ directory exists and is writable
  2. Clear the Stache cache: php please stache:clear

Contact properties not loading in the control panel

  1. Verify your access token is correct
  2. Check that your Private App has the required scopes
  3. Check logs for API error messages

Multi-site not working

  1. Confirm the Pro edition is enabled in config/statamic/editions.php
  2. Confirm Statamic Pro is installed and multi-site is configured
  3. Verify site-specific configuration files exist in the correct locale subdirectories

Debug logging

Enable detailed logging by setting LOG_LEVEL=debug in your .env file. API errors are always logged regardless of log level.