Boting GuoAI implementation & automation

Selected work / Education operations

From RPA steps
to API integration.

I migrated two ClassIn scheduling steps from Yingdao RPA to APIs, then continued maintaining the workflows as the platform changed.

Explore the migration ↓Download case study
Platform
ClassIn
Migration delivered
October 2024
My contribution
Implementation & maintenance
Tools in this migration
Yingdao RPA · APIs

01 / ContextRecurring work.
A focused change.

The scheduling workflow included adding the relevant advisor to a ClassIn lesson session, configuring teaching services for each session, and enrolling students in a separate booking system.

My migration focused on the first two steps, which had been handled through Yingdao RPA. I replaced those steps with API integrations. This case focuses on that migration and the maintenance work that followed.

02 / Before & afterSame tasks.
A different interface.

Two operational actions moved from RPA-driven interface interactions to API integration. The diagrams below explain the migration scope.

Illustrative flow · No live connection

Before: RPA-driven steps

The two tasks used Yingdao RPA to interact with the platform.

Two scheduling actions
  • Add advisor to lesson
  • Configure teaching services
Previous integrationYingdao RPA
Existing platformClassIn lesson sessions
After: API-integrated steps

The same tasks, connected through APIs in October 2024.

Two scheduling actions
  • Add advisor to lesson
  • Configure teaching services
My implementationAPI integration
Existing platformClassIn lesson sessions

Blue highlights my implementation layer, not ownership of the ClassIn platform.

Outside this migration: student onboarding in the separate booking system. These diagrams do not imply that every surrounding workflow was converted to APIs.

Reconstructed for this portfolio at task level. Not a production screenshot, API specification or live demo.

03 / My contributionImplementation,
then upkeep.

My work combined changes to the integration method with continued responsibility for operational workflows.

  1. Migrate the two scheduling actions

    Replaced Yingdao RPA steps for adding advisors to lesson sessions and configuring teaching services with API integrations in October 2024.

  2. Maintain affected integrations

    Reworked ClassIn-related integrations after a major platform update in June 2025 to support continued daily operations.

  3. Support the surrounding workflow

    Developed and maintained scheduling, student-onboarding, lesson-monitoring and reminder workflows. This broader work used Python, RPA and APIs; it is separate from the scope of the two-step migration.

04 / DeliveryBeyond the
initial change.

A migration milestone and a later maintenance milestone show how the work continued after implementation.

  1. Two steps migrated

    Advisor assignment and teaching-service configuration moved from RPA to API integrations.

  2. Adapted to a platform update

    Reworked affected ClassIn integrations and delivered related lesson-allowance checks and weekly lesson-usage resets.

05 / OutcomeWhat changed.

Two scheduling actions moved to APIs, with operational maintenance continuing afterward.

The work connects a defined integration change with the ongoing maintenance needed in an education business.

About this public case. Based on my work records and project history. Business volumes and operational records are omitted. No quantified time-saving, error-rate reduction or uptime claim is made.

Next project / Applied AI

See how I extended conversation analysis into a voice-to-report workflow.

Explore conversation analysis ↗

Boting Guo / Selected work

ClassIn: from RPA to API integration

Education operations · Migration: October 2024 · Contribution: implementation & maintenance

linkedin.com/in/boting-bob-guo-667112381

Context & scope

The scheduling workflow included adding an advisor to a ClassIn lesson session, configuring teaching services, and enrolling students in a separate booking system. I migrated the first two steps from Yingdao RPA to APIs in October 2024. Student onboarding was outside this two-step migration.

The change

Before: Advisor assignment / teaching-service configuration → Yingdao RPA → ClassIn lesson sessions.

After: The same two actions → API integration → ClassIn lesson sessions.

Simplified task-level illustration, reconstructed for this case. Not a production screenshot, API specification or live demo.

My contribution

Delivery milestones

October 2024: Completed the two RPA-to-API scheduling migrations.

June 2025: Adapted ClassIn integrations after a platform update; delivered related lesson-allowance checks and weekly lesson-usage resets.

Outcome

Two scheduling actions moved to APIs, with operational maintenance continuing afterward. The work connects a defined integration change with ongoing operational maintenance.

Public case based on my work records and project history. Business volumes and operational records are omitted. No quantified time-saving, error-rate reduction or uptime claim is made. Prepared October 2026.