Contract automation end-to-end CLM eIDAS + BankID

Custom Oneflow integration development

Appfront builds custom Oneflow integrations that automate the entire contract lifecycle, from your CRM, HR platform, ATS or own application. Using the Oneflow REST API and webhooks, we generate data-driven contracts, route approvals and synchronise every status change in real time. You save hours per contract and receive automatic updates in your source systems for every lifecycle event.

What is an Oneflow integration?

Oneflow is a European Contract Lifecycle Management platform covering the full life of a contract: drafting, negotiation, signing, archiving and renewal. Where many e-signature tools stop once a PDF has been signed, Oneflow treats a contract as a living document that evolves with amendments, approvals and renewals. Both parties can collaborate in real time within the same interactive contract workspace.

A custom Oneflow integration means in practice: creating contracts programmatically from a template and data fields from your CRM, HR system or ATS, configuring approval workflows for internal review, logging lifecycle events (sent, changed, signed, renewed) in your data warehouse, and feeding every status change back to the source systems via webhooks, including creating or updating records after signing.

Appfront builds in line with the official Oneflow developer documentation and the OWASP ASVS security standard. We align templates, workflow logic and error handling with your actual contract processes, so the integration grows with your organisation and continues to flow reliably even at peak volumes.

Interactive contracts

Contracts are no longer static PDFs but live workspaces in which both parties can read, comment, propose edits and sign in real time. Changes are visible inline with a full audit trail, so negotiation and legal review run smoothly.

Lifecycle insights

See for each contract when it was opened, by whom, which pages were viewed and where delays occur. Contract managers can see in a single dashboard which contracts are stalling, which are expiring and which are ready for renewal, exactly when action is needed.

€

eIDAS-compliant signing

Standard e-signature, SMS OTP or strong identification via BankID, Smart-ID or iDIN, depending on the legal certainty you need. For employment contracts, vendor agreements or legally sensitive deals, the appropriate level can be set automatically per template.

Our development process for Oneflow integrations

We work to a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your contract processes, templates and CRM/HR integration through to go-live and ongoing maintenance, every step is aimed at an integration your own team can understand and trust.

1
Analysis & scope

We map out which contract types you want to automate, which data comes from which source system, which approval and identification logic applies to each type, and which lifecycle events matter for your reporting.

2
Architecture

We design the integration architecture, choose the right authentication and draw up an error-handling strategy.

3
Development

Implementation with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & management

Controlled go-live with data validation and a safety net, followed by ongoing management and further development.

What an Oneflow integration delivers in practice

Every Oneflow integration is set up specifically for your contract types, workflows and adjacent systems. Below are the features we most often deliver for organisations using Oneflow as the contract backbone for HR, sales or procurement.

Contracts from CRM or HR

Integration with HubSpot, Salesforce, Pipedrive, Upsales or SuperOffice on the sales side; Teamtailor, Workable, AFAS or Personio on the HR side. Deal or candidate data flows automatically into the right contract, including secondary terms and role-specific clauses.

Template library with data fields

A central library of approved contract templates, data fields that populate automatically, conditional content (show clause X only for contract type Y) and groups for role-based fields. Legal keeps control over permitted clauses, while sales and HR draft contracts quickly within that framework.

Approval workflows

For contracts above a threshold amount, deviating terms or high-risk clauses: automatic routing to a manager, legal, finance or the board for approval before the contract goes to the counterparty. Includes escalation when turnaround times are exceeded and a complete audit trail.

Multi-party signing and BankID

Signing with multiple parties in fixed or parallel order, each at an appropriate level of identification. Standard e-signature for internal documents, SMS OTP for regular contracts, and BankID or Smart-ID for employment agreements and legally sensitive deals, all eIDAS-compliant.

Lifecycle events to source systems

Every status change (contract created, sent, opened, amended, signed, archived, expired) is passed on via webhooks. CRM opportunities move to closed-won, HR systems create the new employee record, and data warehouses keep a complete timeline for compliance and reporting.

Renewals and extensions

Contracts with an end date are monitored automatically: reports on expiring contracts, automatic renewal contracts based on existing data, and notifications to the right contract owner well before expiry. No more missed renewals tracked in spreadsheets.

Typical use cases in practice

An Oneflow integration looks very different from one organisation to the next. We see a number of recurring patterns, and for each of them we have a working setup, with attention to templates, integration with source systems and the right approval and identification logic.

CRM

HR & recruitment

Larger employers and scale-ups that send many employment contracts, NDAs and addenda. Integration with ATS (Teamtailor, Workable, Recruitee) and HRIS (AFAS, Personio, Workday) so candidates and employees automatically get the right contract template, with BankID or Smart-ID for legal certainty. See also our API integrations.

Sales with contract lifecycle management

B2B sales teams that want to do more than sign a proposal and instead manage the entire contract, including amendments, renewals and price changes. Integration with HubSpot, Salesforce, Upsales or SuperOffice so deals automatically trigger the right contract template and renewal events flow back into the pipeline.

Procurement and vendor management

Procurement teams that want to manage vendor agreements, purchase orders, SLAs and DPAs centrally. Approval workflows route through procurement, finance, legal and budget holders depending on amount and risk. A single central repository for all vendor contracts, with searchable data fields and alerts for expiring contracts.

Legal and compliance teams

Legal teams who structure NDAs, partner agreements and licence contracts via Oneflow. Template governance lets non-lawyers create contracts within agreed parameters, with alerts for deviations. EU data residency and complete audit trails make compliance with GDPR and contract audits demonstrable.

Technology we use

We build Oneflow integrations using the official REST API and webhooks, combined with the backend stack that suits you. The precise choice depends on your CRM/HR source systems and identification requirements, so your own team can manage or further develop the implementation.

Oneflow REST API Oneflow webhooks OAuth 2.0 / API keys Contracts, Templates & Workspace API Node.js / Python / PHP / .NET / Ruby / Go HubSpot & Salesforce connectors Upsales / SuperOffice / Pipedrive Teamtailor / Workable ATS AFAS / Personio / Workday HR Data fields & conditional content Approval workflows BankID / Smart-ID / iDIN eIDAS SES / AES / QES Lifecycle event streaming HMAC webhook validation GitHub Actions

Why choose Appfront for your Oneflow integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes. An integration should not only work technically, but also add practical value to the way you work.

For every integration, we write clear documentation and make sure your own team, or any future supplier, can understand and manage it. No black box, just transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.

See also our wider services around API integrations, middleware, custom software development and web app development.

  • Experience with the Oneflow REST API, templates and data fields
  • Specialists in CRM and HR integrations (HubSpot, Salesforce, AFAS, Personio)
  • Experienced with eIDAS, BankID, Smart-ID and multi-party signing
  • Secure by default: API key rotation, webhook signature validation, scoped permissions
  • Structured error handling and retry mechanisms
  • Comprehensive logging and monitoring from day one
  • Clear documentation your team can read and manage
  • A fixed point of contact, no account managers passed around
  • Ongoing maintenance and proactive further development
  • A way of working aligned with your existing IT landscape

Security and privacy in Oneflow integrations

Contracts always contain personal data or confidential business information, particularly HR and vendor contracts. Appfront builds according to Oneflow security best practices and the OWASP ASVS. This includes storing API keys in secure vaults, validating HMAC webhook signatures, using scoped OAuth permissions and carrying out regular audits of contract and identification flows.

Oneflow itself is ISO 27001 and GDPR compliant, hosts data exclusively within the EU (the Netherlands and Sweden), and records a complete audit trail for each contract, including timestamps, IP addresses and identification method. We document the data flows, templates and identification flows so that your record of processing activities is complete and you can demonstrably comply with the GDPR. The audit trail serves as legal evidence for every signature.

More on our security approach: information security policy and CVD policy.

  • GDPR-compliant data processing and data minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Automatic retries and dead-letter queues
  • Monitoring and alerting for anomalies
  • Secrets management in line with best practice
  • Documentation for your record of processing activities

Frequently asked questions about Oneflow integrations

Answers to the questions we most often receive about Oneflow implementations.

A Oneflow integration is a technical link between Oneflow and another system, such as your CRM, HR platform, ATS or own application. Using the Oneflow REST API and webhooks, digital contracts are created programmatically from templates, populated with data fields from your source systems, and synchronised in real time throughout the entire lifecycle: from drafting and negotiating to signing, archiving and renewal. An integration can be simple (automatically creating a single employment template from your ATS) or complex (approval workflows, multi-party signing with BankID and lifecycle analytics sent to your data warehouse).

Oneflow suits organisations that want to automate the full contract lifecycle, not just signing but also drafting, negotiating, amending and managing. It is strong for HR and employment contracts, sales agreements, vendor contracts and NDAs. As a European SaaS product, it offers EU data residency and eIDAS-compliant signing, including BankID. For pure proposals with CPQ and in-document payments, PandaDoc is often a better fit; for purely legal e-signing, DocuSign may be preferable. We advise on what fits your use case.

A simple integration, such as creating one contract template from your CRM or HR system and webhooks for status changes, can go live within a few weeks. More complex scenarios with multiple templates, approval workflows, multi-party signing, lifecycle events in your data warehouse and deep CRM or HR integration usually take longer. After an intake conversation, we give you a realistic estimate.

We work with the official Oneflow REST API and webhooks, combined with the backend stack that suits you — Node.js, Python, PHP, .NET, Ruby or Go. Authentication runs via API keys or OAuth 2.0. For automation we use templates with data fields, conditional content and groups. For signing we support both standard e-signature and eIDAS-compliant methods such as iDIN-style identity verification, SMS OTP and signatures based on identification.

The cost depends on the complexity of the contract templates, the number of systems to integrate (CRM, HR, ATS, ERP), the approval and lifecycle logic you need and the amount of custom work involved. Ongoing management, monitoring and support also affect the total investment. We always provide a clear quote following a no-obligation analysis of your situation.

Yes. Oneflow is ISO 27001 and GDPR compliant, hosts data within the EU (the Netherlands and Sweden), and records a complete audit trail for each contract, with timestamps, IP addresses, the identification method and all changes throughout the lifecycle. Appfront builds to the OWASP ASVS: API keys held in secure vaults, HMAC webhook signature validation, scoped OAuth permissions and strictly separated rights per workspace. We document the data flows so that your record of processing activities remains complete.

Yes. Appfront regularly takes over existing Oneflow integrations, even where they were originally set up by another party. We review the API integrations, template configuration, webhook flows and error handling, document the current setup and propose improvements. From that point on, we can handle changes, extensions and monitoring — including timely API key rotation.

Oneflow suits organisations that see contracts as a core process — HR departments with many employment agreements, sales teams with repeat deals, procurement departments with vendor contracts, and legal teams managing NDAs and partner agreements. Typical use cases include onboarding new employees via contracts from Workday or AFAS, sales agreements from HubSpot or Salesforce, vendor contracts with approvals, and a central contract repository for compliance. It is particularly strong for organisations with European data residency requirements or users of iDIN-based identification.

Ready to build your Oneflow integration?

Tell us which contract types you want to automate and which CRM, HR or ATS systems Oneflow needs to integrate with. We're happy to advise on templates, data fields, approval workflows and identification levels for each contract type. A no-obligation first conversation will give you a clear picture of what's possible within half an hour.

Edit content