Once your Salesforce integration is set up, day-to-day operations come down to a handful of actions: trigger a sync on demand, change how often automatic syncs run, watch the health of the integration, and read the logs when something looks off.Documentation Index
Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt
Use this file to discover all available pages before exploring further.
The integration’s overview page shows status, last-sync time, and quick actions. Health and logs are tabs on the same page.
Run a manual sync
Manual sync is useful for four cases:- You just connected Salesforce and want to confirm sync works.
- You changed sync rules and want to see the new result set immediately.
- New records arrived in Salesforce that you need in Spotzee right now.
- You’re troubleshooting and want to watch a sync happen in real time.
Trigger Sync now
Choose Sync now on the integration card. The button shows progress while the sync runs.
- Connects to Salesforce using the saved OAuth credentials.
- Queries for records matching your sync rules.
- Compares them against existing Spotzee users by external ID.
- Creates new Spotzee users for new records.
- Updates existing users where Salesforce data has changed.
- Logs the outcome (counts, errors, durations) to the Logs tab.
Change sync frequency
By default, Spotzee runs the integration every 60 minutes. Adjust the frequency per integration if you need fresher data or want to consume fewer Salesforce API calls.Choosing the right interval
A few rules of thumb:- High-velocity sales orgs (lots of leads converting fast) tend toward 15-30 minute syncs so changes propagate quickly.
- Stable customer bases (low daily change) tend toward 4-12 hour syncs to conserve API calls.
- Small Salesforce orgs can afford 5-minute syncs because the incremental delta is tiny.
- Large enterprise orgs with API limits in mind run hourly or every few hours.
Incremental sync
After the initial full sync, Spotzee runs incremental syncs by default. Each incremental run pulls only records whoseLastModifiedDate is newer than the previous successful sync. That’s why most syncs return small numbers even when your org has hundreds of thousands of records: only the changed ones come through.
A few notes on what counts as “modified” in Salesforce:
- Any field value changing.
- Record owner changing.
- Related-record changes that propagate (depending on your Salesforce sharing config).
- Manual touches by admins.
Health checks
Spotzee runs four automated health checks against every Salesforce integration:| Check | What it verifies | Failure means |
|---|---|---|
| Credentials | The OAuth tokens still authorise calls to Salesforce | Reconnect to refresh the OAuth grant |
| Field mappings | Every mapped Salesforce field still exists on the object | A field was renamed, deleted, or the user lost permission to read it |
| API limits | Remaining Salesforce API quota is above 10% | You’re running low on Salesforce API calls; check usage in Salesforce Setup |
| Sync staleness | Most recent successful sync is within twice the configured frequency | Syncs are failing or stuck; investigate the logs |
Status badges
Each integration carries one of four statuses:| Status | Colour | Meaning | Action |
|---|---|---|---|
| Active | Green | Healthy. Syncs running on schedule. | None. |
| Error | Red | Something failed. Health check or sync. | Drill in, check logs, fix. |
| Incomplete | Amber | Setup not finished. | Pick objects, configure rules, map fields. |
| Inactive | Grey | Manually disabled by an admin. | Re-enable when ready. |
Read the logs
Every sync writes log entries. Use the Logs tab to see what happened on each run. Event types you’ll see:| Event | Meaning |
|---|---|
sync_started | A sync job began. |
sync_completed | The sync finished without fatal errors. |
sync_failed | The sync hit an unrecoverable error and stopped. |
records_imported | New users were created from Salesforce records. |
records_updated | Existing users were updated with new Salesforce data. |
health_check | A scheduled health check ran. |
Pause and resume
Set status to Inactive to pause syncs without losing configuration:
To resume, re-activate from the same card. Sync rules, field mappings, and OAuth credentials are preserved. The next scheduled sync runs after re-activation.
Next steps
Troubleshoot
Solutions for OAuth failures, missing records, duplicates.
Map fields
Adjust field mappings when fields rename or new ones land.
Configure sync rules
Refine which records flow in.
Salesforce overview
What the integration does and what data flows.