How ServiceNow Syncs with ClickTime
Each sync run follows the same basic flow, whether it's a scheduled run or an on-demand re-sync. A ServiceNow record is created or updated, and on the next scheduled sync (every 30 minutes by default) ClickTime checks for anything changed since the last run. Matching records are found by sys_id, or created if none exists, and the mapped fields are written to ClickTime. The outcome — created, updated, or skipped — is logged for that record.
Bullets you can derive:
- One-directional: ServiceNow → ClickTime only
- Incremental — only changed records process each run
- OAuth (Authorization code grant)
- sys_id is the permanent identifier, independent of name changes
- Not real-time — appears on next scheduled run or on-demand re-sync

