Resources · Zapier integration

Billsby Zapier integrationAutomate Billsby with Zapier.

The Billsby Zapier integration gives you 5 triggers, 4 actions and 3 searches. Every trigger is instant, so a new subscription or a cleared payment reaches your Zap the moment it happens, even on the free plan, where polling triggers wait 15 minutes.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Billsby Zapier integration actually does

It links your Billsby billing account to Zapier, the tool that runs small automations between apps. Billsby events (a customer signs up, a subscription changes, a payment goes through) start the automation, and Zapier then writes back into Billsby or passes the data on to the next step.

Entitlements that follow the subscription. When Subscription Created fires, Add Feature Tags stamps the new subscription with the tags your product reads to unlock features. Nobody has to remember to do it after a sale.

Usage counters kept in step. Update Counter changes a counter on a subscription, so a metered plan can be fed from the outside instead of by hand.

Extra charges billed on time. Create One-Time Charge adds a one-off fee to a customer's invoice, with its own amount, currency and invoice line. A setup fee or a paid add-on stops living in a spreadsheet.

What Zapier does not do for Billsby: it cannot create a customer or a subscription, cancel anything, or remove a tag from the editor. The four actions update and charge existing records, nothing more. If a flow needs more than that, the Billsby Make integration is worth a look before you build, and our Make vs Zapier comparison sets out the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain terms.

Zap
The automation you build: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts a Zap, such as a new Billsby customer. Once the Zap is on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, charges or updates something in an app for you.
Task
The unit Zapier bills. One task is one action that completes successfully, and your plan is a count of those.
Instant vs polling
An instant trigger is pushed by the app the moment the event happens. A polling one is checked by Zapier on a timer. Billsby only has instant ones.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it there otherwise.
Search step
A step that looks up a record that already exists, so the steps after it can reuse what it found.
Cost

What a Billsby Zap really costs

The trigger is free. Watching Billsby is free. You pay, in tasks, for each action that goes through.

  • Trigger0 task
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Billsby premium app?No

A task is counted every time an action succeeds, and each action in a Zap counts on its own: a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap, one trigger and one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. Billsby is not a premium app, so it works from the free plan, and because its triggers are instant, the polling grid below never slows it down.

Connect

Connect Billsby to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Billsby account linked once to Zapier, then reused by every step that talks to Billsby.

  2. 02

    Pick Billsby

    Search for Billsby by name in the dialog, select it, then click Add connection. You need a Billsby account first, with access to the customers and subscriptions your Zaps will touch.

  3. 03

    Sign in and grant access

    Sign in to Billsby in the tab that opens, then allow Zapier to reach the account. From then on, any Billsby step in any Zap can use this connection without asking again.

First Zap

Your first Billsby Zap, step by step

GoalTag every new subscription with the features it unlocks, after checking its details.

  1. 01

    Build: choose the trigger

    Create a Zap, pick Billsby as the app and Subscription Created as the event that starts it, then select your Billsby connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent subscriptions of the account, so you map the next steps on a real one rather than a blank.

  3. 03

    Add the search

    Add Find Subscription and feed it the Subscription ID from the trigger. This turns the Zap into a multi-step Zap, so it needs a paid plan.

  4. 04

    Add the action

    Add Add Feature Tags, map the SubscriptionUniqueId, and type the tag names your product expects. Test this step and read what Billsby sends back.

  5. 05

    Publish

    Click Publish to switch the Zap on. From now on, each new subscription gets its feature tags moments after it is created.

Triggers

Billsby triggers on Zapier

5 events start a Zap when something happens in Billsby, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Customer Created

Instant trigger

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

Starts your Zap when a brand new customer record appears in Billsby. The Zap gets the customer's identifier, which every Billsby action and search needs later on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a founder of a subscription box wants every new customer to land in the welcome sequence of the email tool without exporting a list.
Watch out
a customer is not yet a subscription; if your Zap is about plans or features, start from Subscription Created instead.
2

Customer Updated

Instant trigger

In Zapier“Triggers when customer details are updated.”

Runs each time someone changes the details of an existing customer in Billsby. It is the hook for keeping other tools in line with what billing knows.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an account manager who works from a CRM wants the contact there to follow every correction made on the billing side.
Watch out
this fires on every edit, so pair it with update actions only; a Zap that creates something here creates a duplicate at each change. And never point it at Update Customer Details, or the Zap triggers itself in a loop.
3

Payment Successful

Instant trigger

In Zapier“Triggers when a successful payment is taken.”

Fires as soon as Billsby takes a payment that goes through. Of the five events, this is the one that tells you money has actually arrived, rather than that a plan was signed up for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a SaaS finance lead wants a thank-you message or a usage credit sent only once the card has cleared, never on signup.
Watch out
do not answer this trigger with Create One-Time Charge; if that charge is paid, it is a new successful payment, and the Zap can start again and bill once more.
4

Subscription Created

Instant trigger

In Zapier“Triggers when a subscription gets created.”

Starts the Zap when a customer gets a new subscription in Billsby. The Zap receives the Subscription ID, which is exactly what Add Feature Tags, Update Counter and the subscription searches ask for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a software vendor unlocks paid features by tag and wants each new plan tagged without a support ticket.
Watch out
an existing customer who adds a second plan also fires this trigger, so a Zap that greets newcomers should check the customer first.
5

Subscription Updated

Instant trigger

In Zapier“Triggers when a subscription is updated.”

Reacts when something changes on a subscription that already exists in Billsby. It follows a plan through its life after signup, where Subscription Created only sees the start.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a customer success team wants a note in its shared channel each time an account changes its subscription, so nobody calls with outdated information.
Watch out
each edit fires the Zap, so keep it to updates; adding a one-time charge here would bill on every small change.
Actions

Billsby actions on Zapier

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

1

Add Feature Tags

Action

In Zapier“Adds feature tags to the provided subscriptionIds”

Stamps one or several subscriptions with the tag names you choose. Your product can then read those tags to decide what the account may use.

When to use it
right after Subscription Created, to switch on the features a plan includes.
Watch out
it takes a list of SubscriptionUniqueIds, not a customer ID; one customer with two plans means two subscriptions to tag.
2

Create One-Time Charge

Action

In Zapier“Charges the customer a one-time fee of adjustable amount”

Bills a customer a single fee on top of the plan, with an amount you set and a line of text that shows on their invoice. The currency goes in as an ISO 4217 code such as USD.

When to use it
an onboarding call or a hardware kit sold alongside the plan, billed the moment it is booked.
Watch out
every run is a real charge, so test it on a test customer first.
3

Update Customer Details

Action

In Zapier“Update customer details”

Rewrites the details of an existing customer: first name, last name and email, all four boxes required with the CustomerUniqueId.

When to use it
when your CRM is where contact details are kept clean, and billing should follow it.
Watch out
every required box must be filled on each run, even the ones that did not change, or the step fails.
4

Update Counter

Action

In Zapier“Updates a counter”

Changes the value of a counter on a subscription. You give the subscription, the counter's ID, the kind of operation to run on it and the value to use.

When to use it
a metered plan where seats, credits or units are counted in another tool and have to reach Billsby before the invoice.
Watch out
the CounterId is required and the Zap cannot guess it; note it from your Billsby setup before you build.
Searches

Billsby searches on Zapier

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

Billsby's three searches each take an identifier and hand back the full record, so later steps can use details the trigger did not carry. They sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts one just before and wires it in. Billsby exposes no find-or-create version: these searches never create anything.

1

Find Customer

Search

In Zapier“Finds the details of a customer when given their Customer ID”

Looks up a customer from their Customer ID and returns their Billsby details for the steps that follow.

When to use it
a payment arrives and you want the customer's name and email in the receipt you send from another tool.
Watch out
it only accepts the Billsby Customer ID, not an email, so the ID must come from a trigger or from where you stored it.
2

Find Shipping Address

Search

In Zapier“Finds the details of a subscription shipping address when given a Subscription ID”

Returns the shipping address attached to a subscription, again from its Subscription ID. It matters for businesses that post something physical with each plan.

When to use it
a new subscription to a monthly box, and the warehouse needs the delivery address in its own tool.
Watch out
it wants the Subscription ID, not the Customer ID, so start from a subscription trigger.
3

Find Subscription

Search

In Zapier“Finds the details of a subscription when given a Subscription ID”

Fetches everything Billsby holds on one subscription from its Subscription ID. It is the step to add when a later action needs more than the trigger handed over.

When to use it
before tagging or counting, to confirm which plan you are dealing with.
Watch out
adding it makes the Zap multi-step, so it needs a paid plan.

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 there and the steps that needed it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create on apps that offer it. Billsby does not, so you will not see it on these three searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first, which is the default, stop the Zap, or pass all of them on together.
When it breaks

When a Billsby Zap breaks

Zapier links no Billsby-specific help article and lists no Billsby rate limit. What goes wrong is what goes wrong on any Zap, with money attached.

On a billing account, a broken Zap is rarely silent: a missed tag means a customer who paid without getting access, a looping charge means an angry email. The cases below are the ones to design against, and the Zapier troubleshooting page is where to go once a run has already failed.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you publish it. Customers and subscriptions created earlier are never picked up; moving that backlog is a separate job.

  • A Zap that triggers itself

    If the Zap writes where its trigger watches, such as Customer Updated feeding Update Customer Details, it sets itself off again and again and burns through tasks.

  • A sudden flood of events

    After a bulk import or a migration into Billsby, a trigger that suddenly sends a huge batch can be held back by Zapier's flood protection.

  • A missing identifier

    Every Billsby action and search requires a customer or subscription ID. If no earlier step provides one, the step has nothing to send and fails.
Need help

Need help automating Billsby with Zapier?

A person reads every message.

FAQ

Billsby Zapier integration: frequently asked questions

01Is the Billsby Zapier integration free?
Yes, at least to start. Billsby is not a premium app, so it works on the free Zapier plan, which includes 100 tasks a month and unlimited Zaps. The catch is that free Zaps are limited to two steps: one trigger and one action. As soon as you add a search such as Find Subscription, a filter or a second action, the Zap becomes multi-step and requires a paid plan.
02How many tasks does a Billsby Zap use?
One per successful action, per run. The trigger costs nothing, and the fact that Zapier is listening to Billsby costs nothing either. A Zap that tags each new subscription uses one task per subscription. If it also updates a counter, that is two tasks per run, because each action counts on its own. Actions that fail are not counted, and a few apps or actions can use more than one task when they complete.
03Does Billsby trigger Zaps in real time?
Yes. All five Billsby triggers are instant: Billsby tells Zapier as soon as a customer, a subscription or a payment event happens, and the Zap starts straight away. The polling grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) does not apply to them, whatever plan you are on. In the editor, a Zap built on one of these triggers shows a lightning bolt. If you are on a paid plan, that speed is the same; the plan changes your task count, not how fast Billsby events arrive.
04What do you need to connect Billsby to Zapier?
A Billsby account, and access to the customers and subscriptions the Zap will touch. In Zapier, open Apps, click + Add connection, search for Billsby, click Add connection, sign in to Billsby in the new tab and grant access. The connection is then reused by every Billsby step. Keep in mind that the actions and searches will ask for a customer or subscription identifier, so plan where it comes from. Once connected, test a trigger to confirm the account returns real records.
05Can a Billsby Zap charge a customer twice?
It can, if it is built the wrong way. Create One-Time Charge bills for real on every run. Put it behind Customer Updated or Subscription Updated and it runs on every edit; put it behind Payment Successful and a paid charge can start it again. Use it after a trigger that happens once per event you want to bill, and test it on a test customer before you publish. Each run that goes through is also one task on your plan.
06What if the Billsby operation you need is not there?
Then Zapier cannot do it directly. The Billsby app on Zapier exposes 5 triggers, 4 actions and 3 searches, and none of them creates a customer, creates a subscription or cancels one. In that case, compare with what other automation platforms expose for Billsby before deciding, or have the missing step handled in Billsby itself. Any extra step you add to work around it, a search included, makes the Zap multi-step and needs a paid plan. Check the list on the Zapier app page before you plan the flow.
07Zapier, Make or n8n for Billsby?
There is no single winner, only criteria. First, coverage: list the Billsby operations your flow needs and check which platform exposes each one. Second, cost: on Zapier the trigger is free and each successful action is one task, so count actions per run. Third, speed: the five Billsby triggers on Zapier are instant on every plan. Fourth, who maintains it once it is live. Score each platform on those four points with your own flow in hand.
Same platform

Other docs you might need on this stack.

Browse all integrations