Home | Connectors | OpenText Core Signature | OpenText Core Signature - ServiceNow Integration and Automation
OpenText Core Signature and ServiceNow complement each other well in enterprise workflows where service requests, approvals, and legally binding signatures must be coordinated across departments. ServiceNow manages the workflow, case, and approval process, while OpenText Core Signature provides secure electronic signature execution for documents that require formal authorization.
Data flow: ServiceNow to OpenText Core Signature, then back to ServiceNow
When HR opens an onboarding case in ServiceNow, the system can automatically generate and route employment documents such as offer letters, policy acknowledgements, tax forms, and confidentiality agreements to OpenText Core Signature for signing. Once signed, the executed documents are returned to ServiceNow and attached to the employee case for audit and recordkeeping.
Data flow: ServiceNow to OpenText Core Signature
For high-risk IT requests such as privileged access, software procurement, hardware exceptions, or production changes, ServiceNow can trigger a signature request in OpenText Core Signature after the request reaches approval stage. The signed authorization is then used as evidence before fulfillment proceeds.
Data flow: ServiceNow to OpenText Core Signature, then back to ServiceNow
Procurement teams can manage vendor onboarding, purchase approvals, and contract review in ServiceNow while sending final contract documents to OpenText Core Signature for execution. After all parties sign, the completed agreement is stored in the ServiceNow procurement or vendor record.
Data flow: ServiceNow to OpenText Core Signature, then back to ServiceNow
ServiceNow can orchestrate onboarding cases for customers, partners, or third-party service providers that require signed terms, service agreements, or compliance acknowledgements. OpenText Core Signature handles the signature collection, and the signed documents are returned to the onboarding record for operational teams to continue setup.
Data flow: ServiceNow to OpenText Core Signature, then back to ServiceNow
ServiceNow can launch recurring compliance workflows for employee policy acknowledgements, code of conduct attestations, security training confirmations, or regulatory declarations. OpenText Core Signature captures the signed acknowledgement, and ServiceNow tracks completion status, reminders, and exceptions.
Data flow: Bi-directional
For facilities requests such as lease approvals, space changes, access agreements, or maintenance authorizations, ServiceNow can manage the request and approval workflow while OpenText Core Signature captures formal signoff on documents that require legal or executive approval. Status updates from the signature process can be reflected back in ServiceNow to keep stakeholders informed.
Data flow: ServiceNow to OpenText Core Signature, then back to ServiceNow
ServiceNow can manage legal, risk, or internal investigation cases that require signed settlement letters, remediation commitments, or acknowledgment of corrective actions. OpenText Core Signature handles the signature process, and the signed outcome is attached to the case for closure and compliance evidence.
These integrations are most valuable when ServiceNow acts as the workflow and case management layer, while OpenText Core Signature provides the trusted signature layer for documents that require formal approval, acknowledgment, or legal execution.