Skip to content

Document read-only Mailchimp journey audits - #547

Draft
harrisboatworks wants to merge 1 commit into
browser-use:mainfrom
harrisboatworks:agent/mailchimp-automation-audit-domain-skill
Draft

Document read-only Mailchimp journey audits#547
harrisboatworks wants to merge 1 commit into
browser-use:mainfrom
harrisboatworks:agent/mailchimp-automation-audit-domain-skill

Conversation

@harrisboatworks

@harrisboatworks harrisboatworks commented Jul 21, 2026

Copy link
Copy Markdown

Summary

  • document read-only Mailchimp automation-flow discovery endpoints
  • show how to reconstruct tag triggers, delays, and email campaign steps
  • cover content, archive-render, report, bounce, merge-field, and click-scanner checks
  • define a no-send safety boundary for automation audits

Why

Mailchimp exposes useful journey and step reads that are not obvious from the public API reference. A read-only audit can otherwise drift into dangerous trigger, test-send, or contact-mutation actions. The new domain note provides a bounded workflow that produces live evidence without enrolling or messaging anyone.

Impact

Documentation only. No runtime behaviour changes.

Validation

  • git diff --check
  • confirmed the document contains no account IDs, contact data, credentials, or task-specific details

Summary by cubic

Add a read-only Mailchimp automation audit guide that uses GET-only endpoints to inspect journeys and campaigns without enrolling or sending. It covers reconstructing triggers/delays/steps, safe content/report checks, and a no-send safety boundary; no runtime changes.

  • New Features
    • Documented GET endpoints for journeys, steps, campaigns, reports, and segments.
    • Steps to rebuild the journey graph and timing from step data.
    • Guidance for content verification via campaign content and archive URLs.
    • Do-not-call list of write endpoints to keep audits read-only.

Written for commit e2cc89c. Summary will update on new commits.

Review in cubic

@Kastan97 Kastan97 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ollie (CTO) Review: APPROVED

What this does: Documents read-only Mailchimp automation-flow discovery — tag triggers, delays, email campaign steps, archive render, reports, bounces, merge fields. 83 lines of documentation with a clear no-send safety boundary.

Assessment: Clean documentation. No code changes. The no-send safety boundary is exactly the kind of guardrail that prevents agents from accidentally enrolling contacts during "read-only" audits. No credentials or customer data included.

Good to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants