Connect an external service

What this achieves

A connector is a stored, credentialed link to another system, so data can move between it and Humavera on a schedule rather than by hand. Setting one up means giving Humavera the credentials, telling it how often to sync, and mapping the other system’s field names onto yours.

Required role: Administrator.

Before you start

Get the credentials from the other system first — the wizard asks for them in the middle of the flow and there is no partial save. Which credentials you need depends on the authentication method that system supports.

Steps

Go to Integrations → Hub.
Select Add Connector.
Under Provider, enter the Name, the Provider, and the Type.
Under Authentication, choose the Auth Type and enter the credentials it asks for.
Under Configuration, set the Sync Frequency and add Field Mappings with Add Mapping.
Under Review, check what you entered and select Review & Connect.
Open the connector and select Test connection.

Connector type

Option	Description
HRIS	A human resources system.
LMS	A learning system.
ATS	A recruitment system.
SSO	An identity provider.
Calendar	A calendar service.
Communication	A messaging or communication service.
Custom	Anything not covered above.

Type is a category, not a product. Name the specific system in the Name and Provider fields, where it identifies the connector for whoever administers it next.

Authentication

Option	Description
OAuth 2.0	Asks for the Client ID, Client Secret, Token URL, and Scopes (comma-separated).
API Key	Asks for the API Key and the Base URL.
Basic Auth	Asks for a Username and Password.
SAML	Asks for the SAML Metadata URL and Entity ID.
OIDC	Asks for the OIDC Issuer.

Credentials are stored encrypted. When you edit a connector later, secret fields show a placeholder telling you to leave them blank to keep the current value — they are not read back to you.

Use a dedicated service account on the other system rather than a person’s credentials. A connector built on somebody’s own account stops working the day they leave, and it grants whatever they happened to have.

Example: HC Corp connecting a learning system uses a service account scoped to course and enrolment data. Using Priya Raman’s own account would give the connector her full access and tie the integration to her employment.

Sync frequency

Option	Description
Real-time	Sync as changes occur.
Hourly	Once an hour.
Daily	Once a day.
Weekly	Once a week.
Manual	Only when somebody triggers it.

Start on Manual or Daily while you are still checking the field mappings. A real-time connector with a wrong mapping propagates the mistake continuously, and unwinding it is far more work than the sync saved.

Field mappings

A mapping says which field in the other system becomes which field in Humavera. The wizard notes that mappings are what transform external fields into Humavera fields; with none, there is nothing to transform.

Get these right before you raise the frequency. A mapping error writes bad data into employee records on every run, and each run makes it look more like the truth.

Example: mapping an external system’s employee reference onto the wrong Humavera field at HC Corp does not fail. It succeeds, repeatedly, and the records look populated.

Testing comes after creation

The wizard states it: Test Connection becomes available on the connector detail page after creation. You cannot test from inside the wizard.

So create the connector, then open it and test. A connector that saves cleanly has told you nothing about whether the credentials work.

Managing a connector

Option	Description
Test connection	Checks the credentials and reports the response time.
Sync now	Runs a sync immediately.
Activate / Deactivate	Turns the connector on or off without deleting it.
Edit	Change the configuration and mappings.
Delete	Removes the connector. The interface states this cannot be undone.

Deactivate rather than delete when you are unsure. A deleted connector takes its configuration and mappings with it.

The detail page also carries Overview, Mappings, and History tabs, where history is the record of sync runs and what each one moved.

What happens next

An active connector syncs on the frequency you set, and each run appears in its history and on the data sync page. Trigger a first sync manually and read what it created, updated, skipped, and failed before letting a schedule take over.

Some connectors report that no sync adapter is configured for the provider. Where that is the case, the connector holds its configuration and credentials but data synchronisation is not available for it.