Path: Centers → Data Sources · URL: /centers/data-sources
What this page does
The Data Sources page is where you tell Wazzi which connector feeds each data category. For example: where do Properties come from? Where do Portfolio Contacts come from? Each data category is a slot — and each slot can be filled by one connector.
When you fill a slot and turn on its scheduled sync, Wazzi periodically pulls data from the source connector into Wazzi's data warehouse, where it powers Centers products (dashboards, automations, AI agents).
Why have a separate "Data Sources" concept? Because the same connector can power different categories. Your CRM might feed both Contacts (customer pipeline) and Owners (property owner records). Defining the binding here keeps your data model explicit instead of magic.
How sync actually works
Schedule fires (e.g., "every hour at :37")
↓
Wazzi calls the connector's API for that data category
↓
Records are normalized into Wazzi's internal schema for that category
↓
Stored in your org's data warehouse
↓
Centers products query the warehouse — never the live source
↓
Updates Last Synced timestamp on the Data Sources rowA few implications:
- The dashboard doesn't show real-time data. It shows whatever was synced last — typically minutes to hours stale.
- Failed syncs leave the previous data intact. A bad sync doesn't blank your dashboards. The row goes red until you fix it.
- Manual sync forces an immediate run. Useful after a config change to verify it works without waiting for the next scheduled tick.
Steps
1. Click Centers → Data Sources in the sidebar.
You'll see a row for every data category. The top section is shared across all Centers (Properties, Reservations, Work Orders, etc.); additional rows appear for each enabled Center (Portfolio rows for Portfolio Center, etc.).
2. For each category you want to source, pick a connector from the Connector dropdown.
Heads up — empty dropdown? If a category's Connector dropdown is empty, you haven't added a connector that supplies that data type yet. Head to Browsing the Connectors Catalog and add one.
Example: wiring Portfolio Contacts, Opportunities, and Activity to High Level after setting up the connector in Setting Up the High Level Connector.
3. Configure the schedule, run a manual sync, and turn the row Active.
Each row exposes:
- Schedule — the cron expression for scheduled syncs (e.g.,
37 * * * *= "minute 37 of every hour"). Click to edit. New to cron? See the primer below. - Last Synced — when the last successful sync ran (or
—if never). - Manual sync — click the circular arrow icon to trigger a one-off sync. Useful for verifying configuration.
- Active — flip this on to start scheduled syncs. A row that's bound to a connector but not Active will never auto-sync — only when you click manual sync.
4. Click Save in the top-right to commit configuration changes.
Cron primer
Cron expressions are five space-separated fields: minute hour day-of-month month day-of-week.
| Cron | Means |
|---|---|
* * * * * | Every minute (don't do this — too aggressive). |
0 * * * * | Every hour at minute 0. |
37 * * * * | Every hour at minute 37. (Wazzi defaults to staggered minutes to avoid stampedes.) |
*/15 * * * * | Every 15 minutes. |
0 */6 * * * | Every 6 hours. |
0 9 * * * | Once a day at 09:00 UTC. |
0 9 * * 1-5 | Weekdays at 09:00 UTC. |
Wazzi runs all schedules in UTC. Convert from your local time as needed.
Troubleshooting
- "No connector" in the dropdown for a category. No connector you've added supplies that data type. Add one in Browsing the Connectors Catalog.
- Last Synced is
—even though I set up a connector. The row isn't Active yet, or the schedule hasn't ticked. Click manual sync to confirm wiring works. - Sync failed (red Last Synced). Click the row to see the error. Common: the underlying connector's credentials are bad — fix them in the connector edit page (e.g., Setting Up the High Level Connector), then retry.
- Sync succeeds but data isn't showing in the Center dashboard. Sync runs are eventual — give it 5 to 10 minutes for the warehouse to refresh. If it's still missing, check that Center filters aren't excluding the data.
- I changed the schedule but the next sync ran on the old schedule. Schedule changes apply to future runs; an in-progress sync uses the schedule it was scheduled with.
Best practices
- Don't sync more often than the source can handle. Every sync is real API calls against the external system. A 1-minute schedule on a CRM with 1000 records per page can hit rate limits.
- Keep schedules staggered. Wazzi auto-staggers minute fields by default; if you customize, avoid setting everything to
:00. - Disable Active on rows you're not using. No reason to make API calls if no Center consumes the data yet.
- Review failed-sync alerts weekly. A connector with rotating tokens silently fails sync until someone updates creds. Catch it early via Reading the Audit Log.
Frequently asked questions
Can two connectors feed the same category?
No. Each category has exactly one connector at a time. To union data from multiple sources, use a connector that already aggregates them, or feed each source into a different category.
How far back does a fresh sync go?
Depends on the connector. Most do a full backfill on first sync, then incrementals after. Plan for the first sync to take longer than subsequent ones.
Can I trigger a sync via API?
Yes — Wazzi exposes a sync trigger endpoint per data source. Useful for chaining syncs to external events.
What if I unbind a category (set it to "No connector") with synced data?
The historical data stays in your warehouse; new syncs stop. Re-binding starts incremental syncs again.
What's next
- The same linkage shows up on the connector's Access tab — that's a good place to verify which categories a given connector is feeding. See Setting Up the High Level Connector.
- Need to add a connector that doesn't appear in the dropdown? See Browsing the Connectors Catalog.
- Want to disable a Center temporarily? See Enabling Centers Products.