Home | Connectors | HubSpot | HubSpot - OpenText Core Signature Integration and Automation
Data flow: HubSpot ? OpenText Core Signature ? HubSpot
When a deal reaches the ?Contract Sent? or ?Closed Won? stage in HubSpot, the sales team can trigger an electronic signature workflow in OpenText Core Signature using the customer, deal, and contract details stored in HubSpot. After signing is completed, the signed agreement and audit trail are automatically returned to the HubSpot deal record.
Business value: Speeds up deal closure, reduces manual document handling, and gives sales teams immediate visibility into signature status without leaving HubSpot.
Data flow: HubSpot ? OpenText Core Signature ? HubSpot
For new customers created in HubSpot, onboarding teams can generate and send required documents such as service agreements, terms and conditions, or implementation approvals through OpenText Core Signature. Once signed, the completed documents are attached to the customer record in HubSpot and can trigger the next onboarding step.
Business value: Creates a consistent onboarding process, shortens time to activation, and ensures signed documents are stored alongside customer data for easy access across teams.
Data flow: OpenText Core Signature ? HubSpot
When customers sign consent forms, privacy notices, or marketing authorization documents in OpenText Core Signature, the signed consent status can be synchronized back to HubSpot contact records. This allows marketing teams to segment audiences based on verified consent and communication preferences.
Business value: Improves compliance with privacy requirements, reduces risk of unauthorized outreach, and supports more accurate audience targeting.
Data flow: HubSpot ? OpenText Core Signature ? HubSpot
Organizations using HubSpot to manage recruiting pipelines or employee-related workflows can send offer letters, policy acknowledgments, or onboarding forms to OpenText Core Signature for execution. Signed documents are then linked back to the relevant candidate or employee record in HubSpot.
Business value: Eliminates paper-based HR processing, improves turnaround time for hiring and onboarding, and provides a clear record of completed employment documents.
Data flow: HubSpot ? OpenText Core Signature ? HubSpot
When a customer contract is approaching renewal, HubSpot can automatically create a renewal task and generate the updated agreement for signature in OpenText Core Signature. After execution, the renewed contract is stored in HubSpot and the renewal date, signature completion, and related notes are updated on the account.
Business value: Helps account managers manage renewals proactively, reduces missed deadlines, and keeps contract history centralized for customer success and finance teams.
Data flow: HubSpot ? OpenText Core Signature ? HubSpot
Customer service teams can use HubSpot service tickets or customer records to initiate signature requests for approvals such as change orders, service waivers, escalation approvals, or work authorization forms. OpenText Core Signature handles the signing workflow, and the completed document is returned to the ticket or contact record.
Business value: Accelerates service resolution, improves accountability for customer approvals, and reduces delays caused by manual follow-up.
Data flow: Bi-directional
HubSpot can store metadata such as signer name, signature status, completion date, and document type, while OpenText Core Signature maintains the legally binding signed file and audit trail. This creates a shared view of document lifecycle status across sales, operations, legal, and compliance teams.
Business value: Improves governance, simplifies audits, and ensures teams can quickly verify whether a document has been sent, signed, or is still pending.