Feature Request: YouTube API Integration for Training Videos and Livestream Analytics

[WorshipWarehouse]

Summary

Add YouTube API integration to ChurchBoard to allow churches to embed training videos directly within position resources while also providing livestream analytics and monitoring capabilities inside the ChurchBoard dashboard.

This integration would connect ChurchBoard's volunteer management and production workflows with one of the most common platforms churches already use for video hosting and livestreaming.

Problem

Many churches rely on YouTube for:

• Volunteer training videos.
• Production tutorials.
• Service livestreams.
• Archived services.
• Sermon content.
• Online engagement.

Currently, teams must manage YouTube content separately from their ChurchBoard workflows. This creates several challenges:

• Volunteers must search for training videos manually.
• Training resources are scattered across documents, emails, and shared drives.
• Production teams must leave ChurchBoard to monitor livestream performance.
• Leaders lack centralized visibility into online engagement.

Proposed Solution

Integrate the YouTube Data API and YouTube Analytics API into ChurchBoard to provide two primary capabilities:

1. YouTube Training Resource Integration
2. YouTube Livestream Monitoring and Analytics

---

Feature Area 1: YouTube Training Video Integration

Position-Based Training Videos

Allow administrators to attach YouTube videos directly to ChurchBoard positions.

Example:

Position: ProPresenter Operator

Training Resources:

• "ProPresenter Basics"
• "Sunday Presentation Workflow"
• "Troubleshooting Common Issues"
• "How to Handle Last-Minute Changes"

When a volunteer is scheduled for that position, their ChurchBoard dashboard automatically displays the relevant videos.

Features

• Connect a YouTube channel or account.

• Search and import videos.

• Embed videos directly inside ChurchBoard.

• Attach videos to:

  • Positions
  • Checklists
  • Documents
  • Service types
  • Teams

• Track whether volunteers have viewed required training videos.

• Mark videos as required or optional.

Example Workflow

1. Production leader creates a "Camera Operator" position.

2. Leader attaches three YouTube training videos.

3. Volunteer is scheduled through Planning Center.

4. ChurchBoard displays:

   • Camera Operator checklist.
   • Training documents.
   • Required videos.

5. Volunteer completes training before serving.

---

Feature Area 2: YouTube Livestream Integration

Livestream Dashboard

Allow ChurchBoard to display live YouTube broadcast information without requiring users to open YouTube Studio.

Display:

• Current livestream status.
• Stream title.
• Scheduled streams.
• Viewer count.
• Concurrent viewers.
• Stream duration.
• Likes and engagement metrics.
• Chat activity (where available).
• Stream health information.
• Broadcast errors or warnings.

Production Monitoring

During a service, production teams could quickly view:

• Is the stream live?
• Are viewers connected?
• Is engagement increasing?
• Are there issues requiring attention?

This could exist alongside other ChurchBoard monitoring features such as:

• SPL monitoring.
• Restream status.
• Production checklists.
• Service workflows.

---

Analytics Dashboard

Provide historical reporting for church leadership.

Possible metrics:

Audience Metrics

• Total views.
• Average watch duration.
• Peak concurrent viewers.
• Returning viewers.
• Subscriber growth.
• Traffic sources.

Service Reporting

Create reports such as:

Sunday Service Livestream

• Date:
• Platform:
• Peak viewers:
• Average watch time:
• Total engagement:
• Stream health:

This would allow churches to understand online engagement over time.

---

Benefits

Centralized Volunteer Training

Volunteers receive all necessary resources in one location instead of searching through multiple platforms.

Improved Volunteer Onboarding

New team members can quickly learn their role through structured training pathways.

Better Production Awareness

Production teams can monitor livestream performance without switching between multiple dashboards.

Stronger Documentation Culture

Churches can build repeatable systems around training and service execution.

Leadership Insights

Pastors and ministry leaders gain better visibility into online engagement and outreach.

---

Future Enhancements

Automated Training Paths

Create role-based training programs:

Example:

Audio Engineer Training

1. Console Basics Video
2. Gain Structure Video
3. EQ Fundamentals Video
4. Sunday Workflow Checklist

Certification Tracking

Track:

• Completed training.
• Completion dates.
• Required renewals.
• Volunteer readiness.

Automatic Livestream Linking

When a service is created:

• Automatically attach the upcoming YouTube livestream.
• Display stream information to production teams.
• Connect livestream analytics to the service record.

Multi-Platform Analytics

Combine YouTube data with future integrations:

• Restream.
• Facebook Live.
• Vimeo.
• ChurchStreaming.tv.
• BoxCast.

---

Expected Outcome

YouTube integration would expand ChurchBoard from a production scheduling and monitoring tool into a complete volunteer training and digital engagement platform.

By combining position-based resources, volunteer workflows, and livestream analytics, churches would have a centralized system where teams can prepare, serve, and measure impact from one dashboard.

[wtapper89]

ChurchBoard 1.4.0 implements the live-monitoring slice of this request via #29: YouTube and Facebook channel monitoring plus BoxCast, Resi, and Restream sources in a responsive livestream widget, with live state, elapsed time, and viewer count when the provider exposes it. This issue remains open for the training-video library, historical analytics, and engagement-reporting portions.

[wtapper89]

ChurchBoard 2.0 includes a modular livestream-status foundation and position-resource workflows, but the full authenticated YouTube Data/Analytics API scope in this issue (training completion, channel import, historical analytics, and stream-health details) is not yet complete. Leaving this open as roadmap work.