Skip to content

Add wxcc-token-java-sample playbook (Java OAuth2, WxCC token)#61

Merged
adamweeks merged 1 commit into
mainfrom
playbook/wxcc-token-java-sample
Apr 2, 2026
Merged

Add wxcc-token-java-sample playbook (Java OAuth2, WxCC token)#61
adamweeks merged 1 commit into
mainfrom
playbook/wxcc-token-java-sample

Conversation

@adamweeks
Copy link
Copy Markdown
Collaborator

  • Spring Boot sample from WebexSamples token-java-sample with Gradle src/main layout, env-based OAuth secrets, and deployment docs.
  • README covers My Apps integration, scopes table, WxCC Flow Builder and API token usage, and contact-center catalog rationale.
  • APPHUB metadata with expanded Markdown description and contact_center product type.

Made-with: Cursor

Playbook Pull Request

For internal contributors submitting a new Playbook. See CONTRIBUTING.md for the full submission process from branch naming through merge.


Required Files

Before submitting, confirm your Playbook folder under playbooks/<tool-slug>/ includes:

  • Playbook folder at playbooks/<tool-slug>/ with a kebab-case name matching the third-party tool slug
  • README.md with all 6 required sections: Use Case Overview, Architecture, Prerequisites, Code Scaffold, Deployment Guide, Known Limitations
  • APPHUB.yaml present and correctly formatted (see below)
  • diagrams/ folder present (e.g. with an architecture diagram)
  • src/ folder present with sample code

APPHUB.yaml format

Ensure APPHUB.yaml is correctly formatted per the APPHUB schema in CONTRIBUTING.md: all required fields filled, valid values for vertical and webex_component; status = draft or review (do not set published). The Validate then Publish to Integration workflow will fail if required fields are missing or invalid.


Author Checklist

Before submitting, confirm:

  • This PR touches only one playbook folder (see CONTRIBUTING.md)
  • All 6 required sections present in README.md (Use Case Overview, Architecture, Prerequisites, Code Scaffold, Deployment Guide, Known Limitations)
  • APPHUB.yaml complete with all required fields
  • Branch name follows playbook/<tool-slug>
  • Code scaffold connects to a real, documented Webex API endpoint
  • Deployment guide tested end-to-end
  • No competitor tools (Genesys, NICE, Five9, Talkdesk) as primary integration targets

Review Process and Turnaround

  • Automated validation: When you open or update this PR, the Validate then Publish to Integration workflow runs and posts a comment with results. The PR cannot merge until all checks pass. Fix any failures and push to re-run.
  • Human review: After validation passes, a reviewer performs a ~15-minute spot-check using the review criteria in CONTRIBUTING.md. You may receive change requests; push commits to this branch to address them.
  • Turnaround: Reviewers aim to complete the initial spot-check within 3 business days; you will be notified of any change requests in the PR.

Reviewer: 15-Minute Spot-Check

  • Does the scaffold connect to a real Webex API, SDK, or Developer Tool?
  • Is the deployment guide followable by a competent developer?
  • Does this duplicate an existing Playbook?

Self-Attestation

By submitting this PR I confirm that the deployment guide is accurate to the best of my knowledge and that Webex does not guarantee the functional accuracy of this Playbook.

- Spring Boot sample from WebexSamples token-java-sample with Gradle
  src/main layout, env-based OAuth secrets, and deployment docs.
- README covers My Apps integration, scopes table, WxCC Flow Builder and
  API token usage, and contact-center catalog rationale.
- APPHUB metadata with expanded Markdown description and contact_center
  product type.

Made-with: Cursor
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 1, 2026

Playbook Validation Results

Playbook: playbooks/wxcc-token-java-sample

  • README.md exists
  • README.md contains all 6 required section headers
  • APPHUB.yaml exists
  • No prohibited competitor as primary integration target (APPHUB metadata)
  • All required APPHUB.yaml fields present and non-empty
  • APPHUB.yaml categories has at least one value
  • APPHUB.yaml friendly_id ends with -playbook
  • APPHUB.yaml tag_line is valid (91/128 chars)
  • APPHUB.yaml product_types is valid
  • /diagrams/ folder exists
  • /src/ folder exists
  • Folder name is kebab-case

Validation passed.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 1, 2026

Playbook Details (from APPHUB.yaml)

Field Value
Playbook title Webex Contact Center — Java OAuth token sample
Third-party tool
Categories developer-tools, security-compliance
Estimated implementation time 2-4 hours

Auto-generated from APPHUB.yaml.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 1, 2026

Contentstack: Published to integration

wxcc-token-java-sample-playbook


Published playbooks are available in the integration environment.

@adamweeks adamweeks merged commit 6ca21fa into main Apr 2, 2026
3 checks passed
@adamweeks adamweeks deleted the playbook/wxcc-token-java-sample branch April 2, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants