The Oneflow integration allows you to create, send, track, and e-sign your contracts from your favorite business tools and systems.
While the platform gives you full freedom to build almost any workflow, the documentation is split into three levels of integrations. Each level building on the previous one:
- Standard - custom client integration
- Application - custom integration with a specific application
- Partner - generic integration with a partner and their tool or application.
Standard integrations are account-specific integrations that aim to solve a specific use case. Often, most or all of the required data in the standard integration are hardcoded or automatically fetched without user interaction.
Examples of standard integrations include creating contracts via a webform or as part of the signup process.
Standard integration is also a good place to get started if you are new to the Oneflow integration platform and want to explore its possibilities.
Application integrations are account-specific integrations that connect Oneflow with an external application or system. While some data might be hardcoded, most required data is dynamically collected or selected by the end-user via a UI.
Examples of application integrations include integrating your CRM or ATS with Oneflow to create contracts based on information in those systems.
Partner integrations are generic application integrations that easily allow any account to enable integration between Oneflow and an external system. These integrations rely almost entirely on dynamic data collected from the system or the user.
Examples of partner integrations include integrations with Salesforce, Dynamics, and Hubspot.
Updated over 1 year ago