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 a Oneflow integration?

Oneflow is a European Contract Lifecycle Management platform that covers the full lifecycle of contracts: drafting, negotiating, signing, archiving and renewing. Where many e-signature tools stop as soon as a PDF is signed, Oneflow treats a contract as a living document that evolves with changes, approvals and renewals. Both parties can collaborate in real time in the same interactive contract workspace.

In practice, a custom integration means: 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 according to the official Oneflow developer documentation and the OWASP ASVS security standard. We tailor templates, workflow logic and error handling to your actual contract processes, so the integration grows with your organisation and contracts keep flowing reliably even at peak volumes.

Interactive contracts

Contracts are not a static PDF but a live workspace in which both parties can read, comment, propose edits and sign in real time. Changes are visible inline with an 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 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-sign, SMS OTP or strong identification via BankID, Smart-ID or iDIN, depending on the level of legal certainty you need. For employment contracts, vendor agreements or legally sensitive deals, the appropriate level is 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 & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.

What a 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 deliver most often for organisations that use Oneflow as the contract backbone for HR, sales or procurement.

Contracts from your CRM or HR system

Integration with HubSpot, Salesforce, Pipedrive, Upsales or SuperOffice on the sales side, and 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 are populated 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 draw up contracts at speed within those boundaries.

Approval workflows

For contracts above a threshold amount, with non-standard terms or risky clauses: automatic routing to a manager, legal, finance or the board for approval before the contract goes to the counterparty. With escalation when deadlines are exceeded and a full audit trail.

Multi-party signing and BankID

Signing by multiple parties in a fixed or parallel order, each with an appropriate identification level. Standard e-sign 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 or 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.

Extensions and renewals

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 buried in Excel lists.

Typical use cases in practice

A Oneflow integration looks very different from one organisation to the next. We see a number of patterns come up again and again, and for each of them we have a working setup that covers templates, integrations with source systems and the right approval and identification logic.

CRM

HR & recruitment

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

Sales with a contract lifecycle

B2B sales teams that want to do more than get a proposal signed and keep managing the whole contract, including amendments, renewals and price adjustments. Integration with HubSpot, Salesforce, Upsales or SuperOffice so that 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 in one place. Approval workflows route through procurement, finance, legal and the budget holder depending on amount and risk. One central repository for all vendor contracts, with searchable data fields and alerts for expiring contracts.

Legal & compliance teams

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

Technology we use

We build Oneflow integrations with the official REST API and webhooks, combined with the backend stack that suits you. The exact choice depends on your CRM/HR source systems and identification requirements, so that 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 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, because an integration must not only be technically sound but also add practical value to the way you work.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but 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. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around API integrations, middleware, custom software and web app development.

  • Experience with the Oneflow REST API, templates and data fields
  • Specialist in CRM and HR integrations (HubSpot, Salesforce, AFAS, Personio)
  • Familiar 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
  • Extensive logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive further development
  • An approach tailored to your existing IT landscape

Security and privacy in Oneflow integrations

Contracts always contain personal data or commercially sensitive information, especially HR and vendor contracts. Appfront builds in line with Oneflow security best practices and the OWASP ASVS. Among other things, that means API keys in secure vaults, HMAC webhook signature validation, scoped OAuth permissions and regular audits of contract and identification flows.

Oneflow is itself ISO 27001 and GDPR compliant, hosts data exclusively in the EU (the Netherlands and Sweden) and records a complete audit trail for each contract, with 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 demonstrably comply with the GDPR. The audit trail serves as legal evidence for every signature.

More about our approach to security: information security policy and CVD policy.

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

Frequently asked questions about Oneflow integrations

Answers to the questions we get asked most often 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 entire contract lifecycle: not just signing, but also drafting, negotiating, amending and managing. It is strong in HR/employment contracts, sales agreements, vendor contracts and NDAs. It is a European SaaS with 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. We will advise on what suits your use case.

A simple integration, creating one contract template from your CRM or HR system and using 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/HR integration generally take longer. After an intake conversation, we will 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-sign and eIDAS-compliant methods such as BankID, SMS OTP and identification-based signatures.

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. Ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation.

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

Yes. Appfront regularly takes over the maintenance of existing Oneflow integrations, even when 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 draft improvement proposals. From then on we can handle changes, extensions and monitoring, including timely API key rotation.

Oneflow suits organisations for which contracts are 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: onboarding new employees through contracts from Workday or AFAS, sales agreements from HubSpot or Salesforce, vendor contracts with approvals, and a central contract repository for compliance. Strong for organisations with European data residency requirements or BankID users.

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 per contract type. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.

Edit content