Docs: add invoice-created automation trigger (407069)

[cursor]

Jira

• https://vendasta.jira.com/browse/TLKM-1749

Change classification

• Feature behavior change
• UI / UX change (trigger is available in trigger selection)

Summary of documentation updates

Updated existing Automations docs to reflect the new trigger:

• docusaurus/docs/automations/automation-triggers-reference.mdx
  • Added An invoice is created under the Sales trigger table with overview/special case/example use case.
• docusaurus/docs/automations/index.mdx
  • Added invoice created to the common trigger examples so the trigger is discoverable from the overview.

Existing docs updated vs. new docs created

• Updated existing docs only
• No new page created

Placement reasoning

• The change is a new automation trigger event, so the canonical location is the existing Automation Triggers Reference page.
• The overview page already lists common trigger examples; adding this trigger there improves discoverability without duplicating full reference content.

Acceptance criteria coverage

Mapped from TLKM-1749 acceptance criteria:

1. Build event emission in the sales order repository
   • Internal implementation detail; not directly documented in partner-facing docs.
2. Create automation trigger for invoice creation
   • Documented in automation-triggers-reference.mdx as An invoice is created.
3. Define tasks related to the automation
   • Internal planning/implementation detail; no stable partner-facing behavior to document.
4. Implement frontend changes for trigger selection
   • Reflected in user-facing docs by listing invoice created among available/common triggers.

Figma/images usage

• No Figma links or screenshots were provided in the Jira payload.
• Documentation was updated from Jira text context and existing docs structure.

Skills used

• Repository skill used: sprint-review (workflow/rules for release-ready doc updates, mapping to existing docs, evergreen style)
• Repository tools used for discovery: ripgrep/glob/read

Assumptions and limitations

• Jira payload indicates one merged linked PR but did not expose directly queryable PR author details in accessible GitHub search results.
• I only documented confirmed partner-facing behavior (new trigger availability) and avoided internal architecture details.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi

Related coded-change authors from linked PRs: unable to reliably resolve from available metadata in this environment, so no additional user mentions were added to avoid tagging incorrect people.