In development — usable.software is not live yet.
Usable.softwareA Balane Tech system
All modules/OperationsM15
M15Shared· Operations

Integrations

Connect Usable both ways with your existing systems: data lands idempotently (no duplicate mess on re-sync) and flows back out via an outbound queue.

Live preview — real view with sample data

your-address.usable.works
NameSystemDirectionDataScheduleStatusLast resultLast sync
Bauer & Co.DoneDoneEntry 5ReviewedIn progressOpen09/06/2026
Wolf SpeditionReviewedReviewedRecord 6OpenDoneIn progress20/06/2026
Roth HandelOpenOpenItem 7In progressReviewedDone01/07/2026
Meyer GmbHIn progressIn progressEntry 8DoneOpenReviewed12/07/2026
Kraus LogistikDoneDoneRecord 9ReviewedIn progressOpen23/07/2026

Not a screenshot: the same interface you get in production.

What you do here

You create connections (e.g. to DATEV, a shop, a REST API or via webhook), pick the direction (inbound, outbound or two-way) and the target data (e.g. customers or articles). Inbound records are matched by their external id: known = update, new = create. That keeps two-way mirroring clean and duplicate-free.

Credentials & connection method

For each connection you set how Usable authenticates against the external system (API key, OAuth 2.0, basic auth or HMAC signature). The actual key is stored write-only in the vault: it is saved but never shown again — you only see "set on …". Endpoints must start with https; internal addresses are blocked for security reasons. Use "Test connection" to check the endpoint before going live.

Status & log

Each connection has a status (active, paused, error) and a run log: when it last synced, how many records came in and out and whether there were errors. The queue shows what is still pending. The run log is the GoBD audit trail and is never altered or deleted. "Sync now" triggers a connection immediately and delivers pending records.

Data protection & law

If a connection sends personal data to an external system, record the recipient, the data categories and the status of the data processing agreement (Art. 28 GDPR) here — exactly the entries your record of processing activities (Art. 30) needs. If the recipient is outside the EU/EEA, state the recipient country and the legal basis for the third-country transfer (Art. 44 ff.). Without it, the transfer is not permitted.

What's inside

  • Integrations
  • Integration
  • New integration
  • Sync now
  • Test connection
  • Set credential
  • Set status
  • Pause
  • Activate