Process Hub · Connections and lookup sources
How to create connections and inbound bindings
Connect an approved source and map it into a deployed process.
On this page
Before you start
- Have Manage connections access, a deployed target process and an approved source. Emplyr Connector sources must be granted to the profile by an instance admin. Agree stable record keys and create/update behaviour before importing.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open Settings → Process Hub → Connections. On Connections, select Add connection and choose Emplyr Connector, REST API or Webhook as appropriate.
- Select the approved connector/database source or configure the provider/authentication details. Save and Test connection. Keep secret values in the protected input flow, not in notes.

Select the approved provider or connector source, save its protected configuration, and test the connection. - On Bindings, create a binding. In Details select the deployed Process and tested Connection, then name the binding and choose write mode and Import outcome.

Choose the destination process, source connection and write behaviour before continuing to source data and field mapping. - In Source data, select approved tables/views and columns, the record key and change-tracking mode/column. Decide whether Initial import should include existing records or start with new changes only.
- In Mapping, map source columns to the intended process fields. Review required fields, related-line identity and After import ownership. Source controlled fields must match the process’s read-only design.
- Save the draft to keep unfinished work. Use Edit draft to resume the full wizard or Edit mapping for mapping-only changes. Deploy the binding when its validation is ready; saving alone does not activate import.
- Use Activity to check the first event/results and representative records. Correct row/field errors before retrying. Do not redeploy a different write mode just to bypass a duplicate/match error.

Select the intended binding and inspect its events. This example has no activity yet; it does not show a successful import.
What you should see
A deployed binding imports according to explicit keys, mapping and draft/submitted outcome, with traceable activity.
If something goes wrong
No connector source is offered
Ask the instance admin to grant the physical connection to this profile and verify its heartbeat/status.
A mapping references removed fields
Remove obsolete mappings, map replacements and save/deploy a new reviewed version.
Update existing records only finds zero or multiple records
The configured identifier must match exactly one live record (and line when applicable). Correct identity data with its owner rather than creating duplicates.