Integrations

Connecting tools

Connectors bring your operational data into Qorpera. They are the ingestion layer on which everything else depends.

Personal vs company connectors

Personal connectors are authorised per employee using that person’s OAuth consent. Gmail, Outlook, personal Drive/OneDrive, Teams, personal Calendar. The AI acts on the person’s behalf using their tokens — not via a shared service account. This matters for audit, for access scoping, and for compliance.

Company connectors are installed once by an admin and provide shared data. HubSpot, Stripe, Slack. Company connectors yield events (HubSpot, Stripe) or content + activity (Slack).

How sync works

Each connector runs on a configurable interval (default per provider). The 1-minute sync scheduler ticks through due connectors, respecting concurrency limits and a 3-failure error threshold. Connector output flows into the sync orchestrator, which dispatches a discriminated union:

event — becomes an entity via the event materializer (HubSpot contacts, Stripe invoices).
content — chunked, embedded into pgvector, indexed for retrieval; communication content is evaluated for situation detection.
activity — resolved to person/department entities and written as activity signals for timeline assembly.

Write-back

Some connectors support write-back — the AI can send an email, post a Slack message, create a document. Write-back is a separate capability registered per connector:

Gmail — send_email, reply_to_thread
Google Drive — create/append documents, create/update spreadsheets
Outlook — send_email, reply_to_thread
OneDrive — create/append documents, create/update spreadsheets
Slack — send_slack_message, react_to_message

HubSpot and Stripe do not currently support write-back; they are read-only event streams.

The AI cannot write to your systems unless you explicitly enable write-back per connector. Even with write-back enabled, policy rules can require human approval on specific action types.

Security

OAuth tokens are encrypted at rest with AES-256-GCM and decrypted only at the moment of use. Tokens refresh automatically before expiry (Google, Microsoft, HubSpot, Stripe, Slack). Revoking an OAuth consent in the source system halts sync immediately.

Previous← System jobs NextGoogle Workspace →

Personal vs company connectors

Company connectors are installed once by an admin and provide shared data. HubSpot, Stripe, Slack. Company connectors yield events (HubSpot, Stripe) or content + activity (Slack).

How sync works

event — becomes an entity via the event materializer (HubSpot contacts, Stripe invoices).

content — chunked, embedded into pgvector, indexed for retrieval; communication content is evaluated for situation detection.

activity — resolved to person/department entities and written as activity signals for timeline assembly.

Write-back

Some connectors support write-back — the AI can send an email, post a Slack message, create a document. Write-back is a separate capability registered per connector:

Gmail — send_email, reply_to_thread

Google Drive — create/append documents, create/update spreadsheets

Outlook — send_email, reply_to_thread

OneDrive — create/append documents, create/update spreadsheets

Slack — send_slack_message, react_to_message

HubSpot and Stripe do not currently support write-back; they are read-only event streams.

The AI cannot write to your systems unless you explicitly enable write-back per connector. Even with write-back enabled, policy rules can require human approval on specific action types.