Skip to main content

How to Provide Data for Forms & Flows

Dennis Han
Updated

The Preferred Method: Automated Integrations

For a seamless and reliable experience, we recommend using one of our automated integrations. These systems automatically keep your Forms & Flows roster in sync with your central Student Information System (SIS), saving you time and ensuring data is always accurate.

We fully support and recommend these integrations:

  • Clever
  • ClassLink
  • A cross-rostered API connection (if you are already a SchoolStatus customer)

If your district uses one of these systems, please let our support team know, and we can help you get connected.

Supplemental Methods: Manual & SFTP Uploads

Sometimes, you may have staff or data in another system (like an HR platform) that isn't in your main SIS.

For this supplemental data, you have two options:

  1. Manual File Upload: You can directly upload a .CSV or .XLSX file through your Forms & Flows dashboard.
  2. Secure File Transfer (SFTP): You can set up a secure, automated file transfer for these records.

These methods are useful for adding small groups of users or specific data that isn't available in your primary SIS.

Method

Best For

How It Works

✅ Automated Integrations (Clever, ClassLink, API)

All districts. This is the standard method for getting all your student and staff data into Forms & Flows.Data syncs automatically and securely from your SIS on a regular schedule.

🟡 Manual Uploads / SFTP

Adding small amounts of data, like staff from an HR system not connected to your SIS.You provide a spreadsheet file either by uploading it yourself or through a secure automated transfer.

❌ Full Manual Imports

Not supported for full districts. Managing all student and staff records for an entire district manually is not feasible. 

⚠️ Important Note: For large-scale, district-wide implementations, we cannot rely solely on manual file uploads or SFTP for all data. These methods are not designed for the ongoing, automated syncing required for thousands of records. They are best used as a supplement to a primary integration.

Examples of Supported Setups

  • A New York district using eSchoolData or SchoolTool would connect through our existing infrastructure for those systems.
  • A district already using SchoolStatus would utilize its existing API connection.
  • A district using Clever or ClassLink would sync through that platform.
     

Related articles