v1.2.8
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.7
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.6
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.5
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.4
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.3
Resolve remaining audit findings: correct the delete-task example object type, align appendix request guidance with GraphQL-only POST, list workspace members and the full Klaviyo surface in the declared scope, and narrow activation wording with explicit exclusions
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
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.5
- Changed all API endpoints from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for simplified and unified access.
- Updated connection management instructions and examples to use the new api.maton.ai base URL.
- Clarified that all write operations require explicit user approval to enhance security guidance.
- Added a section about security and permissions, specifying access scope and user confirmation for sensitive operations.
- Removed LICENSE.txt file from the package.
v1.0.4
- Updated all examples and documentation references to use the new Klaviyo API revision date header: 2026-01-15 (was 2024-10-15).
- No functional changes detected; this update is documentation-only.
v1.0.3
- Added "clawdbot" metadata section, including an emoji and required environment variable details.
- No functional or documentation changes to skill usage or behavior.
v1.0.2
No user-facing changes detected in version 1.0.2 (no file changes found).
v1.0.1
- Updated SKILL.md examples to use concise Python scripts (via `python <<'EOF'` blocks and `urllib.request`) for all API interactions, replacing previous usage of the `requests` library.
- Added a note to the skill description about using the `api-gateway` skill for third-party apps other than Klaviyo.
- Improved clarity and consistency in code examples and headers.
- Adjusted API call documentation to a more streamlined style, including explicit HTTP methods and sample bash commands.
v1.0.0
Klaviyo Skill v1.0.0
- Initial release with Klaviyo API integration via managed OAuth.
- Provides endpoints for managing profiles, lists, segments, campaigns, flows, events, metrics, templates, catalogs, and webhooks.
- Includes detailed usage instructions, connection management, and API reference with code examples.
- Supports specifying Klaviyo connections and date-based API versioning.
- Requires network access and a valid Maton API key.