Playbook Import Export and Agency Reuse

Reuse boundary

Reusable playbooks are useful for agencies, but they should never carry client-specific secrets, provider keys, customer data, private policies, or assumptions about WooCommerce configuration. Export the repeatable structure, then localize the context on each site.

Import review

Before importing, compare provider setup, Knowledge Base sources, roles, approval policy, product language, coupon rules, order status conventions, and support ownership. The slash commands tutorial explains playbook behavior, while playbooks and quick actions covers structured input and approval boundaries.

Agency standard

Track source site, export date, version, owner, required local changes, and first-run result. Imported playbooks should run in staging or read-only mode before client production execution.

Owner and cadence

• Primary owner: operations lead for the affected workflow, watcher, agent, playbook, or custom tool.
• Review cadence: before first run, after failed runs, after provider changes, and during monthly automation review.
• Escalate when exported playbooks carry client-specific assumptions, secrets, private policies, or unreviewed write behavior into another site.

Production checklist

• Remove client-specific secrets, customer data, private policies, and provider assumptions before exporting a playbook.
• Localize imported playbooks for each site's roles, Knowledge Base sources, WooCommerce rules, approval policy, and provider setup.
• Define trigger, owner, input data, output, approval requirement, retry behavior, failure notification, and kill switch before enabling automation.
• Start with read-only runs or staging examples until the team has reviewed successful traces and audit records.

Acceptance checks

• The imported playbook runs read-only or in staging before production execution.
• Agency operators can identify source site, export date, local changes, owner, and first-run result.
• The workflow or agent has a named owner who can pause it and explain its last run.
• Failures produce enough audit, diagnostics, and notification context for another operator to respond.

Common mistakes

• Importing an agency playbook into a client site without localizing provider, policy, product, role, and approval assumptions.
• Turning a useful prompt into automation before defining trigger, owner, input scope, approval rule, and failure handling.
• Ignoring noisy alerts or failed runs until operators stop trusting the workflow surface.

Related operations

• Review Agency Governance.
• Practice with the slash commands tutorial.
• Use Workflow Safety before enabling recurring automation.
• Use Automation Safe Mode and Kill Switches before production automation rollout.
• Review Audit Log Review after the first production runs.
• Use Model Evaluation and Regression Review before broad agent or workflow rollout.
• Use Playbooks and Quick Actions for repeatable structured tasks.
• Use Prompt Template Governance before sharing reusable instructions.
• Use Playbook Import Export and Agency Reuse before reusing client workflows.
• Use Tool Validation and Schema Testing before exposing custom tools.
• Use Webhook and External Service Security before sending data outside WordPress.
• Use Insights and Reporting Review before acting on AI summaries.
• Use Content and SEO Workflows before AI-assisted publishing work.
• Use Localization and Translation Review before publishing multilingual copy.
• Use Media Library Asset Lifecycle before reusing generated assets.
• Use Marketing Studio Campaign Review before campaign launches.
• Use Analytics Attribution Review before acting on campaign summaries.