ERP connections
Link one or more Standard Books companies to herbe.calendar for activity sync and creation.
Each ERP connection links herbe.calendar to one Standard Books company. A tenant commonly has two or three connections (e.g. one per legal entity). Connections are independent — each has its own credentials, sync state, and color.
Manage at Admin → Config → Standard ERP Connections.
Adding a connection
Click + Add Connection and fill in:
| Field | Notes |
|---|---|
| Connection name | Friendly name shown in the sources dropdown, e.g. "Burti Production" |
| Company code | The company number in Standard Books, e.g. 3 |
| API base URL | The REST API endpoint, e.g. https://erp.company.com/api |
| Server UUID | (Optional) From Standard Books → Server → Preferences → Server UUID. Enables hansa:// deep links that open records in the desktop client. |
Then choose one authentication method:
OAuth — enter the Client ID and Client Secret from Standard ID, then click Connect OAuth. You'll be redirected to Standard ID to authorize. After approval, tokens are stored encrypted in the database and refreshed automatically.
Basic auth — enter a Standard Books username and password directly. Simpler but credentials are static; rotate them in the ERP when needed.
Standard ID OAuth setup
If using OAuth:
- Go to standard-id.hansaworld.com and create an OAuth application.
- Set the redirect URI to
https://<your-domain>/api/herbe/callback. - Note the Client ID and Client Secret, enter them in the connection form, and click Connect OAuth.
Sync behavior
The incremental sync runs every 15 minutes during business hours and every hour off-hours. It fetches new and updated events using a per-connection cursor. A full reconciliation runs nightly and replaces the whole rolling window.
Events from each connection appear in the calendar under the Outlook source color for that connection. Users see activities from all active connections they have access to.
Connection health
Admin → Cache shows the sync status for each connection — last sync timestamp, next scheduled sync, and any error messages. If a connection shows errors, check the credentials and that the ERP API URL is reachable from the internet.