Get linked platform object
Resolves exactly one platform object linked under a key and routes according to whether a target exists.
Object(s) + key
Get linked platform object
Lien custom
Resolved relationship
Vue d’ensemble
Resolves exactly one platform object linked under a key and routes according to whether a target exists.
Exemple
Retrieve the invoice explicitly linked to a case under related_invoice, then follow a different branch when no link exists.
Key point A custom link expresses an explicit association but changes neither authority nor lifecycle of linked objects.
Decision routes
foundLink found
A compatible target was resolved.
Recommended actionContinue with the object exposed by the route.
not_foundNo usable link
No compatible target is available for the requested key and type.
Recommended actionHandle absence explicitly or create the expected link before retrying.
Parameters 3
object
Source object from which links must be read or removed.
key
Stable business key naming the custom relationship. It isolates this relationship from other links between the same objects.
expected_type
Expected target type. It bounds resolution and determines output type when the node returns a platform object.
Outputs 2
selected_route
Route chosen according to link resolution:
found or not_found.object
Resolved linked object with the type determined by node configuration.
Behavior
The expected type derives the output type. The found route exposes the object; not_found lets the process handle absence without error.
Limits and responsibilities
- Custom links do not replace canonical business-model relationships when those exist.
- Creating a link grants no additional right over the target and transfers no business authority between objects.
- Operations affect only links that exactly match the configured key and criteria.