Resources · Zapier integration

OrderForms Zapier integrationAutomate OrderForms with Zapier.

The OrderForms Zapier integration comes down to 1 trigger, 0 actions and 0 searches: Order Created, which hands each new order from your payment forms to the rest of your tools. It is instant, so the Zap starts right away, even on the free plan.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OrderForms Zapier integration is good for

It connects OrderForms, the drag-and-drop form builder you use to take payments for products and subscriptions, to Zapier. Each new order placed on one of your forms can then start work in another app. OrderForms speaks first here and never listens: it sends orders out, nothing comes back in.

Three results justify the setup. An order log nobody types: Order Created followed by a spreadsheet action keeps a running list of every sale. A team that hears about each sale: the same trigger feeding a chat or email action tells the people who prepare, ship or onboard. Buyers who land in your CRM: the order becomes a contact or a deal in the tool your sales team already lives in, with no copy and paste.

What Zapier does not do for OrderForms matters just as much. There is no action, so no Zap can create, change or refund an order inside OrderForms. There is no search either, so a Zap cannot look up an older order. And with a single trigger, only new orders count: an order that changes later starts nothing. In short, OrderForms is a starting point for your Zaps, never a destination, and every flow has to be designed that way. Before you commit, the Zapier review and Make vs Zapier are both one click away.

Vocabulary

Zapier vocabulary in one minute

Eight words are enough to read this page. Each is explained once here, then used without a reminder.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. For OrderForms there is exactly one: a new order created on one of your forms.
Action
What the Zap does once started: the step that writes, sends or moves something for you, here always in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is counted in tasks.
Instant trigger
A trigger the app reports itself, the moment the event happens, so nothing waits for a scheduled check. Order Created is one.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. OrderForms has none.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What an OrderForms Zap really costs

The trigger never costs a task, and OrderForms is not reserved for paid plans: it works from the free plan. What you pay for is what happens in the other apps.

  • Order Created0 tasks
  • Successful action1 task each
  • Failed actionnot counted
  • Free plan100 tasks a month, two-step Zaps

Each action that succeeds counts as one task, and an action that fails is not counted against your plan. The free plan gives 100 tasks a month and builds two-step Zaps: Order Created plus one action. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan. The interval grid below concerns polling triggers only, so Order Created never waits on it, whichever plan you are on.

Connect

Connect your OrderForms account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page and click + Add connection. A connection is your OrderForms account linked to Zapier once, then reused by every Zap that listens to it.

  2. 02

    Find OrderForms

    Search for OrderForms in the dialog, select it, then click Add connection. You need an OrderForms account, plus access to any forms you do not own yourself but want the Zap to watch.

  3. 03

    Sign in and allow access

    OrderForms opens in a new tab. Sign in with the account that owns the forms, then grant Zapier access. The connection now shows up whenever a Zap starts with Order Created.

First Zap

Your first Zap: log and announce each new order

GoalEach new OrderForms order becomes a row in a sheet, then an email to whoever fulfils it.

  1. 01

    Pick the trigger

    Start building the Zap, choose OrderForms as the app and Order Created as the event that starts it, then select your connection.

  2. 02

    Test on real orders

    Run the trigger test. Zapier brings back the three most recent orders of the connected account, so the next steps are mapped on a real sale rather than a sample.

  3. 03

    Add the sheet row

    Pick Google Sheets as the action app and map the order details you want to keep into the columns of your sheet, one column per detail.

  4. 04

    Add the email

    Add Gmail as a second action and write the message with details from the order. Two actions make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test, then publish

    Test each step once and read what came back before going further. When it all looks right, publish the Zap to switch it on.

Triggers

The OrderForms trigger

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

1

Order Created

Instant trigger

In Zapier“Triggers when a new order is created.”

A customer completes one of your OrderForms payment forms, the order is created, and the Zap starts with that order in hand. It is the only door OrderForms opens to Zapier, so every automation built on this app begins here, whether the form sells a one-off product or a subscription.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each sale should reach your sheet, your inbox or your CRM without anyone exporting a file.
Watch out
it reacts to new orders only; a later change to an order starts nothing.
When it breaks

When an OrderForms Zap breaks

Zapier attaches no help article to OrderForms, and no limit specific to the app is documented. The cases below are the general ones that hit any Zap.

With a single instant trigger there is little to tune, which means the breakdowns are rarely in OrderForms itself. They sit in timing, volume and plan limits. For anything outside these three, the Zapier troubleshooting page is the next stop.

  • Past orders never arrive

    A Zap only reacts to what happens after it is switched on. Orders taken before publication are not picked up, and moving that backlog is a separate job.

  • A sudden flood held back

    When a trigger returns a huge batch at once, after a bulk import or a migration for instance, Zapier's flood protection can hold it back.

  • The second action will not stick

    On the free plan a Zap stops at two steps. Adding a second action or a filter after Order Created makes it multi-step, and that needs a paid plan.
Need help

Need help automating OrderForms with Zapier?

A person reads every message.

FAQ

OrderForms and Zapier: common questions

01Is the OrderForms Zapier integration free?
Yes. OrderForms is not reserved for paid plans, so it runs on Zapier's free plan. That plan gives you 100 tasks a month and as many Zaps as you like, but each Zap is limited to two steps: Order Created and one action. A row in a sheet or a single email fits. A second action, or a filter that keeps only some orders, turns the Zap into a multi-step one, and that requires a paid plan. No price is quoted on this page, because Zapier's plan grids change too often to publish.
02How many tasks does an OrderForms Zap use?
One per successful action, per order. The Order Created trigger itself never costs a task, and an action that fails is not counted against your plan. A Zap that adds a sheet row for each order therefore uses one task per order; a Zap that adds the row and then sends an email uses two. Since OrderForms has no actions of its own, every task you spend is spent in the other apps of the Zap. A few apps and actions take more than one task when they complete, so check your plan's count after the first orders.
03Does OrderForms send orders to Zapier in real time?
Yes. Order Created is an instant trigger: OrderForms tells Zapier the moment an order is created, and the Zap starts right away, whatever your plan. The interval grid, from 15 minutes on Free down to 1 minute on Team and Enterprise, only applies to polling triggers, and OrderForms has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. The flip side is that nothing is sent retroactively: orders created before the Zap was published never reach it.
04What does connecting OrderForms to Zapier require?
An OrderForms account, plus read or write access on any forms you do not own yourself but want the Zap to watch. The connection starts on the Apps page of your Zapier account: click + Add connection, search for OrderForms, pick it, click Add connection, then sign in to OrderForms in the tab that opens and grant Zapier access. It is done once. Every Zap that starts with Order Created then reuses that connection, so there is nothing to repeat for the next one.
05Can a Zap update or refund an OrderForms order?
No. OrderForms offers no action in Zapier, only the Order Created trigger, so a Zap can read new orders but never write anything back. Creating, editing, cancelling or refunding an order stays a job for the OrderForms interface. The same goes for older orders: with no search available, a Zap cannot look one up later. What a Zap can do is carry each new order into other apps the moment it is created, and act there, in a sheet, an inbox, a CRM or a team chat.
06What if the OrderForms operation needed is missing?
Then it is not available in Zapier today. The list is short and closed: 1 trigger, no action, no search. Anything that needs to reach into OrderForms, such as changing an order or reading an old one, cannot be built with this integration. The realistic options are to rethink the flow so it starts from Order Created and acts only in other apps, or to handle that part in OrderForms directly. If neither fits, the need belongs to another tool.
07Zapier, Make or n8n for OrderForms?
It comes down to criteria rather than a winner. On the Zapier side, the OrderForms facts are these: one instant trigger, no action, no search, a free plan capped at 100 tasks a month with two-step Zaps, and every successful action billed. So ask yourself whether your flow only needs to push new orders out, or also needs to write back into OrderForms. Estimate how many orders, and so how many actions, you expect each month. Then check those same points for OrderForms on the other two tools before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations