← Back to Skills Marketplace
byungkyu

constant-contact

by byungkyu · GitHub ↗ · v1.2.1 · MIT-0
cross-platform ✓ Security Clean
7492
Downloads
3
Stars
0
Active Installs
10
Versions
Install in OpenClaw
/install constant-contact
Description
Constant Contact API integration with managed OAuth. This is a write-capable integration — it can read, create, update, delete, and bulk-modify contacts, email campaigns, contact lists, tags, custom fields, segments, and marketing analytics. Use this skill when users want to interact with Constant Contact marketing data. All write operations (POST, PUT, DELETE, bulk actions, campaign sending/scheduling) require explicit user approval with specific resource identifiers before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. The endpoints documented here are the intended surface, not a technical limit — the `maton api` passthrough can reach others the connection permits. Default to read and list calls, and confirm every write or new connection with the user.
Usage Guidance
Install this only if you intend to let an agent administer a Constant Contact account through Maton. Review write requests carefully, especially campaign sending, scheduling, imports, exports, and bulk contact changes, and prefer OAuth over long-lived API keys.
Capability Assessment
Credentials
Network access, Bash execution for CLI/API calls, and Constant Contact account access are necessary for the integration; no bundled executable or unrelated local system access was found.
Install Mechanism
Installation relies on the external Maton CLI via npm or Homebrew, with an SDK/raw HTTP fallback; this is disclosed and aligned with the integration purpose.
Instruction Scope
The instructions repeatedly require read/list checks first, explicit user approval with resource identifiers before writes, extra confirmation for campaign sending and bulk changes, and treating API-returned content as untrusted data.
Persistence & Privilege
OAuth/API credentials are stored by Maton in normal credential stores, and the skill explicitly warns not to print, extract, persist, or broadly expose secrets; no background worker or hidden persistence is instructed.
Purpose & Capability
The stated purpose is managing Constant Contact marketing data through Maton, and the documented read, write, bulk, reporting, and campaign operations match that purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install constant-contact
  3. After installation, invoke the skill by name or use /constant-contact
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.6
- Removed the file: skill-card.md. - No code or feature changes; documentation only.
v1.0.5
- Updated API hostname from gateway.maton.ai/ctrl.maton.ai to api.maton.ai throughout documentation and examples. - Clarified that this integration is write-capable (supports create, update, delete, and bulk-modify operations) and includes segments in its scope. - Strongly emphasized user confirmation requirements for all write, bulk, and high-impact operations, with new step-by-step safety guidelines. - Improved security documentation, including explanations about connection management, resource scoping, and the need to use the correct Maton-Connection header for multi-account setups. - Removed LICENSE.txt file.
v1.0.4
- Expanded skill to include additional resources: tags, custom fields, segments, and bulk operations. - Improved and clarified documentation for query parameters, example usage, and response samples across all endpoints. - Added missing endpoints and examples for account management, sender email management, and subresource inclusion. - Updated instructions to specify required fields (such as `create_source` when creating contacts). - Refined skill description for greater accuracy and detail regarding supported features.
v1.0.3
- Added a new clawdbot metadata section specifying an emoji and required environment variable (MATON_API_KEY). - No changes to skill features or user-facing functionality; documentation metadata only.
v1.0.2
- Documentation in SKILL.md reformatted or rewritten. - No functional changes; only documentation was updated.
v1.0.1
No changes detected in this version. - Version number updated from 1.0 to 1.0.1. - No file changes present between this and the previous version.
v1.0.0
Constant Contact skill v1.0.0 – Initial release - Adds integration with Constant Contact API for managing contacts, email campaigns, lists, segments, tags, and custom fields. - Supports managed OAuth connections via Maton platform with simple connection management. - Provides endpoints for creating, updating, deleting, and listing contacts, lists, and tags. - Includes API references and Python code samples for quick start and connection management. - Requires network access and a valid Maton API key.
Metadata
Slug constant-contact
Version 1.2.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 10
Frequently Asked Questions

What is constant-contact?

Constant Contact API integration with managed OAuth. This is a write-capable integration — it can read, create, update, delete, and bulk-modify contacts, email campaigns, contact lists, tags, custom fields, segments, and marketing analytics. Use this skill when users want to interact with Constant Contact marketing data. All write operations (POST, PUT, DELETE, bulk actions, campaign sending/scheduling) require explicit user approval with specific resource identifiers before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. The endpoints documented here are the intended surface, not a technical limit — the `maton api` passthrough can reach others the connection permits. Default to read and list calls, and confirm every write or new connection with the user. It is an AI Agent Skill for Claude Code / OpenClaw, with 7492 downloads so far.

How do I install constant-contact?

Run "/install constant-contact" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is constant-contact free?

Yes, constant-contact is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does constant-contact support?

constant-contact is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created constant-contact?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.1.

💬 Comments