consolidated: Capture Zapier integration walkthrough screenshots

Read docs/user-guide/integrations/zapier.md lines 24–96 and map its 13 placeholder image links to the capture table in the issue. The specified assets belong under static/img/integrations/zapier/; producing them requires an authenticated Zapier session and checking each capture for sensitive data. Done means all 13 authentic screenshots and links are in place, alt text matches the captures, and npm run build succeeds. The issue reports 104 comments, so review the discussion for current decisions before starting.

Supersedes #65 — this issue is the consolidated spec.

What

Replace the remaining generic Webhooks screenshot placeholders in the Zapier integration walkthrough with authentic, step-specific Zapier UI captures. Add 13 PNGs under static/img/integrations/zapier/ and update the corresponding image links in docs/user-guide/integrations/zapier.md.

Why

The walkthrough describes distinct Zapier screens, but 13 of its images currently point to the unrelated Ultimate Multisite Webhooks list. Step-specific captures make the instructions usable and prevent readers from mistaking WordPress admin screens for Zapier screens.

Tier

Selected tier: tier:standard

Tier rationale: The write surface and required captures are defined, but producing authentic captures requires an authenticated Zapier session and careful visual verification.

How

Files to Modify

• EDIT: docs/user-guide/integrations/zapier.md:24-96 — replace the 13 remaining /img/admin/webhooks-list.png image destinations with the mapped Zapier capture assets.
• NEW: static/img/integrations/zapier/*.png — add the 13 mapped captures below.

Complete Write Surface

• Callers/readers: Docusaurus renders docs/user-guide/integrations/zapier.md; all linked assets resolve beneath static/img/.
• Writers/mutation paths: Markdown image links in the Zapier guide are the only references to replace.
• Existing verification/tests: npm run build validates Docusaurus content and static asset resolution.
• Cleanup/rollback paths: Preserve static/img/admin/webhooks-list.png; it remains legitimately referenced by docs/user-guide/integrations/webhooks.md.

Implementation Steps

1. Use an authenticated Zapier account and capture the listed UI states at 1280×800, cropping each image to the relevant card or panel. A real end-to-end Zap session is preferred over mocked individual screens.

2. Save the following captures and update the matching image destination in docs/user-guide/integrations/zapier.md:

   Doc line	Capture	Asset path
   24	Dashboard sidebar with + Create Zap highlighted	/img/integrations/zapier/dashboard-create-zap.png
   30	App search with wp ultimo typed	/img/integrations/zapier/app-search.png
   34	Trigger dropdown showing New Ultimate Multisite Event	/img/integrations/zapier/trigger-event.png
   38	Zapier Sign in modal requesting API credentials	/img/integrations/zapier/signin-modal.png
   50	API Key, API Secret, and URL credential form	/img/integrations/zapier/credentials-form.png
   58	payment_received event selected	/img/integrations/zapier/event-picker.png
   62	Test trigger before running the test	/img/integrations/zapier/test-trigger.png
   66	Successful trigger-test payload	/img/integrations/zapier/test-result.png
   76	Create Items on Ultimate Multisite action selection	/img/integrations/zapier/action-create-items.png
   80	Authentication picker selecting the created connection	/img/integrations/zapier/action-auth.png
   86	Item dropdown listing Customers, Payments, Sites, and related types	/img/integrations/zapier/action-item-type.png
   92	Expanded Customer fields	/img/integrations/zapier/action-customer-fields.png
   96	Action test summary showing filled and unfilled fields	/img/integrations/zapier/action-test-summary.png

3. Keep line 44 on its existing /img/admin/settings-api-webhooks.png image. Current main already shows the relevant Ultimate Multisite API Settings panel there, so it is not a placeholder and no duplicate um-enable-api.png capture is needed.

4. Confirm every alt text accurately describes its visible capture, then run npm run build and inspect the rendered page/browser console for broken image links.

Hazards and Compatibility

• Credentials: Redact API keys, secrets, customer data, URLs that identify private environments, and any personal information before committing captures.
• Asset retention: Do not delete or repurpose webhooks-list.png; the Webhooks guide still uses it.
• Capture fidelity: Most captures are in Zapier, not wordpress.local; use the WordPress API Settings screen only for the already-correct line-44 asset.

Verification Before Dispatch

npm run build

• Surface mapping: A successful build verifies the changed Markdown and static image paths resolve through Docusaurus. Browser inspection verifies the Zapier page has no broken image-link console errors.

Files Scope

Hard boundaries: Do not change unrelated integration documentation or delete existing shared assets. Do not commit credentials or personal data in screenshots.

AI brief owner: @superdav42

• docs/user-guide/integrations/zapier.md
• static/img/integrations/zapier/*.png

Acceptance Criteria

• Thirteen distinct PNGs exist under static/img/integrations/zapier/ for the mapped Zapier steps.
• The 13 remaining generic webhooks-list.png destinations in docs/user-guide/integrations/zapier.md point to their corresponding mapped captures.
• The existing API Settings image at line 44 remains intact, and static/img/admin/webhooks-list.png is not deleted.
• Every screenshot is captured at 1280×800 and cropped to the relevant panel without exposing credentials, personal data, or private environment details.
• npm run build succeeds; the rendered page has no broken image links in the browser console.
• The implementation PR resolves this issue and references #64.

Context & Decisions

• The original #65 report identified 14 repeated placeholder destinations and provided the Zapier capture sequence.
• Current-head verification found that the original line-44 entry has already been corrected to /img/admin/settings-api-webhooks.png; this consolidated scope therefore retains that valid screenshot and replaces the remaining 13 placeholders.
• Per @superdav42, a real end-to-end Zapier session is preferred so the workflow and resulting screenshots are authentic.
• The no-work circuit-breaker comment is operational history only; it does not alter the implementation scope.

Contributors

cc @superdav42

aidevops.sh v3.34.13 plugin for OpenCode v1.18.31 with gpt-5.6-terra spent 3m and 73,752 tokens on this as a headless worker.