ormuz
Home/Orchestration/Nodes Core/Request approval
RouteurStable

Request approval

Resolves approvers among a company's contacts, emails them a request, and suspends the process until an aggregated decision is reached.

Destinataire + contenu
Request approval
request_approval
4 routes

Vue d’ensemble

Resolves approvers among a company's contacts, emails them a request, and suspends the process until an aggregated decision is reached.

Exemple

Request approval from a certified legal representative before releasing a high-risk order.

Decision routes

approved

Approved

The approval policy is satisfied.

Recommended actionContinue on the authorized business path.
rejected

Rejected

The approval request was rejected according to received decisions.

Recommended actionHandle the rejection or request a new decision according to your policy.
expired

Expired

The request was not resolved before its deadline.

Recommended actionRemind or escalate if the business case permits it.
no_eligible_approver

No eligible approver

No contact satisfies the configured role, certification, or conflict criteria.

Recommended actionCorrect targeting or route to administrative review.

Parameters 15

companyRequisCompany
Company whose contacts are considered potential approvers.
requestorOptionnelContact
Contact initiating the request, used to apply the conflict policy with approvers.
role_typesRequisenum[]
Accepted contact roles for resolving eligible approvers.
certification_levelsRequisenum[]
Minimum or accepted certification levels for approvers.
selection_strategyRequisenum
Selection strategy used when multiple contacts meet the criteria.
approval_modeRequisenum
Aggregation mode for a simple request when multiple eligible approvers are contacted.
requestor_conflict_policyOptionnelenum
Rule applied when a requester is also among the eligible approvers.
mailerRequisref(extension_config)
Email configuration utilisé pour cette opération de communication.
approval_titleRequisstring
Approval title utilisé pour cette opération de communication.
email_subjectRequisstring
Subject of the approval email sent to resolved contacts.
email_bodyRequisstring
Approval message body. It may contain the action link generated for the approver.
approval_markdownRequisstring
Business context presented to the approver before the decision.
waiting_markdownOptionnelstring
Message displayed while the human decision is still pending.
expires_inRequisduration
Validity period of the temporary access or approval request.
rejection_reason_requiredRequisboolean
Whether a justification is required when an approver rejects the request.

Outputs 11

statusenum
Current normalized state of the mailing, approval, or verification.
selected_routeenum
Business route selected from the observed state or decision.
decided_atdatetime
Date and time at which the approval request was resolved.
expires_atOptionneldatetime
Expiration date and time of the access or request.
reasonOptionnelstring
Decision reason when provided.
contacted_approversContact[]
Contacts actually requested to approve.
requestor_conflict_detectedboolean
Whether a requester/approver conflict was detected.
excluded_approversContact[]
Eligible contacts excluded by the conflict policy.
approval_requestOptionnelApproval request
Canonical approval request created to track the human decision.
approverOptionnelContact
Contact who resolved the simple request when available.
decisionOptionnelApproval assignment
Approval decision that resolved the simple request.

Behavior

The node selects contacts by roles, certifications, and strategy, applies the conflict policy with the requester, creates an approval request, and resumes when the first or first_decision policy is satisfied.

Limits and responsibilities

  • Email is only the solicitation channel; the canonical decision lives in the approval request.
  • An eligible approver must be selected according to an explicit role policy.
  • Self-approval must be possible only if your conflict policy allows it.