claude-plugin-wordpress-manager 2.6.0 → 2.9.1

package/skills/wp-analytics/references/traffic-attribution.md

@@ -0,0 +1,92 @@
+# Traffic Attribution
+
+## UTM Parameter Standards
+
+UTM (Urchin Tracking Module) parameters tag URLs to track marketing campaign performance.
+
+### Required Parameters
+| Parameter | Purpose | Example |
+|-----------|---------|---------|
+| `utm_source` | Traffic origin | `google`, `facebook`, `newsletter` |
+| `utm_medium` | Marketing channel | `cpc`, `email`, `social`, `referral` |
+| `utm_campaign` | Campaign name | `spring-sale-2024`, `black-friday` |
+
+### Optional Parameters
+| Parameter | Purpose | Example |
+|-----------|---------|---------|
+| `utm_term` | Paid search keyword | `running+shoes` |
+| `utm_content` | Ad variation / CTA | `cta-button-red`, `hero-banner` |
+
+### URL Format
+```
+https://example.com/page?utm_source=google&utm_medium=cpc&utm_campaign=spring-sale
+```
+
+## Source/Medium Mapping
+
+### Standard Mappings in GA4
+| Source/Medium | Description |
+|---------------|-------------|
+| `google / organic` | Google organic search |
+| `google / cpc` | Google Ads paid search |
+| `facebook / social` | Facebook organic posts |
+| `facebook / cpc` | Facebook paid ads |
+| `newsletter / email` | Email marketing campaigns |
+| `(direct) / (none)` | Direct traffic or untagged |
+| `referral / referral` | Incoming links from other sites |
+
+### Plausible Source Mapping
+Plausible uses `visit:source` which maps to the referrer or `utm_source`:
+- Organic search: `Google`, `Bing`, `DuckDuckGo`
+- Social: `Facebook`, `Twitter`, `LinkedIn`
+- UTM-tagged: uses the `utm_source` value directly
+
+## Combining GA4 Traffic with WooCommerce Conversions
+
+### Data Flow
+1. **GA4** tracks the user journey: source, medium, pages visited, events
+2. **WooCommerce** records the transaction: products, revenue, order ID
+3. **Attribution** connects which traffic source led to which purchase
+
+### Attribution Models
+| Model | Logic | Best For |
+|-------|-------|----------|
+| Last click | Credits the last touchpoint before conversion | Simple campaigns |
+| First click | Credits the first touchpoint in the journey | Brand awareness |
+| Linear | Equal credit to all touchpoints | Multi-touch evaluation |
+| Data-driven | ML-based credit distribution (GA4 default) | Complex funnels |
+
+### Implementation Steps
+1. Ensure GA4 enhanced e-commerce tracking is active (via Site Kit or GTM)
+2. Map WooCommerce order IDs to GA4 transaction events
+3. Use `ga4_conversions` tool with `purchase` event to get revenue by source
+4. Cross-reference with WooCommerce order data for product-level attribution
+
+## Cross-Platform Discrepancy Analysis
+
+### Common Causes of Data Differences
+| Issue | GA4 Impact | Plausible Impact |
+|-------|-----------|-----------------|
+| Ad blockers | Under-reports (blocked) | Under-reports (blocked) |
+| Cookie consent | Under-reports if declined | No impact (cookieless) |
+| Bot traffic | Filtered (mostly) | Filtered |
+| SPA navigation | May miss if not configured | Tracks via History API |
+| Caching | CDN may cache tracking | Same |
+| Sampling | Large datasets sampled | No sampling |
+
+### Reconciliation Steps
+1. Compare total sessions (GA4) vs visits (Plausible) for the same period
+2. Calculate the gap percentage: typically 10-30% difference is normal
+3. Check source-level: organic search should be closest between platforms
+4. Investigate large discrepancies in specific sources or pages
+5. Use CWV data as an independent third reference for page-level traffic
+
+## Campaign Tracking Best Practices
+
+- **Always tag** paid campaign URLs with UTM parameters
+- **Use consistent naming** conventions (lowercase, hyphens, no spaces)
+- **Document all campaigns** in a shared spreadsheet or naming convention guide
+- **Test tagged URLs** before launching campaigns
+- **Monitor `(not set)`** values in GA4 — indicates untagged traffic
+- **Review referral exclusions** in GA4 to prevent self-referrals
+- **Set up conversion goals** in both GA4 and WooCommerce for accurate ROI

package/skills/wp-analytics/scripts/analytics_inspect.mjs

@@ -0,0 +1,153 @@
+/**
+ * analytics_inspect.mjs — Detect analytics configuration readiness.
+ *
+ * Checks WP_SITES_CONFIG for GA4, Plausible, and Google API key credentials.
+ * Scans for analytics plugins and tracking code.
+ *
+ * Usage:
+ *   node analytics_inspect.mjs [--cwd=/path/to/project]
+ *
+ * Exit codes:
+ *   0 — analytics configuration found
+ *   1 — no analytics configuration found
+ */
+
+import { readFileSync, existsSync, readdirSync } from 'node:fs';
+import { join, resolve } from 'node:path';
+import { argv, stdout, exit } from 'node:process';
+
+// ---------------------------------------------------------------------------
+// Helpers
+// ---------------------------------------------------------------------------
+
+function readFileSafe(filePath) {
+  try { return readFileSync(filePath, 'utf-8'); } catch { return null; }
+}
+
+function existsSafe(filePath) {
+  try { return existsSync(filePath); } catch { return false; }
+}
+
+function globDir(dirPath) {
+  try { return readdirSync(dirPath); } catch { return []; }
+}
+
+// ---------------------------------------------------------------------------
+// Detectors
+// ---------------------------------------------------------------------------
+
+function detectGA4Config() {
+  const ga4 = { configured: false, indicators: [] };
+  const raw = process.env.WP_SITES_CONFIG;
+  if (!raw) return ga4;
+
+  let sites;
+  try { sites = JSON.parse(raw); } catch { return ga4; }
+  if (!Array.isArray(sites)) return ga4;
+
+  for (const site of sites) {
+    const label = site.id || site.url || 'unknown';
+    if (site.ga4_property_id) {
+      ga4.configured = true;
+      ga4.indicators.push(`ga4_property_id configured for ${label}`);
+    }
+    if (site.ga4_service_account_key) {
+      ga4.indicators.push(`ga4_service_account_key configured for ${label}`);
+    }
+  }
+  return ga4;
+}
+
+function detectPlausibleConfig() {
+  const pl = { configured: false, indicators: [] };
+  const raw = process.env.WP_SITES_CONFIG;
+  if (!raw) return pl;
+
+  let sites;
+  try { sites = JSON.parse(raw); } catch { return pl; }
+  if (!Array.isArray(sites)) return pl;
+
+  for (const site of sites) {
+    const label = site.id || site.url || 'unknown';
+    if (site.plausible_api_key) {
+      pl.configured = true;
+      pl.indicators.push(`plausible_api_key configured for ${label}`);
+    }
+    if (site.plausible_base_url) {
+      pl.indicators.push(`plausible_base_url: ${site.plausible_base_url}`);
+    }
+  }
+  return pl;
+}
+
+function detectGoogleApiKey() {
+  const cwv = { configured: false, indicators: [] };
+  const raw = process.env.WP_SITES_CONFIG;
+  if (!raw) return cwv;
+
+  let sites;
+  try { sites = JSON.parse(raw); } catch { return cwv; }
+  if (!Array.isArray(sites)) return cwv;
+
+  for (const site of sites) {
+    const label = site.id || site.url || 'unknown';
+    if (site.google_api_key) {
+      cwv.configured = true;
+      cwv.indicators.push(`google_api_key configured for ${label}`);
+    }
+  }
+  return cwv;
+}
+
+function detectAnalyticsPlugins(cwd) {
+  const indicators = [];
+  const pluginsDir = join(cwd, 'wp-content', 'plugins');
+  const plugins = globDir(pluginsDir);
+
+  const analyticsPlugins = [
+    'google-analytics-for-wordpress',
+    'google-site-kit',
+    'wp-google-analytics-events',
+    'plausible-analytics',
+    'koko-analytics',
+    'matomo',
+    'independent-analytics',
+  ];
+
+  for (const plugin of analyticsPlugins) {
+    if (plugins.includes(plugin)) {
+      indicators.push(`plugin: ${plugin}`);
+    }
+  }
+  return { found: indicators.length > 0, indicators };
+}
+
+// ---------------------------------------------------------------------------
+// Main
+// ---------------------------------------------------------------------------
+
+function main() {
+  const cwdArg = argv.find(a => a.startsWith('--cwd='));
+  const cwd = cwdArg ? resolve(cwdArg.split('=')[1]) : process.cwd();
+
+  const ga4 = detectGA4Config();
+  const plausible = detectPlausibleConfig();
+  const googleApiKey = detectGoogleApiKey();
+  const plugins = detectAnalyticsPlugins(cwd);
+
+  const anyConfigured = ga4.configured || plausible.configured || googleApiKey.configured || plugins.found;
+
+  const report = {
+    analytics_configured: anyConfigured,
+    ga4: ga4,
+    plausible: plausible,
+    google_api_key: googleApiKey,
+    analytics_plugins: plugins,
+    cwd,
+  };
+
+  stdout.write(JSON.stringify(report, null, 2) + '\n');
+  exit(anyConfigured ? 0 : 1);
+}
+
+main();

package/skills/wp-content-attribution/SKILL.md

@@ -97,3 +97,4 @@ The script checks WooCommerce presence, analytics plugins, UTM tracking setup, c
 - `wp-content-repurposing` — transform high-ROI content into multi-channel formats
 - `wp-search-console` — correlate GSC keyword data with WooCommerce conversions for content-commerce attribution
 - `wp-content-optimization` — prioritize optimization of high-revenue content using attribution data
+- Per correlazione contenuto→conversione completa, combina `wp-analytics` + `wp-content-attribution`

package/skills/wp-content-optimization/SKILL.md

@@ -170,3 +170,4 @@ Use the **`wp-content-strategist`** agent for content optimization workflows tha
 - **`wp-content-attribution`** — track content sources and attribute traffic
 - **`wp-programmatic-seo`** — generate SEO-optimized content at scale
 - **`wp-social-email`** — distribute optimized content across channels
+- Per prioritizzare ottimizzazione con dati CWV, combina `wp-analytics` + `wp-content-optimization`

package/skills/wp-content-workflows/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: wp-content-workflows
+description: This skill should be used when the user asks about "workflow automation",
+  "triggers", "scheduled tasks", "WP-Cron", "content publishing triggers",
+  "hook-based actions", "post status transitions", "automated notifications",
+  "workflow triggers", "event-driven actions", "content lifecycle hooks",
+  "multi-channel actions", "trigger management", or mentions setting up
+  automated workflows that fire on WordPress events or schedules.
+version: 1.0.0
+tags: [workflows, triggers, cron, automation, hooks, scheduling]
+---
+
+# WordPress Content Workflows Skill
+
+## Overview
+
+Event-driven workflow automation system for WordPress. Combines WP-Cron scheduling, content lifecycle hooks, and WordPress action/filter hooks to trigger multi-channel actions (Slack, email, webhook). Provides trigger creation, management, testing (dry-run), and audit logging. This skill connects WordPress events to notification and action channels, enabling automated responses to content changes, user actions, and scheduled tasks.
+
+## When to Use
+
+- User wants to create automated triggers for WordPress events
+- User needs scheduled tasks (cron-based publishing, periodic reports)
+- User asks about post status transitions (draft to published, trash, etc.)
+- User wants to hook into WordPress actions (user_register, comment_post, etc.)
+- User needs multi-channel action routing (Slack + email + webhook on same event)
+- User asks about trigger management (list, test, enable/disable, delete)
+- User wants to set up WooCommerce order-based workflows
+- User needs to audit or troubleshoot existing workflow triggers
+
+## Decision Tree
+
+1. **What type of trigger?**
+   - "cron" / "scheduled" / "periodic" → Schedule-Based Triggers (Procedure 1)
+   - "on publish" / "post status" / "content change" → Content Lifecycle Hooks (Procedure 2)
+   - "on login" / "user register" / "comment" / "plugin" → WP Action/Filter Hooks (Procedure 3)
+   - "notify Slack and email" / "multi-channel" → Multi-Channel Action Configuration (Procedure 4)
+   - "list triggers" / "test" / "disable" / "delete" → Trigger Management (Procedure 5)
+
+2. **Run detection first:**
+   ```bash
+   node skills/wp-content-workflows/scripts/workflow_inspect.mjs [--cwd=/path/to/project]
+   ```
+   This identifies configured action channels, automation plugins, WP-Cron status, and webhook setup.
+
+## Procedures
+
+### Procedure 1: Schedule-Based Triggers
+
+See `references/schedule-triggers.md`
+- Configure WP-Cron intervals (hourly, twicedaily, daily, weekly, custom)
+- Set up scheduled content publishing triggers
+- Create recurring health check and report triggers
+- External cron setup (server cron vs WP-Cron)
+- Test scheduled trigger with `wf_create_trigger` using cron schedule type
+
+### Procedure 2: Content Lifecycle Hooks
+
+See `references/content-lifecycle-hooks.md`
+- Hook into post status transitions (draft→published, published→trash)
+- Support custom post types (products, portfolios, events)
+- Monitor taxonomy and term changes
+- Track media upload events
+- Create trigger with `wf_create_trigger` using content lifecycle event type
+
+### Procedure 3: WP Action/Filter Hooks
+
+See `references/wp-action-hooks.md`
+- Hook into core WordPress actions (user_register, wp_login, comment_post)
+- WooCommerce hooks (woocommerce_new_order, woocommerce_order_status_changed)
+- Plugin activation/deactivation hooks
+- Filter hooks for content transformation workflows
+- Create trigger with `wf_create_trigger` using action hook event type
+
+### Procedure 4: Multi-Channel Action Configuration
+
+See `references/multi-channel-actions.md`
+- Map triggers to one or more action channels (Slack, email, webhook)
+- Configure template variables ({{post_title}}, {{user_name}}, {{order_total}})
+- Channel-specific formatting (Block Kit for Slack, HTML for email, JSON for webhook)
+- Rate limiting per channel to prevent flooding
+- Update trigger actions with `wf_update_trigger`
+
+### Procedure 5: Trigger Management
+
+See `references/trigger-management.md`
+- List and filter triggers with `wf_list_triggers`
+- Activate/deactivate triggers without deleting (via `wf_update_trigger`)
+- Test triggers in dry-run mode
+- Review trigger audit log
+- Bulk operations (enable/disable all, export/import)
+- Delete stale triggers with `wf_delete_trigger`
+
+## MCP Tools Reference
+
+| Tool | Description |
+|------|-------------|
+| `wf_list_triggers` | List all workflow triggers with optional status/type filters |
+| `wf_create_trigger` | Create a new workflow trigger (cron, lifecycle, action hook) |
+| `wf_update_trigger` | Update trigger config, actions, or status (active/inactive) |
+| `wf_delete_trigger` | Delete a workflow trigger (with safety confirmation) |
+
+## Reference Files
+
+| File | Content |
+|------|---------|
+| `references/schedule-triggers.md` | WP-Cron patterns, custom intervals, external cron setup |
+| `references/content-lifecycle-hooks.md` | Post status transitions, CPT support, taxonomy changes, media events |
+| `references/wp-action-hooks.md` | Core WP actions, WooCommerce hooks, plugin hooks, filter hooks |
+| `references/multi-channel-actions.md` | Channel config, template variables, formatting, rate limiting |
+| `references/trigger-management.md` | Listing, activate/deactivate, dry-run testing, audit log, bulk ops |
+
+## Recommended Agent
+
+Use the **`wp-site-manager`** for automated workflow orchestration that combines trigger creation, multi-channel action routing, and lifecycle management.
+
+## Related Skills
+
+- **`wp-alerting`** — shares Slack and SendGrid channels for notification delivery
+- **`wp-monitoring`** — source of health/performance data that may trigger workflows
+- **`wp-webhooks`** — outbound/inbound webhook infrastructure for webhook action channel
+- **`wp-social-email`** — shares SendGrid and Mailchimp config for email actions
+
+## Cross-references
+
+- Workflow triggers pair with `wp-alerting` for severity-based notification routing
+- Scheduled triggers depend on WP-Cron config detectable via `wp-monitoring`
+- Webhook actions use `wp-webhooks` infrastructure for outbound delivery
+- Email actions share SendGrid/Mailchimp config with `wp-social-email`
+- WooCommerce hooks connect to `wp-woocommerce` for order-based workflows
+
+## Troubleshooting
+
+| Issue | Cause | Resolution |
+|-------|-------|------------|
+| Cron trigger not firing | DISABLE_WP_CRON is true and no server cron configured | Set up server cron job: `*/5 * * * * wget -qO- https://example.com/wp-cron.php` |
+| Content hook missed | Post updated via direct DB query (bypasses hooks) | Ensure content changes go through `wp_update_post()` or REST API |
+| Slack action fails | slack_webhook_url or slack_bot_token not configured | Add Slack credentials to WP_SITES_CONFIG |
+| Email action 403 | SendGrid API key lacks Mail Send permission | Regenerate key with "Mail Send" access in SendGrid dashboard |
+| Duplicate triggers firing | Multiple hooks registered for same event | Review triggers with `wf_list_triggers` and deduplicate |
+| Trigger test fails | Action channel unreachable or credentials expired | Run `workflow_inspect.mjs` to verify channel configuration |
+| WooCommerce hooks silent | WooCommerce not active or hooks not registered | Verify WooCommerce is active; hooks fire only after `woocommerce_init` |
+| Detection script exit 1 | No workflow config found | Add action channel credentials to WP_SITES_CONFIG and install wp-crontrol |

package/skills/wp-content-workflows/references/content-lifecycle-hooks.md

@@ -0,0 +1,131 @@
+# Content Lifecycle Hooks
+
+## Post Status Transitions
+
+WordPress fires `transition_post_status` on every status change:
+
+| Transition | From → To | Common Use |
+|------------|-----------|------------|
+| Publish | `draft` → `publish` | Notify team of new content |
+| Schedule | `draft` → `future` | Confirm scheduling |
+| Unpublish | `publish` → `draft` | Alert editors |
+| Trash | `publish` → `trash` | Audit log entry |
+| Restore | `trash` → `draft` | Notify original author |
+| Pending review | `draft` → `pending` | Notify reviewers |
+
+### Hook Signatures
+
+```php
+// Generic transition hook
+add_action('transition_post_status', function ($new, $old, $post) {
+    if ($new === 'publish' && $old !== 'publish') {
+        // First-time publish — trigger workflow
+    }
+}, 10, 3);
+
+// Specific transition hooks (preferred for performance)
+add_action('draft_to_publish', function ($post) {
+    // Fires only on draft → publish transition
+});
+
+add_action('pending_to_publish', function ($post) {
+    // Fires on pending → publish (after review approval)
+});
+```
+
+### Trigger Config Example
+
+```json
+{
+  "type": "content_lifecycle",
+  "event": "draft_to_publish",
+  "post_type": "post",
+  "actions": [
+    { "channel": "slack", "message": ":newspaper: New post published: *{{post_title}}* by {{post_author}}" }
+  ]
+}
+```
+
+## Custom Post Type Support
+
+The same transition hooks work for any registered post type:
+
+| Post Type | Slug | Example Trigger |
+|-----------|------|-----------------|
+| WooCommerce Product | `product` | Notify when new product goes live |
+| Portfolio | `portfolio` | Share on social when portfolio item published |
+| Event | `event` | Send reminder email on event publish |
+| Landing Page | `page` | Alert marketing team on page publish |
+
+Filter by post type in trigger config:
+
+```json
+{
+  "event": "draft_to_publish",
+  "post_type": ["post", "product"],
+  "condition": "post_type IN (post, product)"
+}
+```
+
+## Taxonomy and Term Changes
+
+| Hook | Fires When | Parameters |
+|------|------------|------------|
+| `set_object_terms` | Terms assigned to a post | `$object_id`, `$terms`, `$tt_ids`, `$taxonomy` |
+| `created_term` | New term created | `$term_id`, `$tt_id`, `$taxonomy` |
+| `edited_term` | Term updated | `$term_id`, `$tt_id`, `$taxonomy` |
+| `delete_term` | Term deleted | `$term_id`, `$tt_id`, `$taxonomy`, `$deleted_term` |
+
+Example: notify when a post is tagged with "featured":
+
+```json
+{
+  "type": "content_lifecycle",
+  "event": "set_object_terms",
+  "condition": "taxonomy == 'post_tag' AND terms CONTAINS 'featured'",
+  "actions": [
+    { "channel": "slack", "message": "Post tagged as featured: {{post_title}}" }
+  ]
+}
+```
+
+## Media Upload Events
+
+| Hook | Fires When | Parameters |
+|------|------------|------------|
+| `add_attachment` | New media uploaded | `$attachment_id` |
+| `edit_attachment` | Attachment metadata updated | `$attachment_id` |
+| `delete_attachment` | Media file deleted | `$attachment_id` |
+| `wp_handle_upload` | File upload processed | `$upload` array |
+
+Example: log large file uploads:
+
+```json
+{
+  "type": "content_lifecycle",
+  "event": "add_attachment",
+  "condition": "filesize > 5MB",
+  "actions": [
+    { "channel": "webhook", "url": "{{audit_webhook_url}}", "payload": { "event": "large_upload", "file": "{{filename}}", "size": "{{filesize}}" } }
+  ]
+}
+```
+
+## Example: Notify Slack When Blog Post Published
+
+```json
+{
+  "name": "Blog Post Published Notification",
+  "type": "content_lifecycle",
+  "event": "draft_to_publish",
+  "post_type": "post",
+  "actions": [
+    {
+      "channel": "slack",
+      "message": ":mega: *New blog post published!*\n*Title:* {{post_title}}\n*Author:* {{post_author}}\n*URL:* {{post_url}}",
+      "channel_override": "#content-updates"
+    }
+  ],
+  "status": "active"
+}
+```

package/skills/wp-content-workflows/references/multi-channel-actions.md

@@ -0,0 +1,151 @@
+# Multi-Channel Action Configuration
+
+## Action Channel Types
+
+| Channel | Identifier | Required Config | Tool |
+|---------|-----------|-----------------|------|
+| Slack (Webhook) | `slack` | `slack_webhook_url` in WP_SITES_CONFIG | `slack_send_webhook` |
+| Slack (Bot) | `slack_bot` | `slack_bot_token` + `slack_channel` | `slack_send_message` |
+| Email (SendGrid) | `email` | `sendgrid_api_key` in WP_SITES_CONFIG | `sg_send_email` |
+| Webhook (HTTP) | `webhook` | Target URL in action config | Custom HTTP POST |
+| Mailchimp | `mailchimp` | `mailchimp_api_key` in WP_SITES_CONFIG | Mailchimp API |
+
+## Template Variables
+
+Common variables available in all action templates:
+
+| Variable | Description | Example Value |
+|----------|-------------|---------------|
+| `{{site_url}}` | WordPress site URL | `https://example.com` |
+| `{{site_name}}` | Site title | `My WordPress Site` |
+| `{{timestamp}}` | Event timestamp (ISO 8601) | `2026-03-01T14:30:00Z` |
+| `{{trigger_name}}` | Name of the firing trigger | `Blog Post Published` |
+| `{{post_title}}` | Post title (content events) | `Hello World` |
+| `{{post_url}}` | Post permalink | `https://example.com/hello-world` |
+| `{{post_author}}` | Post author display name | `John Doe` |
+| `{{post_type}}` | Post type slug | `post` |
+| `{{user_name}}` | User display name | `Jane Smith` |
+| `{{user_email}}` | User email address | `jane@example.com` |
+| `{{order_id}}` | WooCommerce order ID | `1234` |
+| `{{order_total}}` | Order total with currency | `$99.00` |
+| `{{order_status}}` | Current order status | `completed` |
+
+## Channel-Specific Formatting
+
+### Slack (Block Kit)
+
+```json
+{
+  "channel": "slack",
+  "format": "block_kit",
+  "blocks": [
+    {
+      "type": "header",
+      "text": { "type": "plain_text", "text": "{{trigger_name}}", "emoji": true }
+    },
+    {
+      "type": "section",
+      "fields": [
+        { "type": "mrkdwn", "text": "*Post:*\n{{post_title}}" },
+        { "type": "mrkdwn", "text": "*Author:*\n{{post_author}}" }
+      ]
+    }
+  ],
+  "fallback_text": "{{trigger_name}}: {{post_title}} by {{post_author}}"
+}
+```
+
+### Email (HTML)
+
+```json
+{
+  "channel": "email",
+  "to": "team@example.com",
+  "subject": "[{{site_name}}] {{trigger_name}}",
+  "format": "html",
+  "body": "<h2>{{trigger_name}}</h2><p><strong>{{post_title}}</strong> by {{post_author}}</p><p><a href='{{post_url}}'>View Post</a></p>"
+}
+```
+
+### Webhook (JSON)
+
+```json
+{
+  "channel": "webhook",
+  "url": "https://api.example.com/events",
+  "method": "POST",
+  "headers": { "Content-Type": "application/json", "X-Webhook-Secret": "{{webhook_secret}}" },
+  "payload": {
+    "event": "{{trigger_name}}",
+    "post": { "title": "{{post_title}}", "url": "{{post_url}}", "author": "{{post_author}}" },
+    "timestamp": "{{timestamp}}"
+  }
+}
+```
+
+## Rate Limiting Per Channel
+
+| Channel | Default Limit | Burst | Cooldown |
+|---------|---------------|-------|----------|
+| Slack (Webhook) | 1 msg/sec | 5 msg burst | 1 second |
+| Slack (Bot) | 1 msg/sec per channel | Tier 2 | Varies |
+| Email (SendGrid) | 100 msg/sec (plan-dependent) | — | None |
+| Webhook | 10 req/sec | 20 burst | 100ms |
+
+**Rate limit strategy:**
+- Queue actions when rate exceeded
+- Batch low-priority events into digest messages
+- Critical events bypass rate limits (sent immediately)
+- Log rate limit hits for trigger tuning
+
+## Multi-Channel Action Mapping
+
+A single trigger can fire multiple actions across channels:
+
+```json
+{
+  "actions": [
+    { "channel": "slack", "priority": "high" },
+    { "channel": "email", "priority": "high" },
+    { "channel": "webhook", "priority": "normal" }
+  ]
+}
+```
+
+**Priority levels:**
+- `critical` — all channels fire immediately, bypass rate limits
+- `high` — all channels fire immediately, respect rate limits
+- `normal` — queued, batched if necessary
+- `low` — batched into digest (hourly or daily)
+
+## Example: Critical Order — Slack + Email + Webhook
+
+```json
+{
+  "name": "Critical Order Alert",
+  "type": "action_hook",
+  "event": "woocommerce_payment_complete",
+  "condition": "order_total > 500",
+  "actions": [
+    {
+      "channel": "slack",
+      "priority": "critical",
+      "message": ":moneybag: *High-value order!* #{{order_id}} — {{order_total}}"
+    },
+    {
+      "channel": "email",
+      "priority": "critical",
+      "to": "sales@example.com",
+      "subject": "High-value order #{{order_id}} — {{order_total}}",
+      "template": "high_value_order"
+    },
+    {
+      "channel": "webhook",
+      "priority": "critical",
+      "url": "https://crm.example.com/api/orders",
+      "payload": { "order_id": "{{order_id}}", "total": "{{order_total}}", "event": "high_value" }
+    }
+  ],
+  "status": "active"
+}
+```