Integration directory

Connect your stack.
Glove keeps the state.

Glove Core holds its own state and record, and executes on it. Where you run a CRM, an ERP or your own tools, Glove connects bidirectionally and keeps them in sync — writing every outcome back. Keep the stack you rely on; replace nothing to start.

Do you need a CRM at all? → Glove vs Salesforce

Deep CRM integrations

Bidirectional · state stays in sync
How it connects

Anything that starts a conversation can feed the same state.

Channels, records and events all write into one shared state, so the process reads the same context regardless of where the turn came from.

Channels01
WhatsApp, web chat and SMS
Email and inbound forms
Voice, on Glove Core
Connected systems02
HubSpot and Salesforce, bidirectional
Spreadsheets and internal databases
Your own APIs, called as process steps
Events03
Webhooks from any source
Record and stage changes
Scheduled timers and SLAs
See how channels share one state →

Glove does not ask you to migrate anything.

Glove Core runs the process and holds the record; the systems you already run keep doing what they do well, kept in sync. Replace nothing to start.

Bring your stack to the call.

Thirty minutes on one of your own processes, running against the systems you already use.