Skip to main content
MSPortal.ai keeps your data current by syncing automatically from every connected integration on a regular schedule. Higher-volume data that changes often (like tickets) refreshes frequently, while reference data that rarely changes (like product catalogs) refreshes once a day. Syncs are deliberately staggered throughout the day to keep the platform fast and responsive.
All scheduled times below are in UTC. Frequencies are accurate as of the latest release and may change as we tune performance. A run can start later than its interval because of queueing, provider limits, turned-off datasets or errors.

​
Need data updated right now?

1

Open Integrations

Go to Settings > Integrations and find the integration you need.
2

Request a sync

Use the sync action for the data you need. The integration card has a Resync icon, and some setup pages offer Sync now or Quick Sync. These refresh different sets of data, so read the action before you use it.
3

Check the result

A request queues background work. Check the last synced time and any error before you rely on the data.
Clear & Resync removes the portal’s data for that integration and rebuilds it. Do not use it to get a recent update. See Clear and Resync.

​
Microsoft 365

​
Google Workspace

Enabled directory datasets and posture run daily. Posture can be deferred while Google usage reports are incomplete. Company-level Sync now queues a separate manual request. See Google Workspace setup.

​
PSA integrations

If you’ve enabled Autotask webhooks, ticket updates arrive in near real-time rather than waiting for the scheduled sync.
These are target intervals checked by a scheduler every ten minutes. Due work can start later; opt-in datasets must also be enabled.

​
RMM integrations

NinjaOne software synchronization runs daily at 04:30 UTC when Software is enabled; changed settings, company mappings, and device imports also queue software work.
Scheduled sync for the legacy network-device endpoint is paused because it is not returning usable device inventory. Standard Asio device syncs continue daily.

​
Backup & security integrations

​
Documentation integrations

​
Billing & distribution integrations

​
I made a change in my source system and it’s not showing up

1

Find the data area

Note which data is stale (tickets, users, a reference list) and which integration it comes from.
2

Check scope and mapping

Confirm that data area is turned on for the integration and the record’s company is mapped.
3

Compare the schedule

Find the data area in the tables above. A ticket sync does not refresh reference lists or financial data, which run on their own schedules.
4

Request a sync

Use the sync action from Need data updated right now?, then check the last synced time and any error. Refreshing your browser does not start a provider sync.

​
Frequently asked questions

No. It is how often the work is scheduled. Queueing, provider limits, turned-off datasets and errors can delay it. Use the last successful sync time to judge freshness.
No. What each sync action covers differs by integration. See the integration’s guide.
Quick Sync refreshes tickets. Statuses and routing options come from a separate reference-data sync that runs daily.
No. It only reloads what MSPortal already has.
No. It removes portal data before it rebuilds it. Check scope, mapping and errors first, then use a normal sync.
Send the integration, data area, affected company, last successful sync time and any visible error. Never include API secrets.