Resources · Zapier integration

Oneflow Zapier integrationAutomate Oneflow with Zapier.

The Oneflow Zapier integration gives you 1 trigger, 9 actions and 0 searches. The trigger fires the moment a contract changes status, even on the free plan, and the actions cover the whole contract: create it, fill it, send it, download it, delete it.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Oneflow Zapier integration actually does

It links your Oneflow account to Zapier so that a contract can start an automation, or be built by one. In practice: Oneflow reports each status change to Zapier, and Zapier can create, complete, send, read, download or delete contracts in your account without you opening Oneflow.

Three results come up again and again. A contract built from a deal: Create Contract opens it, Add Participant puts the signer on it, Add Product fills the product table. A contract that leaves on its own: Send Contract mails it to its participants with your subject line and message. A signed copy filed where your team works: Contract Status Changed starts the Zap and Download Contract fetches the PDF for the next step.

Now the limits. There is exactly one trigger, and it watches status changes only. There is no search step either, so a Zap cannot look up a contract by its name: every action that touches an existing contract wants its Contract ID, which has to come from an earlier step. The good news sits on the trigger itself. It is instant, so the free plan gets the same speed as the most expensive one.

If you are still choosing a tool, read Make vs Zapier and n8n vs Zapier before you build anything serious.

Vocabulary

Zapier vocabulary, in plain words

Eight words come back on every line of this page. Here they are once, so the rest reads easily.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One action that your Zap completes successfully counts as one task on your plan.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the unseen ones.
Instant trigger
A trigger the app reports itself, the moment the event happens. Nothing waits for a check. The Oneflow trigger is one.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What a Oneflow Zap really costs

Oneflow is not a premium app, so it works on the free plan. The trigger costs nothing: Zapier only bills an action that went through.

  • Contract Status Changed0 tasks, instant on every plan
  • Each successful action1 task (a few actions take more)
  • Free plan100 tasks a month, Zaps of 2 steps
  • Oneflow on ZapierNot premium, available on Free

Each successful action is one task, and a failed one is not counted. A three-action Zap therefore uses three times what a one-action Zap uses. The catch is the free plan: two steps maximum, one trigger and one action. Add a filter or a second action and the Zap needs a paid plan. The interval grid below concerns polling triggers only; the Oneflow trigger is instant on every plan, so the grid never slows it down.

Connect

Connect Oneflow to Zapier in 3 steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your Oneflow account linked to Zapier once, then reused by every step that needs it.

  2. 02

    Pick Oneflow

    Type Oneflow in the search box of the dialog, select it, then click Add connection. A new tab opens on the Oneflow side, where you sign in with the account the Zaps will act for.

  3. 03

    Grant access

    Allow Zapier to use the account. You need an Oneflow account of your own, plus read or write rights on any contract you do not own and still want a Zap to touch.

First Zap

Your first Zap: file every signed contract

GoalWhen a contract reaches the status you choose, download its PDF and drop it into a shared Google Drive folder.

  1. 01

    Choose the trigger

    Pick Oneflow as the app that starts the Zap, then Contract Status Changed as the event, and select your Oneflow connection.

  2. 02

    Set the status

    Fill in the required box Trigger when contract status changed to with the status that matters to you. Test the trigger: Zapier brings back the three most recent items of your account.

  3. 03

    Add Download Contract

    Add a Oneflow step with Download Contract and map the Contract ID that the trigger brought back. No typing, you pick it from the trigger output.

  4. 04

    Send the file to Drive

    Add Google Drive with Upload File and map the PDF from the previous step. This third step makes it a multi-step Zap, so it runs on a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back before moving on. When every step looks right, click Publish to switch the Zap on.

Triggers

The Oneflow trigger

1 event starts a Zap when something happens in Oneflow, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Contract Status Changed

Instant trigger

In Zapier“Triggers when the contract status is changed.”

Starts your Zap when a Oneflow contract moves to the status you named in the trigger. It is the only door into Zapier from Oneflow, so every automation that reacts to a contract goes through it: a signature to file, a deal to update in your CRM, a teammate to alert.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your sales team wants the signed PDF and the deal update right after the client signs, without anyone checking Oneflow by hand.
Watch out
the status box is required, so one Zap follows one target status; two statuses mean two Zaps.
Actions

The 9 Oneflow actions

Oneflow gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Participant

Action

In Zapier“Add a new participant to a Oneflow contract”

Puts a new person on an existing contract, with the participant type and name you map from earlier steps.

When to use it
the signer is only known after the contract exists, for example once the client fills in an onboarding form.
Watch out
this needs the Contract ID, and Oneflow has no search on Zapier, so the ID must come from the trigger or from Create Contract.
2

Add an Attachment or Expanded PDF

Action

In Zapier“Add an attachment or expanded PDF to a Oneflow contract”

Attaches a file to a contract, either as a plain attachment or as an expanded PDF, depending on the Upload as option.

When to use it
general terms or a technical appendix must travel with every contract of one type.
Watch out
the file, or its public URL, must not exceed 20 MB, and the contract needs an attachment or expanded PDF section to receive it.
3

Add Product

Action

In Zapier“Add product into an existing Oneflow contract”

Writes a product line, with its name and quantity, into a product table of an existing contract.

When to use it
the quote lives in another tool and the contract should list the same items without retyping them.
Watch out
the contract's template must hold at least one product table. You choose which one by its table ID, and tables are numbered from top to bottom in the contract.
4

Get Contract Details

Action

In Zapier“Get details of an existing Oneflow contract”

Reads an existing contract from its Contract ID and hands its details to the steps that follow.

When to use it
the trigger tells you a status moved, and the next steps need more of that contract to update a spreadsheet or a CRM record.
Watch out
on Zapier this is an action, not a search step, so it counts as a task each time it succeeds.
5

Send Contract

Action

In Zapier“Send a contract to Oneflow contract participants”

Sends a ready contract to its participants, with the subject line and message you write in the step.

When to use it
once participants and products are on the contract, the last step of the same Zap can send it out with nobody clicking anything.
Watch out
the subject is capped at 150 characters and the message at 5000; a mapped field that runs longer breaks the step.
6

Create Contract

Action

In Zapier“Create a new Oneflow contract”

Opens a brand new contract in your Oneflow account, created in the name of the Oneflow user you pick in the step.

When to use it
a deal reaches the closing stage in your CRM and the contract should exist before anyone asks for it.
Watch out
the step also asks whether to add an external link to the contract; this answer is required, so decide it once in the setup.
7

Delete Contract

Action

In Zapier“Delete an existing Oneflow contract”

Removes an existing contract from Oneflow, acting as the Oneflow user you select.

When to use it
a deal is marked lost in your CRM and the draft contract tied to it should not linger in the list.
Watch out
the step deletes for real as soon as it runs. Test it on a dummy contract first, and consider a filter so only the right contracts reach this step.
8

Download Contract

Action

In Zapier“Download the Oneflow contract as a PDF”

Fetches the contract as a PDF so a later step can store it, attach it to an email or archive it.

When to use it
finance wants every signed contract in one shared folder, named the same way, without anyone exporting it by hand.
Watch out
this step only fetches the file; to keep it, add a step after it that stores or sends the PDF.
9

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw HTTP request to Oneflow, reusing the sign-in of your connection, for a need none of the eight actions above covers.

When to use it
someone on the team knows the Oneflow request they want and only needs Zapier to carry the sign-in.
Watch out
requests only reach domains tied to Oneflow, and with Stop on error set to Yes, the step halts when Oneflow returns an error.
When it breaks

When a Oneflow Zap breaks

Zapier attaches no help article of its own to Oneflow. What breaks comes from Zapier's general rules and from the limits written into the actions.

  • Old contracts are never picked up

    A Zap only reacts to what happens after it is switched on. Contracts that changed status before that stay where they are; moving the backlog is a separate job.

  • The Zap that sets itself off

    A Zap that writes into the place its own trigger watches starts itself again and again, and burns through your tasks fast. Check what each action changes.

  • A bulk change gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the runs back.

  • The attachment is too heavy

    Add an Attachment or Expanded PDF refuses files over 20 MB, and needs a matching section in the contract to land in.

  • No product table in the template

    Add Product only works if the contract's template holds at least one product table. Without one, the step has nowhere to write.

  • A subject line that runs long

    Send Contract caps the subject at 150 characters and the message at 5000. A mapped field from a long CRM note can cross that line.
Need help

Need help automating Oneflow with Zapier?

A person reads every message.

FAQ

Oneflow and Zapier: frequent questions

01Is the Oneflow Zapier integration free?
Yes, it works on the free plan, because Oneflow is not a premium app on Zapier. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. So Contract Status Changed followed by Download Contract fits. The same Zap with a filter or a second action, for example to file the PDF in Google Drive, becomes a multi-step Zap and needs a paid plan. You still need your own Oneflow account on the Oneflow side.
02How many tasks does a Oneflow Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that downloads the contract after a status change therefore costs one task each time it runs. Add a second action and each run costs two. An action that fails is not counted. Get Contract Details is an action on Zapier, not a search step, so it counts like the others. The free plan holds 100 tasks a month, which is the number to compare with how many contracts change status in your account.
03Is Oneflow on Zapier real time?
Yes for the trigger. Contract Status Changed is an instant trigger: Oneflow tells Zapier when the status changes, and the Zap starts straight away, on every plan. The polling grid of 15 minutes on Free and 2 minutes on Professional does not apply to it. In the editor, a Zap built on an instant trigger shows a lightning bolt. The actions then run one after another, in the order of your steps, each counted as a task when it succeeds.
04What do you need to connect Oneflow to Zapier?
A Oneflow account, and read or write rights on any contract you do not own that the Zap should touch. The connection starts from the Apps page of Zapier with + Add connection: you search Oneflow, sign in on the Oneflow side and grant access. After that, most actions ask which Oneflow user performs them, the contract creator or another user of your account. Pick a user who can work on the contracts concerned, or the step will fail.
05Why does Add Product fail on some contracts?
Because the contract's template has no product table. Add Product writes a line into a product table, and it needs at least one in the template behind the contract. You then pick the table by its ID, numbered from top to bottom in the contract. If your templates differ, the same Zap will work on some contracts and fail on others. The fix is on the Oneflow side: add a product table to the templates that the Zap feeds.
06What if the Oneflow operation you want does not exist on Zapier?
Look at API Request (Beta) first. It is the advanced action at the end of the list: it sends a raw HTTP request to Oneflow with the sign-in of your connection, so you are not limited to the nine ready-made actions. It only reaches domains tied to Oneflow, and it asks for a method and an address. It suits someone who knows exactly which request to send. Without that profile, the ready-made actions and the single status trigger are the real scope of this integration.
07Zapier, Make or n8n for Oneflow?
Compare them on the criteria that matter for contracts rather than on reputation. On Zapier, Oneflow brings one instant trigger on status changes, nine actions and no search step, and it works on the free plan as long as the Zap stays at two steps. So check three things in any tool: whether the status change arrives instantly, whether the contract actions you need are there, and what a scenario of three or four steps costs you. The tool that answers those for your volume is the right one.
Same platform

Other docs you might need on this stack.

Browse all integrations