Mailchimp Workflow Automator

Mailchimp Workflow Automator

Quick Reference

Why This Skill Exists

We need this skill because Mailchimp workflows degrade when auth, schema, and side-effect handling drift when integrations are run ad hoc. This specific skill turns Mailchimp Workflow Automator into a deterministic, auth-checked workflow for executes repeatable multi-step workflows using mailchimp..

Trigger Checklist

• The task explicitly requires Mailchimp Workflow Automator rather than generic brainstorming.
• The provider tenant, workspace, or environment is known before execution begins.
• Credential reuse has been checked before asking for new secrets.
• Success criteria, side effects, and handoff owner are clear.
• If the run mutates provider state, the relevant approval gates are available.

Auth & Access Profile

Inputs (contract)

Outputs (contract)

Step-by-Step Implementation Guide

1. Define the workflow graph, mutating boundaries, and approval requirements for Mailchimp Workflow Automator, then checkpoint where Mailchimp state can be replayed safely.
2. Validate credential reuse and trigger context before any step begins, with a focus on which branches require explicit human sign-off.
3. Implement executes repeatable multi-step workflows using mailchimp. as a deterministic sequence of step contracts, approvals, and checkpoint writes.
4. Capture step-level artifacts, side-effect evidence, and pending approvals in the workflow runbook so every branch remains auditable.
5. Run simulation and regression suites that cover missing approvals, missing checkpoints, and contract drift at each step boundary.
6. Publish the workflow runbook with completion state, pending approvals, and the exact checkpoint required for any safe replay.

Operational Runbook

Preflight

• Validate the trigger context, approval policy, and downstream side effects for the workflow.
• Confirm which steps are replay-safe and where checkpoints must be stored.

Execution

• Run one step at a time with checkpointing and approval gates between mutating boundaries.
• Stop immediately when an unapproved branch or ambiguous side effect is encountered.

Recovery

• Replay only from the last approved checkpoint after correcting the failing step.
• Suspend the workflow when downstream state can no longer be reconciled deterministically.

Handoff

• Return the executed steps, pending approvals, and checkpoint references.
• Explain whether the workflow finished, paused, rolled back, or is awaiting human action.

Validation Gates & Test Matrix

• Required validation suites: unit, integration, simulation, regression-baseline

Failure Modes & Recovery Playbook

Tool Call Implementation

• Reuse existing credentials first. Check environment variables, secure stores, and active sessions before prompting.
• Start with the smallest authenticated read or validation call that proves identity and scope.
• Preserve request, response, and approval traces in mailchimp-workflow-runbook so downstream owners do not need to rediscover context.
• If any auth, contract, or approval gate fails, halt execution and attach remediation guidance instead of guessing.

Credential Reuse Policy

• Reuse valid provider credentials by default and prefer tenant-scoped sessions over newly created secrets.
• Prompt for credentials only when they are missing, invalid, expired, or point at the wrong environment.
• For webhook flows, validate the signing secret against a known sample before accepting live traffic.

Guardrails

• quality: Checkpoint every step boundary and attach side-effect evidence before proceeding. (step-checkpoint+evidence-attach)
• safety: Pause the workflow when approval context is missing or stale. (workflow-approval-check)
• reliability: Replay only from approved checkpoints after step failures. (checkpoint-replay)

Acceptance Checklist

• Credential preflight and scope validation completed successfully.
• Required validation suites ran and all fail-closed gates passed.
• mailchimp-workflow-runbook, scorecard, and handoff packet were produced.
• Any mutations, approvals, or rollbacks are reflected in the artifact bundle.

Anti-Patterns

• Do not ask for new credentials before checking reusable auth context.
• Do not skip the read-only or dry-run validation step for mutating work.
• Do not proceed when approval gates, signing secrets, or rollback checkpoints are missing.
• Do not hand off partial or ambiguous provider state as complete.

Handoff Contract

• Produces: mailchimp-workflow-runbook, execution scorecard, approval trace, and next actions.
• Consumes: workflow specification, trigger context, approval policy.
• Readiness rule: release only after auth, contract, approval, and reliability gates all pass.
• Downstream hint: route to mailchimp:workflow-automator consumers with approval and credential context attached.

Observability & Continuous Improvement

• SLO: >=99.7% successful runs per 7-day window
• Error budget: <=0.3% critical failures per 7-day window
• Alert triggers:
• credential validation failures exceed baseline
• schema or contract regressions persist for two consecutive runs
• critical posture or rollback events exceed tolerance
• Primary outcome metric: workflow success rate
• Secondary metrics: approval latency, retry recovery rate
• Review cadence: weekly