Document read-only Mailchimp journey audits - #547
Draft
harrisboatworks wants to merge 1 commit into
Draft
Conversation
Kastan97
reviewed
Jul 28, 2026
Kastan97
left a comment
There was a problem hiding this comment.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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 --checkSummary 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.
Written for commit e2cc89c. Summary will update on new commits.