Charlie Blomkvist
Yes, monday.com can be connected to Oneflow, the Swedish platform for creating, signing and managing digital contracts. With the integration, a contract or proposal is created in Oneflow from the deal in monday.com, with names, dates and attachments from the item, the status in monday.com updates when the contract is sent, opened and signed, and the signed contract ends up on the right item. We have built a ready-made integration that is listed in Oneflow's partner marketplace, and for flows that need to do more, the integration is built in an integration platform like Make. This article covers what the integration does, how it is built and what to consider before you get started.
- The rep clicks Create contract on the deal in monday.com
- The contract is created from a Oneflow template with customer, contact person, price and attachments from the deal
- Router · Reviewed first?YesThe contract stays as a draft in OneflowNoThe contract is sent straight to the customer
The details are pulled from the deal, so nothing is typed in twice.
- The contract is sent from Oneflow
- The customer opens the contract
- Router · Signed?YesStatus Signed and the date are set in monday.comNoA task for the rep to follow up
The rep sees in monday.com where the contract stands without logging in to Oneflow, and contracts that get stuck are caught.
- All parties have signed
- The signed PDF is saved in the file column on the deal
- The project is created on the project board with start and end dates from the contract
The project manager gets a project with the right details and the contract close at hand.
- The candidate is set to Offer on the recruitment board
- The employment contract is created from the HR template with name, role, salary and start date
- The contract is sent to the candidate
- Onboarding starts once the contract is signed
The same integration works for HR, and onboarding begins without anyone having to announce it.
The flows above are only examples of how it can work. Every integration is built around your process: which steps to include, what should happen in each situation and who is responsible for what.
Short answer
monday.com has no built-in Oneflow integration, and Oneflow has no app of its own in the monday.com marketplace. There is, however, a ready-made integration that we at Straviont, formerly SOLO SAP, have built and that is listed in Oneflow's partner marketplace: with one click on the item in monday.com, the contract is created in Oneflow, details and attached PDF files come along, and the events sent, opened, updated and signed flow back to the board. When the flow needs to do more, for example start projects or create the customer in the finance system, the integration is built in Make or Zapier, or directly against the Oneflow API.
What the integration can do
Here are four common examples. Your integration can do more, less or something entirely different, depending on how you work.
The contract is created in Oneflow from your template when the rep clicks on the item or when the deal reaches the right status. Customer, contact person, price, dates and attached PDF files are pulled from the columns in monday.com.
The contract can stay as a draft in Oneflow until someone has reviewed it, or be sent straight to the customer. Which applies can depend on contract type or amount.
When the contract is sent, opened, updated and signed, the event is brought into status and date columns in monday.com.
A signed contract can create the project, add the customer to the finance system or kick off onboarding. We describe how the invoice is then created in monday.com and Fortnox: how the integration works, using the Swedish accounting system Fortnox as the example.
Why connect monday.com and Oneflow?
- Shorter time from yes to signature. The contract is created in seconds from the deal, instead of whenever the rep has time to put it together.
- Fewer errors in contracts. The details come from the item in monday.com and are not typed in again.
- Sales, HR and delivery see the same thing. Whoever owns the item sees in monday.com whether the contract is signed, and the next step can begin without anyone asking.
- Contracts in one place. The signed contract sits on the item in monday.com and in Oneflow, not in a single user's inbox.
How the integration is built
There are three ways to build it, and which one fits depends on how advanced the flow is.
| Option | Best when | Keep in mind |
|---|---|---|
| Ready-made integration in Oneflow's partner marketplace | You want to create contracts from the item in one click and see status on the board, for sales or HR | Quick to get started and built for monday.com, but the flow ends on the board. Requires a Oneflow plan with API access |
| Make or Zapier | The contract should be created automatically on a status, or move on to projects, file storage and finance | Zapier has its own Oneflow app. In Make, the Oneflow API is called directly or through a community-maintained app. Requires a well-designed flow and error handling |
| Custom code against the Oneflow API | Large volumes or unusual requirements the platforms cannot handle | The most flexible, but requires someone to own and maintain the code |
For many companies, the ready-made integration is enough, and as the flow grows, Make is the right choice. But the platform is just the tool. What determines whether the integration holds up is how it is built: how the columns in monday.com map to data fields, products and parties in the Oneflow template, how the flow handles exceptions such as declined contracts and changed terms, and what happens when something goes wrong. An integration that works in a test but silently misses a status in production costs more than it saves. That is why we build with logging and alerts from the start, and manage the integration as the process or the systems change.
What to decide before you build
An integration is never better than the process it automates. These questions determine whether it works in practice:
- What should create the contract? A button on the item, a status on the deal or an approval. Decide exactly which event in monday.com creates the contract, and who is allowed to trigger it.
- Which template and which fields? The Oneflow template needs data fields for what will be pulled from monday.com, and the columns must be filled in before the contract is created.
- Review or send directly? Should every contract be reviewed in Oneflow first, or can standard contracts below a certain amount be sent directly?
- What happens once the contract is signed? Just a status, or should the project be created, the customer added to the finance system and the PDF saved in your file storage?
- What happens when something goes wrong? A good flow logs every run and flags when a contract could not be created, instead of silently skipping it.
Oneflow and monday.com share the contract process
Oneflow is built for the contract: the template, the content, the signing and the archive. monday.com is built for the deals, the candidates and what happens before and after the contract. The integration lets each tool do what it does best, with the deal in monday CRM or the candidate on the recruitment board in monday work management owning the data. If you use DocuSign, GetAccept or PandaDoc instead, read more in monday.com and DocuSign, monday.com and GetAccept and monday.com and PandaDoc.
Straviont builds the integration
We are an official monday.com partner and certified CRM specialists with monday.com, and we built the ready-made integration between monday.com and Oneflow that is listed in Oneflow's partner marketplace. When the flow needs to do more, we build it in Make. We start with the process: what should create the contract, which details must be in place and what should happen once it is signed. Only then is the flow built, with logging and error handling, and we manage it as your business changes. You can find more systems we connect to monday.com under all integrations.
Frequently asked questions
Can monday.com be connected to Oneflow?
Yes. There is a ready-made integration in Oneflow's partner marketplace, built by us at Straviont, that creates contracts in Oneflow in one click from monday.com and brings the status back. For flows that need to do more, the integration is built in Make or Zapier, or with custom code against the Oneflow API.
Can a contract be created automatically from a deal in monday.com?
Yes. The integration can create the contract from your Oneflow template when the rep clicks on the item or when the deal reaches a certain status. Names, dates, price and attached PDF files are pulled from the columns, and the contract can be sent directly or reviewed first.
Can we see in monday.com when the customer has signed?
Yes. When the contract is sent, opened, updated and signed, the event can be brought into status and date columns in monday.com, and the status can drive the next step.
Does the integration work for employment contracts?
Yes. The same integration can be used from a recruitment board, where the candidate's details fill in the HR template in Oneflow and the signed contract starts onboarding in monday.com.
What do we need in Oneflow to connect the systems?
A Oneflow plan with API access, which is not included in every plan, and a user with access to the templates that will be used.
Should we choose the ready-made integration or Make?
The ready-made integration is enough when you want to create contracts from the item and see status on the board. Make fits when the contract should be created automatically on a status, when the status should drive the next step, or when the contract should move on to projects, file storage and the finance system.
Next steps
Start by describing the flow from deal to signed contract: what creates the contract, which template is used, whether it should be reviewed first and what should happen afterward. From there, building it goes quickly. If you want help, you can book a free mapping session and we will go through it together.