ERP
Oracle, SAP, Odoo and more.
Integrations
WQ3 integrations
Connect WQ3 to ERP, HR, CRM, productivity and storage systems, or build a custom integration.
Categories
HR
Employee lifecycle documents.
CRM
Sales contracts from your pipeline.
Productivity
Work where your documents are.
Storage
Keep signed copies where you need them.
Custom
Scoped per agreement through the API.
Integrations are scoped and enabled per agreement.
Integration pages
Oracle
Send documents from Oracle business processes for signature and return the signed result.
SAP
Connect SAP business processes to WQ3 signing workflows.
Odoo
Send Odoo documents for signature through WQ3.
How integrations work
Send documents from your system to WQ3, let the parties sign, then get the signed copy and status back in your system automatically.
ERP systems
SAP, Oracle and Odoo.
Any other system
Through the WQ3 API and webhooks.
Agreed scope
Each integration is planned with your technical team.
Define the signing handoff in your business process
Start with the point at which a document becomes ready for signature, rather than with the application you want to connect. Identify which internal approvals must happen first, who may initiate sending, and which approved document version should reach the signers. This matters because WQ3 locks documents once they are sent, so content review should happen before that handoff.
Plan how the document will remain associated with the correct employee, sales opportunity or business transaction in your system. Discuss the reference used to make that connection, the information needed to start the request, and the destination for the completed copy. These are integration design decisions, not assumptions about a universal set of supported fields.
Plan requirements for each signer
Make signing requirements part of your workflow design rather than a decision left until development is complete. Everyday agreements may use electronic signature, while formal or high-value contracts may call for remote signing or token signing. WQ3 allows different levels for different signers in the same document, so your planning should account for every party involved.
Keep account identity verification separate from the choice of signature level. The eKYC add-on verifies the account holder and can be required with any of the three levels; it is not a fourth level. Before implementation, document the requirements for each signer category and review how those choices will be handled within the agreed integration.
Plan to retain signing evidence alongside the document
Your record-keeping plan should cover evidence of completion, not just the final file. Every completed WQ3 document comes with an audit trail and completion certificate recording the actions taken. Decide what your team needs to retain, how it should relate to the original business record, and who needs access for internal review or a later dispute.
Consider verification after the signing workflow has ended. WQ3’s public check page allows a contract’s authenticity to be checked without an account, using its QR code, reference and file fingerprint. Discuss how those references will remain accessible with stored copies, and confirm that the agreed integration scope covers the evidence-handling approach your organisation needs.
Test the complete workflow before launch
Prepare representative test scenarios before accepting an integration for everyday use. Check that the correct document is selected, invitations reach the intended signers, and the completed result is associated with the right business record. Include documents with different signing requirements or verified-account requirements wherever those are part of your planned scope.
Also define responsibilities when a handoff does not complete as expected. Agree who investigates, how duplicate or delayed updates should be handled, and what information your team needs to trace a problem. These are implementation questions to resolve, not claims about specific retry mechanisms or delivery guarantees; clear ownership makes operational issues easier to address.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
What should we prepare for an integration discussion?+
Bring a sample document, the proposed sending trigger, signer roles, required signing levels, and the business record that should receive the result.
Must every signer use the same level?+
No. WQ3 supports different levels for signers in the same document. Discuss how that selection will be handled within your integration scope.
Is eKYC an additional signing level?+
No. It is an account-verification add-on that can accompany electronic signature, remote signing or token signing.
What evidence should our storage design consider?+
Consider the audit trail and completion certificate alongside the signed document. Confirm how this evidence will be retained and linked during scoping.
Does a recipient need an account to verify a completed contract?+
No. WQ3’s public check page supports authenticity checks without an account, using the contract’s QR code and reference.