ormuz
Home/Integrations/Bridge/Nodes/Ensure user (Bridge)
BridgeConnecteurStable

Ensure user (Bridge)

Creates or reuses the Bridge user associated with an Ormuz contact for bank-aggregation features.

Vue d’ensemble

Ensure Bridge user establishes the Bridge identity of a contact once and reuses it in later banking operations.

The process designer therefore works with an Ormuz contact and typed bridge_user object without having to store or search for a Bridge UUID manually.

  • An existing mapping is reused and returns created = false.
  • When no mapping exists, Ormuz creates the Bridge user and associates its UUID with the contact.
  • The bank-authorization token is neither created as an output nor retained in the process.

Process example

Contact Ormuz
Créer ou réutiliser un utilisateur (Bridge)
User Bridge + extension_object_mapping

Exemple simplifié d’utilisation de Créer ou réutiliser un utilisateur (Bridge) dans un processus Ormuz.

Data resolution

The node applies the following rules from the supplied objects and filters.

DataSource or rule
Contact canoniquecontact.id.
Default external referencecontact.id when external_user_id is not supplied.
Existing userBridge user → contact mapping for the active configuration.
Created userNew Bridge User only when no association exists.

Parameters 3

Contexte principal

Objects and configuration that determine the Bridge operation.

extension_config_idRequisref(extension_config:bridge)
Active Bridge configuration used for this operation. It determines the Bridge API credentials and environment; the merchant remains the merchant of the current process.
contactRequisContact
Ormuz contact to associate durably with a Bridge user. This contact represents the person whose bank connections and aggregation data will be accessed.

Payer or user identity

Information used to identify the person or company interacting with Bridge.

external_user_idOptionnelstring
Optional external reference used when creating the Bridge user. If absent, Ormuz uses the contact identifier, providing a stable, reusable reference.

Outputs 3

Banking data

Bank-aggregation or verification objects available to subsequent steps.

bridge_userBridge user
Bridge user representing the Ormuz contact for bank-aggregation and account-verification operations.

Session and traceability

Session identifiers, mappings, and creation indicators.

extension_object_mappingextension object mapping
Traceability link between the primary Bridge object produced by the node and the Ormuz object with which it is associated.
createdboolean
Whether the node created a new Bridge object. false means an already-associated object was found and reused.

Behavior

Look for the mapping

The node checks whether the contact already has a Bridge user for this configuration.

Reuse or create

The existing user is reread; otherwise a new Bridge user is created with the selected external reference.

Tracer l’association

The mapping to the contact is returned with the created indicator.

Limits and responsibilities

  • external_user_id may contain only letters, digits, -, or _ and must not exceed 128 characters.
  • Multiple Bridge users mapped to the same contact are treated as ambiguous and are not resolved automatically.
  • The node does not connect any bank; it only prepares the Bridge identity required by subsequent actions.

Troubleshooting

external_user_id rejected

Use a reference of 1 to 128 characters containing only letters, digits, hyphens, and underscores.

Multiple users for the same contact

Fix the relevant Bridge mappings instead of arbitrarily choosing a user in the process.

Reference

ParameterRule
external_user_id absentUtilise contact.id.
external_user_id fourniMust match [a-zA-Z0-9-_]{1,128}.