Mautic Control

Controlled Mautic CRM operations for OpenClaw, with guarded API, webhook, console, and workspace tools.

Install

openclaw plugins install clawhub:@completetech/openclaw-mautic-plugin

Mautic Control for OpenClaw

Controlled Mautic CRM operations from OpenClaw: typed API tools, webhook discovery, conservative console maintenance, and guarded workspace staging.

Mautic Control overview

PackageRuntimeMautic TargetOpenClaw
@completetech/openclaw-mautic-pluginmautic-controlMautic 7.x, tested with 7.1.1>=2026.5.22

Install

openclaw plugins install clawhub:@completetech/openclaw-mautic-plugin

After installation, configure the non-secret connection settings in OpenClaw and provide Mautic credentials through environment variables or your platform secret store.

What You Can Do

WorkflowToolsDefault Safety
Check Mautic reachability and policymautic_statusRead-only status check
Work with Mautic API resourcesmautic_request, mautic_entityCredentials required, API paths only
Discover webhook trigger namesmautic_webhook_triggersNo credentials required
Run maintenance commandsmautic_consoleOptional bridge, allowlisted commands only
Stage import/export filesmautic_workspace_fileOff by default, bounded to one workspace root

Good Fits

  • Inspect Mautic health before generating CRM workflow documents.
  • Read or update contacts, companies, segments, campaigns, emails, forms, webhooks, and related API entities through policy-gated calls.
  • Confirm available webhook events before designing automations.
  • Run narrow Mautic maintenance or automation jobs from a private console bridge when an operator enables them.
  • Stage CSV, JSON, or Markdown files in a dedicated workspace directory.

Conservative by Default

The plugin starts narrow. API access requires credentials, maintenance commands are off, automation jobs are off, and workspace read/write are off until explicitly enabled.

CapabilityDefaultEnable Only When
Mautic APIAvailable after credentialsThe agent is allowed to operate this Mautic instance
Console bridgeStatus-onlyA trusted operator needs allowlisted console commands
Automation jobsOffCampaign, segment, or webhook jobs are intentional
Workspace read/writeOffA dedicated staging directory is configured
Filesystem boundaryAlways onEvery path must remain under allowedWorkspaceRoot

Production Setup

StepSettingGuidance
Connect MauticbaseUrlUse the internal URL OpenClaw should call. Use HTTPS for hosted or routed deployments.
Add API credentialsMAUTIC_API_USERNAME, MAUTIC_API_PASSWORDStore secrets outside plugin UI and source control.
Choose API routingdefaultApiVersionUse legacy for /api or v2 for /api/v2 where available.
Keep console privateconsoleUrl, MAUTIC_CONSOLE_TOKENDeploy the bridge only on a private network and only if console commands are needed.
Guard file stagingworkspaceRoot, allowedWorkspaceRootUse a dedicated staging directory, not a home directory or secrets path.
Limit agent exposureOpenClaw profilesPrefer explicit tool allowlists for agents that process untrusted input.

Secure Transport

Authenticated tools send Mautic API credentials with each request. Use https:// for production, hosted, routed, or cross-host deployments.

Plain http:// is acceptable only for a trusted loopback address or private container network such as http://mautic_web. The plugin reports a transport warning for non-HTTPS baseUrl values, and authenticated API tools refuse to send credentials to routable plain-HTTP hosts.

Tools

ToolWhat It DoesRequires
mautic_statusChecks dashboard reachability, API auth, resolved config, transport policy, command policy, and workspace policy.API credentials for auth check
mautic_requestSends authenticated requests to Mautic paths under /api or /api/v2.API credentials
mautic_entityLists, reads, creates, updates, and deletes supported Mautic resources.API credentials
mautic_webhook_triggersLists valid Mautic webhook trigger events.Plugin only
mautic_consoleRuns allowlisted Mautic console commands through the private bridge.Console bridge and token
mautic_workspace_fileLists, reads, writes, or deletes files under a guarded workspace root.Workspace toggles

Required Secrets

Never store these values in the plugin UI, README, or source control.

SecretPurpose
MAUTIC_API_USERNAMEMautic API username. Use least-privilege credentials.
MAUTIC_API_PASSWORDMautic API password.
MAUTIC_CONSOLE_TOKENShared token for the optional console bridge. Required only for mautic_console.

OAuth2 is preferred for external production integrations where available. The local verification stack uses Basic auth only for loopback automation.

Plugin Settings

These settings are non-secret and can be configured in OpenClaw.

SettingDefaultProduction Guidance
baseUrlhttp://mautic_webInternal Mautic URL reachable by OpenClaw.
consoleUrlhttp://mautic_console:8099/consoleInternal bridge URL. Leave unused if console commands are not needed.
workspaceRoot/workspace/mauticDedicated staging directory for file operations.
allowedWorkspaceRoot/workspace/mauticHard boundary for file access. Do not use a home directory or secrets path.
defaultApiVersionlegacyUse legacy or v2 based on your Mautic routes.
requestTimeoutSeconds60HTTP timeout. Range: 5 to 600 seconds.
allowMaintenanceCommandsfalseEnables cache/plugin maintenance commands.
allowAutomationJobCommandsfalseEnables campaign, segment, and webhook job commands.
allowWorkspaceReadfalseEnables list/read under workspaceRoot.
allowWorkspaceWritefalseEnables write/delete under workspaceRoot.

Environment fallbacks are supported for non-secret settings:

MAUTIC_BASE_URL
MAUTIC_CONSOLE_URL
MAUTIC_WORKSPACE_DIR
MAUTIC_ALLOWED_WORKSPACE_ROOT
MAUTIC_DEFAULT_API_VERSION
MAUTIC_REQUEST_TIMEOUT_SECONDS
MAUTIC_ALLOW_MAINTENANCE_COMMANDS
MAUTIC_ALLOW_AUTOMATION_JOB_COMMANDS
MAUTIC_ALLOW_WORKSPACE_READ
MAUTIC_ALLOW_WORKSPACE_WRITE

Console Bridge

The console bridge is optional. It is needed only for mautic_console; API, entity, webhook, status, and workspace tools can run without it.

RequirementProduction Guidance
Bridge fileDeploy mautic/console-bridge.php only when console commands are required.
NetworkKeep the bridge on a private network reachable by OpenClaw.
AuthenticationProtect every request with MAUTIC_CONSOLE_TOKEN.
Public accessDo not expose the bridge directly to the public internet.
Command scopeKeep execution limited to the plugin and bridge allowlists.

Local Docker Stack

The companion Docker stack uses explicit local settings:

baseUrl=http://mautic_web
consoleUrl=http://mautic_console:8099/console
workspaceRoot=/workspace/mautic
allowedWorkspaceRoot=/workspace/mautic
defaultApiVersion=legacy
requestTimeoutSeconds=60
allowMaintenanceCommands=true
allowAutomationJobCommands=false
allowWorkspaceRead=true
allowWorkspaceWrite=true

These are local-stack defaults, not production defaults. Do not expose the local stack's loopback credentials or Basic auth settings publicly.

Compatibility

This release was verified against Mautic Community 7.1.1, the latest GitHub release checked on 2026-05-26. Mautic's own release page lists Mautic 7 as the actively supported series.

ComponentSupported Target
OpenClaw Gateway2026.5.22 or newer
MauticMautic 7.x, tested with 7.1.1
Mautic APILegacy /api routes and /api/v2 where available
Console bridgeOptional, private network only
Workspace file accessOptional, dedicated staging directory only

Validate against your exact Mautic instance before broad rollout, especially if custom plugins, nonstandard API routing, or reverse proxies are involved.

Verify

npm run lint
npm test
npm run package:check
npm run readiness:check

Live stack checks:

npm run live:smoke
node scripts/audit.mjs
node scripts/audit.mjs --live
docker compose exec -T openclaw sh -lc 'openclaw security audit --deep --json'

Publish

The package is published on ClawHub as @completetech/openclaw-mautic-plugin.

Releases are published as a ClawPack npm-pack artifact. Trusted publishing uses GitHub Actions OIDC; no long-lived ClawHub token is stored in repository secrets.

For a future release:

npm run readiness:check
rm -rf clawpack
mkdir -p clawpack
npm exec --yes clawhub -- package pack . --pack-destination clawpack --json
gh workflow run clawhub-publish.yml --ref main

Optional publish environment variables are CLAWHUB_OWNER, CLAWHUB_CHANGELOG, CLAWHUB_SOURCE_REPO, CLAWHUB_SOURCE_REF, CLAWHUB_TAGS, CLAWHUB_CLAWSCAN_NOTE, and CLAWHUB_ALLOW_PRIVATE_SOURCE.

See docs/TRUSTED_PUBLISHING.md for the trusted publisher workflow and verification commands.

Limits

  • Pre-1.0 release: validate in the target environment before broad rollout.
  • mautic_console cannot run arbitrary shell or Mautic console commands.
  • mautic_workspace_file is for guarded staging workflows, not full filesystem access.
  • ClawHub scan status may be pending immediately after a new release is published.