Resources · Zapier integration

OneBill Zapier integrationAutomate OneBill with Zapier.

The OneBill Zapier integration gives you 4 triggers, 4 actions and 2 searches. Invoices, leads, subscribers and payments can feed your other tools, and leads, subscribers, subscriptions and payments can be created in OneBill without retyping a thing.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OneBill Zapier integration handles for you

OneBill runs the billing side of a subscription business: who the customers are, what plan they pay for, which invoices go out and which payments come in. Plugging it into Zapier lets billing events (an invoice generated, a payment recorded, a new subscriber) start work in other apps, and lets other apps create leads, subscribers, subscriptions and payments in OneBill.

Three typical results, each tied to a real operation. Leads that reach billing without copy-paste: a form or a CRM feeds Create Lead, so sales and billing share the same record. Subscriptions opened from the deal: Find Subscriber retrieves the account number, then Create Subscription attaches the right product and price plan. A finance team that sees money land: New Payment and New Invoice push each event into a chat channel, a sheet or your accounting tool.

And the limits. There is no action to update or cancel anything in OneBill, only to create, and the two searches cover leads and subscribers, not invoices or payments. Every trigger is a polling one, so events arrive with a delay set by your plan. Some triggers watch exactly what an action writes (New Payment and Create Payment, for instance), which makes accidental loops easy. If editing existing billing records matters, read the Zapier review and the Make vs Zapier comparison before you build.

Vocabulary

Zapier vocabulary, the short version

Eight words cover the whole page. Each keeps the meaning given here.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, like a new OneBill invoice. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like creating a subscriber.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only unseen ones. All OneBill triggers work so.
Instant trigger
A trigger the app reports itself the moment the event happens, so nothing waits for the next check. OneBill has none.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a subscriber's account number, so the next steps can use it.
Cost

What it really costs to run

OneBill is not reserved for paid plans on Zapier, so it runs from the free plan. What you spend is tasks, and only successful actions use them.

  • OneBill trigger0 tasks
  • Each successful action1 task
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger typeAll 4 are polling

The trigger never costs a task, and neither do Zapier's checks for new invoices, leads, subscribers or payments. Each action that goes through counts once; a failed one is not billed. A Zap that creates a subscriber, then a subscription, spends two tasks per run. The free plan gives 100 tasks a month and unlimited Zaps, but stops each Zap at two steps. A filter, a search or a second action makes it a multi-step Zap that needs a paid plan. Your plan also sets how often the four polling triggers are checked.

Connect

Connect your OneBill account

  1. 01

    Open the connections page

    In your Zapier account, go to Apps and click + Add connection. You need a OneBill account, plus read or write access on any record you do not own but want the Zap to touch.

  2. 02

    Pick OneBill

    Type OneBill in the search box of the dialog, select it and click Add connection. A new tab opens on the OneBill sign-in screen, waiting for your credentials.

  3. 03

    Sign in and grant access

    Log in to OneBill and allow Zapier to reach the account. The connection is stored once, and every later trigger, action or search that uses OneBill reuses it.

First Zap

Your first Zap: a subscription for every new subscriber

GoalWhen a new subscriber appears in OneBill, find their account number and open a subscription on the right price plan.

  1. 01

    Build: choose the trigger

    Create a Zap, pick OneBill as the app and New Subscriber as the event, then select your OneBill connection. The trigger has no other setting to fill.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent subscribers from your account, so you map fields on a real one rather than an empty template.

  3. 03

    Add Find Subscriber

    Add OneBill again, this time the search Find Subscriber, under the SEARCH heading of Action event. Fill Search By and Value from the trigger, then test.

  4. 04

    Add Create Subscription

    Add Create Subscription. Map the account number from the search, type the Product Name and Priceplan Name as they exist in OneBill, then set Activation Date and Quantity.

  5. 05

    Test and publish

    Test the step and read what came back, then publish. With a search in the middle, this is a multi-step Zap, so it needs a paid plan.

Triggers

OneBill triggers

4 events start a Zap when something happens in OneBill. Zapier checks for them at the interval your plan allows.

1

New Invoice

Polling trigger

In Zapier“Triggers when a​n​ invoice is generated.”

Starts your Zap each time OneBill generates an invoice, so the people who chase, file or report on revenue see it without logging in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your bookkeeper wants every new invoice copied into the accounting tool or a shared folder of the month.
Watch out
OneBill offers no search on invoices, so a later step cannot look up an older invoice; only the one that fired the Zap is at hand.
2

New Lead

Polling trigger

In Zapier“Triggers when a new lead is ​created.”

Reacts to a fresh lead created in OneBill, the prospect stage before someone becomes a paying subscriber.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
sales should get a follow-up task in the CRM or an alert in chat for each lead entered by the billing team.
Watch out
never pair it with Create Lead in the same Zap, or every lead created spawns another one and your tasks drain in a loop.
3

New Subscriber

Polling trigger

In Zapier“Triggers when a new subscriber is​ created​.”

Fires when a new subscriber record is created in OneBill, the moment a customer becomes billable.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
onboarding, a welcome email or an account in your support desk should start for each new customer.
Watch out
subscribers created before the Zap was published never come through; plan a separate import if the backlog matters.
4

New Payment

Polling trigger

In Zapier“Triggers when ​a payment is recorded​.”

Watches the cash side: every payment recorded in OneBill starts the Zap with that payment in hand.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
finance wants a line in the cash-tracking sheet, or a thank-you note to go out, for each payment received.
Watch out
Create Payment writes exactly what this trigger watches, so a Zap that starts here and records a payment in OneBill loops on itself.
Actions

OneBill actions

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

1

Create Lead

Action

In Zapier“Creates a new Lead.”

Adds a prospect to OneBill from data collected elsewhere, so billing knows about them before the first invoice.

When to use it
a demo request or a pricing form on your site should land in OneBill as a lead.
Watch out
Account Type, First Name, Last Name and Email are all required; a form missing one of them fails the step.
2

Create Subscriber

Action

In Zapier“Creates a new subscriber.”

Registers a paying customer as a subscriber in OneBill, straight from the tool where the sale was closed.

When to use it
a deal marked won in your CRM should turn into a billable account the same day, without a handover email.
Watch out
it asks for the same four required fields as Create Lead, Account Type included, so map each one explicitly.
3

Create Subscription

Action

In Zapier“Creates a new subscription.”

Attaches a subscription to an existing subscriber, with the product, price plan, start date and quantity you choose.

When to use it
a signed order elsewhere should open the matching subscription in OneBill.
Watch out
five fields are required, starting with Account Number; Find Subscriber is the usual way to supply it.
4

Create Payment

Action

In Zapier“​Creates a payment entry against a subscriber.”

Records a payment against a subscriber in OneBill, full or partial, so balances reflect money received elsewhere.

When to use it
payments collected by another tool should show up in OneBill without manual entry.
Watch out
Payment Date, Payment Method and Amount are required, and never run it in a Zap triggered by New Payment.
Searches

OneBill searches

2 search steps look for data that already exists in OneBill, so a later step can use it.

A search step finds something that already exists in OneBill and passes it to the next steps. Both OneBill searches return the record including its account number, which several actions need. In the editor they sit at the bottom of the Action event list, under SEARCH, and some action fields offer + Add search step to insert one just before. Whether a search wants an exact value or something close is decided by OneBill. Three settings decide what happens next.

1

Find Lead

Search

In Zapier“Finds a lead (including their account number).”

Looks up an existing lead in OneBill and hands back the record with its account number.

When to use it
a form arrives and you need to know whether this prospect is already in OneBill before creating a new lead.
Watch out
Search By and Value are both required; pick the criterion first, then map the value from an earlier step.
2

Find Subscriber

Search

In Zapier“Finds a subscriber (including their account number).”

Retrieves an existing subscriber, account number included, which is the missing piece for Create Subscription.

When to use it
an order or a payment comes from another tool and has to be tied to the right OneBill customer.
Watch out
set the multiple-results option; two subscribers matching the same value would otherwise send the first one on.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that offer it. OneBill exposes no find-or-create, so its two searches only ever find.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When the integration breaks

Zapier attaches no help article to OneBill, and no app-specific limit is documented. What goes wrong comes from how Zaps behave in general, and billing data makes some of these failures expensive.

  • Past invoices and payments stay behind

    A Zap only reacts to what happens after you switch it on. Invoices, leads and payments that already existed are never sent; moving them is a separate job.

  • The payment loop

    A Zap started by New Payment that runs Create Payment, or New Lead with Create Lead, sets itself off again and again and burns through your tasks.

  • Bulk billing runs held back

    When a trigger suddenly returns a huge batch, after an import or a mass invoicing run, Zapier's flood protection can hold those runs back.

  • A subscriber that cannot be found

    By default, Find Subscriber with no result stops the Zap and skips Create Subscription. Check the no-result setting before relying on it.
Need help

Need help automating OneBill with Zapier?

A person reads every message.

FAQ

OneBill Zapier integration: FAQ

01Is the OneBill Zapier integration free?
Yes. OneBill is not reserved for paid plans, so it works on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. A Zap from New Payment to a chat message fits. A Zap that searches a subscriber before creating a subscription does not: a search, a filter or a second action makes it multi-step, which requires a paid plan.
02How many tasks does a OneBill Zap use?
One per successful action. OneBill triggers never cost a task, and Zapier checking for new invoices, leads, subscribers or payments is free however often it runs. Each action that completes counts once, so creating a subscriber and then a subscription spends two tasks per run. A failed action is not billed. A loop between New Payment and Create Payment is the fastest way to burn tasks, so keep those apart.
03Do OneBill triggers work in real time?
No. All four OneBill triggers are polling triggers: Zapier asks OneBill for new items at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can change how often a polling trigger checks and run a check by hand from the editor. The trigger type comes from the app and cannot be switched to instant in Zapier.
04What does it take to connect OneBill to Zapier?
A OneBill account, plus read or write access on any record you do not own but want the Zap to touch. In Zapier, open Apps, click + Add connection, search for OneBill, then click Add connection. Sign in to OneBill in the tab that opens and grant Zapier access to the account. The connection is saved once and reused by every OneBill trigger, action or search you add later. Nothing to redo for the next Zap.
05Why does Create Subscription fail in a OneBill Zap?
Usually because one of its five required fields is empty or wrong: Account Number, Product Name, Priceplan Name, Activation Date or Quantity. The account number rarely travels with data from another app, so put Find Subscriber just before and map its result. Product and price plan names have to match what exists in your OneBill account. That search makes the Zap multi-step, so it runs on a paid plan. Test the step on a real subscriber.
06What if the OneBill operation you need is not there?
Then Zapier cannot do it for OneBill today. The app offers four triggers (New Invoice, New Lead, New Subscriber, New Payment), four actions that create leads, subscribers, subscriptions and payments, and two searches for leads and subscribers. Nothing updates or cancels a record, and nothing searches invoices or payments. If that missing step is central, consider another tool, or keep it inside OneBill and automate around it. Check the list before you design.
07Zapier, Make or n8n for OneBill?
Decide on criteria, not on a ranking. On Zapier, check first that create-only actions and two searches cover your billing process. Then weigh the delay: polling triggers check every 15 minutes on the free plan, faster on paid ones. Next, count tasks, one per successful action, and whether your Zaps fit in two steps or need searches and a paid plan. Put the other tools through the same checks for OneBill before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations