Skip to content
AssureSwarm Docs

Agent Operating Guide

/bridge-snow-sync

Bi-directional sync that keeps Cowork Canvas issue and remediation-task records in step with ServiceNow: Canvas updates push out, ServiceNow changes return as suggestions.

Keep your Canvas issue and remediation-task records in lockstep with ServiceNow. Outbound, the skill pushes Canvas updates to the mapped ServiceNow tables. Inbound, ServiceNow substatus and remediation progress come back as suggestions via suggest_change for a human to approve; nothing is written to your tenant directly. It’s the same shape as the Archer sync: you configure the field mapping once with /bridge-mapping-edit, and syncs are then mapping-driven, conflict-aware, and idempotent.

When to use

Section titled “When to use”

When you track issues and remediation, often regulatory issue management, in both Canvas and ServiceNow and need them consistent without dual entry. Pull ServiceNow substatus and remediation progress into Canvas, push Canvas updates out, or run both directions.

Inputs

Section titled “Inputs”
Flag Required Notes
--push / --pull / --both No Sync direction. If omitted, the skill asks. Both is the default.
--since <ISO> No Override the last-sync watermark to re-pull or re-push from a chosen point.

Example

Section titled “Example”

/bridge-snow-sync --pull reads each ServiceNow record changed since the last pull, applies your mapping in reverse, and submits one suggest_change per record into the mapped Canvas custom fields. You review and approve the batch in Canvas. If a field changed on both sides since the last sync, that record stops and the conflict is surfaced rather than auto-merged.

Good to know

Section titled “Good to know”
  • ServiceNow’s table API has tighter rate limits than Archer, so the skill paces its calls using the per-customer limits in the bridge config.
  • When both sides changed the same field, the skill hands the conflict to /bridge-conflict-resolve and holds that record until it’s resolved.
  • Pulled remediation completion is the usual trigger to kick off a validation step on the Canvas side.
  • Check sync health and open conflicts with /bridge-sync-status.
Section titled “Related”