Triggering a Sync

A sync can start in one of three ways:

Webhook — the source system pushes a notification to ExpoPlatform the moment a record changes, and processing kicks off immediately. Visit is the main webhook-driven integration.
Scheduled — every scheduled-polling integration is picked up by a scheduler that ticks every five minutes. This is on by default for every subscription; you don't need to configure it.
Manual — you trigger it yourself from the admin UI. This page covers how.

For the mechanics of scheduled polling (cadence, cursor advancement, pausing), see Scheduled Syncs and Full Resyncs.

Manual triggers

Manual syncs are started from the Auto Sync tab on the integration's configuration page. The tab lists one subscription card per entity the integration syncs — one card for visitor-only or exhibitor-only integrations, two cards for integrations like Visit that sync both.

Each card has two buttons:

Trigger a sync now — runs an incremental sync immediately, ahead of the next scheduler tick. Use this when you've just changed a setting and want to verify the effect without waiting up to five minutes.
Trigger a full resync — clears the integration's sync cursor and re-fetches all matching records from the source. Slower than an incremental run, but guarantees nothing has been missed.

Multi-step integrations add a third button, Resync Steps…, covered below.

How to start a manual sync

Go to Admin → Integrations → your integration
Open the Auto Sync tab
On the subscription card for the entity you want to sync, click either Trigger a sync now or Trigger a full resync

When to use a full resync

Trigger a full resync when:

Setting up the integration for the first time
Recovering from an error state
You've changed a key setting (Category Mapping, Product Categories Mapping, field mapping) and want the new rules applied to all existing records — not just new ones
You suspect data was missed due to a connectivity issue

A full resync also re-runs the update field mapping for every existing record. If you have any fields included in the update mapping, those fields will be overwritten with the current source values on every record. See How Sync Works → What happens when a record is re-imported before running one.

Resync Steps (multi-step integrations)

Some integrations run their sync as a chain of steps — for example, fetching a list of exhibitors, then fetching detailed data per exhibitor. These integrations show a Resync Steps… button next to the sync buttons.

Clicking it opens a dialog listing every step:

Tick the steps you want to re-run (at least one)
Click Start Resync

The selected steps run as a full sync within a single job; unselected steps are skipped. Use this to repair one specific step — for example re-pushing exhibitor logos to ExpoFP — without re-running the entire chain.

Webhook triggers

Webhook-driven integrations (currently Visit) send a notification to a dedicated ExpoPlatform endpoint as soon as a record changes in the source system. ExpoPlatform then fetches and processes the changed record without waiting for a scheduled poll.

You don't trigger webhooks manually — they fire automatically. What you can do:

Check webhook health — the Visit configuration page has a Webhook Information panel on the Visitor Settings and Exhibitor Settings tabs, showing the current state of the webhook connection
Reactivate a broken webhook — if the webhook status shows error, Visit has stopped delivering notifications; you'll need to reactivate it and trigger a full resync to recover any missed changes

See the Visit integration page for the specifics.

Webhook errors mean missed updates. If a webhook enters error state, any changes that occurred during the error window are not replayed automatically. Reactivate the webhook or trigger a full resync to catch up.

Scheduled runs

Every scheduled-polling integration uses the same scheduler, which ticks every five minutes. On each tick, any subscription due for a sync gets a new run queued automatically.

You don't need to set up a schedule — it's on by default for every scheduled-polling integration once the subscription is created.

For the details on cadence, cursor advancement, pausing, and daily full resyncs, see Scheduled Syncs and Full Resyncs.