How integration syncing works

Once an integration is connected, Pilea handles the syncing. Here’s how the machinery works - and which knobs you can turn.

Automatic syncing

HubSpot, Attio, Intercom and Zendesk sync automatically every 6 hours. New conversations, tickets, and customer records flow in without anyone pressing a button.

Meeting recorders (Jiminny, Granola, Fireflies, Gong) are polled every 6 hours too, shortly after the CRM and support syncs. See Importing call recordings and meetings. Attio call transcripts follow the Attio sync - see Importing call transcripts from Attio.

Notion syncs on its own schedule, per page.

Slack is event-driven: messages arrive as they’re posted, no polling.

Exports (Linear, Jira, GitHub Issues) and GitHub Repositories don’t sync on a schedule. Exports happen when you click, and status changes come back through webhooks; repository reads happen on demand.

Manual syncing

Every connected integration card has a Sync now button. Click it when you want fresh data immediately - say, right after connecting or after changing a filter.

Long syncs run in the background, with progress shown on the card. Need to stop one? Stop sync is right there on the card too.

Full re-sync

Sometimes you want to re-import history - for example, after changing filters. Open the integration’s config dialog, go to the Advanced tab, and click Full Re-sync from Start. It re-imports all data from the “Synced from” date, and already processed records are left untouched - so you won’t create duplicates.

The Advanced tab also has Pull Tags Now, which refreshes the list of tags available for filtering without running a full sync.

The “Sync from” date

Each integration has a Sync from date in its settings that controls how far back to sync data. Data older than this date is skipped. You set it during setup and can adjust it later. The integration’s overview shows it as Synced from, next to Last sync and Items synced.

Organization-level connections, workspace-level control

Integrations connect once, at the organization level - every workspace in your organization can then access them. But each workspace stays in control of its own slice:

• An Auto sync switch per workspace, on the connected card - one workspace can sync from an integration while another leaves it off. The workspace that connects an integration gets it switched on; other workspaces start with it off.
• Filters and data types per workspace, in the config dialog’s Settings tab - tag filters, and where an integration syncs multiple data types, Data Types checkboxes to choose which ones import.

ℹ️ Note: Only admins can change integration settings. If you can’t toggle a sync or edit a filter, ask a Pilea admin in your organization.

Duplicating a workspace copies its settings but leaves integration syncing off in the copy until you turn it on. See Creating and switching between workspaces.

PII redaction

Pilea can automatically redact names, emails, phone numbers, and other sensitive data from feedback as it’s imported - across all sources. Turn it on in Settings → PII Redaction. You’ll also find a Privacy & Security card at the top of the Integrations page describing this.

Redaction is fail-closed: imported feedback is not analysed until redaction has confirmed it’s safe. See PII redaction settings.

💡 Tip: If you’re importing support tickets or call recordings, turn on PII redaction before your first big sync so sensitive details never land in your feedback data in the first place.

Disconnecting

Each integration’s Advanced tab has a Disconnect Integration option. Heads up: disconnecting stops syncing data and may affect other workspaces in your organization, since connections are organization-wide.

What’s coming

Exports to Monday, Asana, ClickUp and Trello are rolling out - email us if you’d like early access.

Next: Using the Pilea API and MCP