Skip to content

consolidated: Capture Zapier integration walkthrough screenshots #190

Open

Description

@superdav42

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 Screenshot audit and refresh program (master) #64.

Context & Decisions

  • The original Screenshots: Zapier integration walkthrough (14 placeholders) #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.

Activity

  1. added
    documentationImprovements or additions to documentation
    help wantedExtra attention is needed
    origin:workerCreated by headless/pulse worker session
    consolidatedIssue superseded by a consolidated child
    tier:standardAuto-created by pulse labelless backfill (t2112)
    on Oct 11, 2026
  2. locked as resolved and limited conversation to collaborators on Oct 11, 2026
  3. superdav42 commented on Oct 11, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=3f237a3e63c551de51516ef4b0968b41 runner=superdav42 ts=2026-10-11T02:25:09Z max_age_s=1800 version=3.34.13 opencode_version=1.18.31 lease_token=3f237a3e63c551de51516ef4b0968b41 device=device-1783824528-2609248-26808 session=issue-190 phase=prelaunch expires_at=1791685631

  4. superdav42 commented on Oct 11, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_LEASE phase=prelaunch lease_token=3f237a3e63c551de51516ef4b0968b41 device=device-1783824528-2609248-26808 session=issue-190 expires_at=1791685975 ts=2026-10-11T02:25:25Z attempt_id=attempt:fc887c92-6069-4e23-a25c-c1a823119199

  5. added
    status:queuedWorker dispatched, not yet started
    and removed
    status:queuedWorker dispatched, not yet started
    on Oct 11, 2026
  6. 341 remaining items

  7. superdav42 commented on Nov 6, 2026

    @superdav42
    ContributorAuthor

    aidevops.sh v3.39.119 automated scan.

  8. superdav42 commented on Nov 6, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=49b341cfc1c34add2ecae06ce8064c37 runner=superdav42 ts=2026-11-06T02:47:40Z max_age_s=1800 version=3.39.119 opencode_version=1.18.31 lease_token=49b341cfc1c34add2ecae06ce8064c37 device=device-1783824528-2609248-26808 session=issue-190 phase=prelaunch expires_at=1793933382

  9. superdav42 commented on Nov 6, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_LEASE phase=prelaunch lease_token=49b341cfc1c34add2ecae06ce8064c37 device=device-1783824528-2609248-26808 session=issue-190 expires_at=1793933735 ts=2026-11-06T02:48:05Z attempt_id=attempt:ed67eedb-d696-47ab-8dd9-00c17b7b0770

  10. added
    status:queuedWorker dispatched, not yet started
    and removed
    status:queuedWorker dispatched, not yet started
    on Nov 6, 2026
  11. superdav42 commented on Nov 6, 2026

    @superdav42
    ContributorAuthor

    Dispatching worker (deterministic).

  12. superdav42 commented on Nov 6, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_LEASE phase=ready lease_token=49b341cfc1c34add2ecae06ce8064c37 device=device-1783824528-2609248-26808 session=issue-190 expires_at=1793940565 ts=2026-11-06T02:49:25Z attempt_id=attempt:ed67eedb-d696-47ab-8dd9-00c17b7b0770


    aidevops.sh v3.39.119 automated scan.

  13. superdav42 commented on Nov 6, 2026

    @superdav42
    ContributorAuthor

    CLAIM_RELEASED reason=blocked runner=superdav42 ts=2026-11-06T02:50:18Z aidevops_version=3.39.119 opencode_version=1.18.31 claim_id=6675493548 nonce=49b341cfc1c34add2ecae06ce8064c37 lease_token=49b341cfc1c34add2ecae06ce8064c37 device=device-1783824528-2609248-26808 session=issue-190

    TERMINAL_BLOCKER_CIRCUIT active=true observations=2 task_revision=6665e44e3d1f1127611ac40f blocker=acf05bf0adb333a56d232f79

    Automatic redispatch is held for the repeated known blocker. See the preceding recovery observation.

    An OWNER/MEMBER can retry without deleting history by posting terminal-blocker-circuit:retry as a standalone line. Relevant revisions re-arm code/brief blockers, but never permission blockers. Retry schedules verification only and grants no access.


    aidevops.sh v3.39.119 plugin for OpenCode v1.18.31

  14. removed their assignment
    on Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    auto-dispatchconsolidatedIssue superseded by a consolidated childdocumentationImprovements or additions to documentationhelp wantedExtra attention is neededorigin:workerCreated by headless/pulse worker sessionstatus:blockedPartial work blocked; inspect reason and next actiontier:standardAuto-created by pulse labelless backfill (t2112)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions