Health status
System availability, event lag and queue size show right in the connection's interface.
IntegrationsSystem catalog and statuses
Don't change your systems.
Connect them once.
The catalog is a target list: it shows which system classes and products the ecosystem plans to support. Connector depth is confirmed by contract tests — until then the status stays honest.
Connect onceThe source of truth stays put
The ecosystem does not move your database. It reads what's permitted and acts where the object lives.
Catalog
The target system catalog
The system classes and specific products the connector architecture targets. An integration counts as ready only after contract tests.
Showing 18 of 18
| System | Class | Operations | Direction | Requirements |
|---|---|---|---|---|
| 1C | ERP & accounting | Read · Write · Events | Two-way | Full access or exchange via the standard mechanism |
| Bitrix24 | CRM & workspace | Read · Write · Events | Two-way | An account with rights to the needed entities |
| amoCRM | CRM | Read · Write · Events | Two-way | An integration key and deal permissions |
| MoySklad | Warehouse & trade | Read · Write · Events | Two-way | An API token and document permissions |
| Saby / SBIS | E-documents, HR, accounting | Read · Write · Events | Two-way | Agreed access to the document flow |
| Kontur | E-documents & checks | Read · Events | Inbound | Access to the organization's services |
| Yandex 360 | Office | Read · Write · Events | Two-way | The organization's OAuth app |
| VK WorkSpace | Office | Read · Write · Events | Two-way | The organization's OAuth app |
| Directum | ECM and BPM | Read · Write · Events | Two-way | Access to routes and documents |
| ELMA365 | BPM & CRM | Read · Write · Events | Two-way | Access to processes and entities |
| Naumen | Service and contact center | Read · Write · Events | Two-way | Access to tickets and SLAs |
| SAP | ERP | Read · Write · Events | Two-way | Sign-off from the security team |
| Oracle | ERP & databases | Read · Write · Events | Two-way | Sign-off from the security team |
| Banks | Finance | Read · Write | Two-way | Payment rights are granted separately |
| Telephony | Communications | Read · Events | Inbound | Access to calls and recordings |
| Messengers | Communications | Read · Write · Events | Two-way | A business account and channel connection |
| Marketplaces | Commerce | Read · Events | Inbound | The seller account's API key |
| Industry systems | Domain-specific perimeters | Depends on the system | Configurable | Connector built by your team or a partner |
Connection health
A connection is visible and verifiable
Connector state is part of the product, not an admin's side concern.
Failure and retry
A failed action is never lost: Hummer Continuity queues it and retries by the rules.
Contract tests
Before a connector is declared Available it passes a test suite on real operations.
Connection permissions
Scope and permitted operations are set at connection time and visible to the owner.
Validity period
Access is granted for a term and renewed deliberately, not silently.
Revocation
Disconnecting takes one click and never breaks the history of completed actions.
Missing a system?
File a request or build the connector yourself
The Connector SDK is open: a customer team or a partner can build a connector to an internal or industry system and publish it to HummerStore if they wish.