Docs: clarify Zapier Business App trigger setup instructions (390829)

[cursor]

Jira

• https://vendasta.jira.com/browse/MRNA-2136

Change classification

• Feature behavior change (Zapier integration behavior for Business App trigger setup instructions)

Summary of documentation updates

• Updated existing page: docusaurus/docs/administration/advanced/developer-apis/zapier-integration.mdx
  • In Creating Your First Zap → Step 1, added explicit guidance to use Business App as a trigger app and complete Zapier Setup instructions before trigger testing.
  • In Troubleshooting → App Greyed Out, replaced contradictory guidance with app-selection guidance:
    • Vendasta for actions
    • Business App for triggers
    • Webhooks by Zapier for automation webhook trigger flows
  • In FAQ Why is the app greyed out when I try to add it?, aligned wording with the same behavior.

Existing docs updated vs new docs created

• Updated existing docs only
• No new pages created

Placement reasoning

• The issue concerns Zapier setup behavior and trigger/action selection, which is already documented in the Zapier integration guide and its troubleshooting/FAQ sections. Updating this page keeps related guidance in one canonical location and avoids duplication.

Acceptance criteria coverage

Mapped from Jira issue description/expected behavior:

1. Setup instructions should populate for Business App trigger flows
   • Covered by new trigger setup instruction under Step 1, explicitly telling users to select Business App and complete in-app Setup instructions.
2. Reduce confusion between Vendasta app and Business App trigger use
   • Covered by troubleshooting and FAQ clarifications that differentiate which app to use for actions vs triggers vs webhook-based workflows.

Figma/images usage

• Jira attachments/screenshots were referenced from webhook context (behavior comparison between Business App and Vendasta app).
• No direct image/Figma asset extraction was performed in-repo for this docs patch.

Skills used

• sprint-review (repo skill read and applied for evergreen style and repo compliance checks)
• Repository discovery/search tools: rg, ReadFile, Glob

Assumptions and limitations

• Webhook payload did not include explicit, machine-readable acceptance criteria fields; coverage was mapped from the issue description and expected behavior text.
• Linked code PR metadata in accessible GitHub search was not available from this environment, so no additional code-author tags were added beyond requested reviewers.

Requested reviewers/tags

@ahnikakuse
@haleyserrano
@maryam6samadi