A directory of integration opportunities. These connections are not live in 21f.
FAMILIAR TOOLS. NEW POSSIBILITIES.
Khan AcademyGoogleOutschool
THE INTEGRATION DIRECTORY
Find your family’s next connection.
Eight candidates, each with a practical use for homeschooling and a clear path to explore. Filter by what you want to bring together.
Potential connections · not connected
“Documented API” means the provider offers a developer interface; 21f still needs to build and authorize the connection. “External workflow” uses links, feeds, or files instead. Listings do not imply a partnership or endorsement.
8 of 8 opportunities
KA
External workflow
Learning
Khan Academy
Keep lesson links and available learning reports alongside your family’s plan.
How it could work
Link to lessons and import available assignment-report CSV files. Khan Academy’s legacy public API was retired; automatic progress sync is not offered here.
Access needed
Report exports are documented for teacher assignment reports. A parent or student account may not have the same export options.
What would need to be built
Add lesson-link fields and a secure CSV importer with a review step. Confirm report access and permitted use before importing; record where each result came from.
Bring permitted assignments and due dates into a more complete learning week.
How it could work
Read authorized courses and coursework through the Classroom API, then map assignments into a proposed 21f planning view.
Access needed
Google consent and appropriate teacher, student, or administrator permissions. Parent status alone does not grant access; domain and feature restrictions may apply.
What would need to be built
Build account authorization, assignment mapping, refresh controls, and disconnect handling. Check the requested scopes, verification requirements, and any feature-specific licensing.
See enrolled class times alongside the rest of your homeschool schedule.
How it could work
Use Outschool’s personal calendar feed for a proposed read-only schedule view. Booking, class changes, and enrollment stay in Outschool.
Access needed
A family’s Outschool calendar-feed link. Updates depend on refresh timing. A general public enrollment or progress API has not been verified.
What would need to be built
Build a private calendar-feed importer, show the last refresh time, and handle schedule changes. Discuss broader access with Outschool directly before planning deeper synchronization.
Make lessons, appointments, and learning blocks easier to coordinate.
How it could work
Create or update learning events in a parent-authorized calendar. Start with an app-created calendar or narrowly scoped event access.
Access needed
Google authorization and the appropriate calendar permissions. Verification can be required for public apps requesting sensitive user-data access.
What would need to be built
Add calendar selection, time-zone handling, duplicate prevention, and update controls. Define whether a connection reads, writes, or does both before the parent approves it.
Keep selected portfolios, learning documents, and receipts close to your workflow.
How it could work
Let parents choose files to use with 21f through a file picker. The drive.file scope can limit access to files created or shared with the app.
Access needed
Google consent and permission to access each file. Broader restricted scopes can add verification and security-assessment requirements.
What would need to be built
Build file selection and attachment handling, explain whether 21f stores a link or a copy, and handle revoked access. Do not request full-drive access for a selected-file workflow.
Connect a family’s Outlook schedule and permitted OneDrive learning files.
How it could work
Use Microsoft Graph to work with authorized calendar events and files, with a clearly defined permission scope for each workflow.
Access needed
Microsoft account consent within the user’s rights. Personal and work/school support differs by API; school or workplace policies may require administrator approval.
What would need to be built
Build delegated account authorization, calendar and file selection, and disconnect controls. Check account support and tenant policies before enabling each capability.
Keep authorized tutoring or co-op meetings and their join links in one plan.
How it could work
Schedule meetings for authorized hosts and surface their join links. Another teacher’s meetings remain subject to that host’s controls.
Access needed
Zoom authorization and meeting permissions. Host features depend on the account or plan; public app distribution requires Zoom review.
What would need to be built
Build user authorization and meeting scheduling, preserve host safety settings, and protect join links. Complete any required distribution review before offering it publicly.
Bring permitted coursework from participating Canvas courses into the family’s week.
How it could work
Read authorized assignment details and due dates, then map them into a proposed 21f planner without assuming access to every learner’s records.
Access needed
An enabled developer key, approved scopes, user authorization, and existing course access. Institution-managed accounts generally need administrator involvement.
What would need to be built
Configure approved access for the participating Canvas instance, build assignment import and refresh behavior, and respect the permissions and scope of each authorized user.
Official sources reviewed September 24, 2026. Provider features, account requirements, and terms can change. The workflows described here are proposals for 21f.
A PRACTICAL CONNECTION PLAN
Start useful. Connect thoughtfully.
A proposed sequence for development. Each connection needs a working implementation, permission review, and real-family testing before launch.
01
Bring the week together.
Explore Google Calendar, selected Drive files, and Outschool calendar feeds first. Start with parent-controlled access and clear refresh behavior.
02
Connect the learning work.
Evaluate Classroom, Canvas, Microsoft 365, and Zoom where the family’s account permissions support the workflow. Show what was imported and when.
03
Go deeper with evidence.
Test Khan Academy report imports where exports are available. Discuss broader provider access directly before promising enrollment or progress synchronization.
DESIGNED AROUND YOUR FAMILY
Useful connections. Clear boundaries.
Our proposed approach gives parents a clear view of what is shared, why it is needed, and how to stop the connection.
Request the smallest useful permissions. Use the provider’s authorization screen instead of collecting provider passwords.
Keep family records private.
Treat learner reports, calendar-feed links, and documents as private. Define storage, deletion, and child-account requirements before enabling a connection.
Make disconnecting clear.
Plan for revoking access, stopping updates, and explaining what happens to previously imported records.