Resources · Zapier integration

Piriod Zapier integrationAutomate Piriod with Zapier.

The Piriod Zapier integration has 11 triggers, 0 actions and 0 searches. All 11 are instant: a new customer, a finalized invoice, a failed payment or a subscription change reaches your other tools without waiting, even on the free plan.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Piriod Zapier integration does for your billing

Piriod handles subscriptions and recurring billing. Connected to Zapier, it becomes a source of events: every time something happens to a customer, an invoice, a payment, a payment source or a subscription, Zapier can pass it on to your CRM, your accounting sheet or your team chat.

Three results subscription businesses build first. A dunning alert: Payment Failed pings the account manager the moment a charge does not go through, so someone calls the customer before the next cycle. A clean accounting trail: Invoice Finalized adds each confirmed invoice to the sheet your bookkeeper works from, with no monthly export. A CRM that matches billing: Customer Created and Customer Updated keep the contact record in your sales tool in step with Piriod.

Now what Zapier does not do here. Piriod offers no action at all, so a Zap can't create a customer, issue an invoice, record a payment or start a subscription in Piriod. There is no search either, so a Zap can't look up a customer in Piriod halfway through. The flow is one way: Piriod speaks, your other apps listen. If your plan needs data written back into Piriod, that part stays manual or goes through another route.

Each Zap built on these triggers then needs an action in another app, and that is where the tasks are spent. Before choosing your stack, n8n vs Zapier and Zapier training are worth a look.

Vocabulary

Zapier vocabulary, in plain words

Eight words you will meet in the editor, each explained once here and used as is afterwards.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it: here, a billing event in Piriod.
Action
What the Zap does once started: the step that writes, sends or moves something. With Piriod, actions live in other apps.
Task
The unit Zapier bills: one action your Zap completed successfully. Your plan counts those and nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the way Piriod does.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Connection
Your Piriod account linked to Zapier once, then reused by every Piriod trigger in every Zap you build.
Multi-step Zap
Any Zap with more than one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
Cost

What a Piriod Zap really costs

The Piriod side costs nothing. Every trigger is free; you pay for what the Zap does next, in other apps.

  • Piriod trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks / month, 2-step Zaps
  • Premium appNo

A task is one successful action. A Piriod event that only posts a chat message costs one task per run; one that also logs a row in a sheet costs two. An action that fails is not counted. Piriod is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps each. Notifying two tools, or adding a filter, makes the Zap multi-step and needs a paid plan. The interval grid below concerns polling triggers only; all 11 Piriod triggers are instant and ignore it.

Connect

Connect your Piriod account in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, go to the Apps page and click + Add connection. You need a Piriod account, plus access to any data you don't own that the Zap should read.

  2. 02

    Find Piriod

    Type Piriod in the search box of the dialog, select it, then click Add connection. Zapier opens a new browser tab where the Piriod sign-in takes place.

  3. 03

    Sign in and grant access

    Log in to Piriod in that tab and allow Zapier to use the account. The connection is saved, and every Piriod trigger in your Zaps reuses it from then on.

First Zap

Your first Zap: log every confirmed invoice

GoalEach time Piriod finalizes an invoice, add it to your accounting sheet and tell the finance channel.

  1. 01

    Pick the Piriod trigger

    In the editor, choose Piriod as the app that starts the Zap and Invoice Finalized as the event, then select the connection you just added.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent finalized invoices of your account, so you map the next steps on a real invoice and not on a blank.

  3. 03

    Add the spreadsheet action

    Add your spreadsheet app and its add-a-row action. Map the invoice data from the trigger into the columns of your sheet, then test the step and check the row.

  4. 04

    Add the chat message

    Add your team chat app and write the message, pulling the invoice details from the trigger. This second action makes it a multi-step Zap, so it needs a paid plan.

  5. 05

    Publish

    Click Publish to switch the Zap on. Invoices finalized from now on flow through; invoices confirmed before stay out of the sheet.

Triggers

Piriod triggers

11 events start a Zap when something happens in Piriod, and 11 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.”

A new customer appears in Piriod and the Zap starts with that customer's record, ready to be copied wherever your sales or support team works.

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 company that wants every new paying account to appear in its CRM without someone typing it twice.
Watch out
customers created before the Zap was published are never sent, so import the existing base separately if the CRM needs it.
2

Customer Updated

Instant trigger

In Zapier“Triggers when a customer is updated.”

Fires on changes, not on arrivals: when an existing customer record is edited in Piriod, the Zap runs with the updated version so other tools can catch up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping the billing contact in your helpdesk aligned when a client changes company details in Piriod.
Watch out
any edit sets it off, so a busy account can spend tasks fast; a filter (paid plan) narrows it to the changes you care about.
3

Invoice Finalized

Instant trigger

In Zapier“Triggers when a invoice is finalized (confirmed).”

Once an invoice is confirmed in Piriod, this trigger hands it to the Zap. It waits for the confirmed version, which makes it the safest starting point for anything accounting touches.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
feeding the sheet or the folder your accountant reconciles each month, one confirmed invoice per row.
Watch out
invoices finalized before you published the Zap won't show up, so the first month in the sheet may be incomplete.
4

Payment Created

Instant trigger

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

Each time a new payment is created in Piriod, the Zap gets it. Created is not the same as paid: this fires on the payment's appearance, before you know how it ends.

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 log of every payment attempt for a finance team that wants the full picture, failures included.
Watch out
to celebrate or count actual revenue, Payment Succeeded is the better event.
5

Payment Failed

Instant trigger

In Zapier“Triggered when a payment fails.”

When a charge does not go through, Piriod reports the failure and the Zap starts. This is the trigger that protects revenue, because it turns a silent problem into a message someone reads.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alerting the account owner in team chat so they contact the customer before the subscription lapses.
Watch out
a long run of failed payments can spend tasks quickly on the free plan's 100.
6

Payment Succeeded

Instant trigger

In Zapier“Triggers when a payment is successfully paid.”

Only the payments that were actually paid reach this Zap. It's the cleanest signal that money came in, without the noise of attempts still pending.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
sending a thank-you email from your mailing tool or unlocking access in another app once the customer has paid.
Watch out
pair it with Payment Failed rather than Payment Created if what you track is the outcome, not the attempt.
7

Payment Updated

Instant trigger

In Zapier“Triggers when a payment is updated.”

Here the Zap runs whenever an existing payment changes in Piriod. It catches the later life of a payment, after its creation, whatever the change turns out to be.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping a payment line in your reporting sheet current instead of recording only its first state.
Watch out
because every change counts, add a filter (paid plan) if only a specific change should go further.
8

Source Created

Instant trigger

In Zapier“Triggers when a source is created.”

Piriod calls it a source, and this trigger starts the Zap when one is created. Zapier's listing says nothing more about what a source holds, so test it against your own account first.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
recording in your CRM that a customer has just set up a new source in Piriod.
Watch out
run the trigger test and read the three items it brings back before mapping anything.
9

Source Stored

Instant trigger

In Zapier“Triggers when a source is stored.”

A sibling of Source Created, but tied to a different moment: it fires when a source is stored in Piriod. The listing does not spell out how stored differs from created.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when your follow-up should wait until Piriod has kept the source, rather than just registered it.
Watch out
build one test Zap per trigger and compare what each brings back before choosing between the two.
10

Subscription Created

Instant trigger

In Zapier“Triggers when a subscription is created.”

A customer signs up to a plan and Piriod creates the subscription: that is the moment this Zap starts, with the new subscription in hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
kicking off onboarding, such as adding the customer to a welcome sequence in your email tool.
Watch out
subscriptions created by a bulk import into Piriod can arrive as one huge batch, and Zapier may hold them back.
11

Subscription Updated

Instant trigger

In Zapier“Triggers when a subscription is updated.”

Upgrades, downgrades, any edit to an existing subscription: when one changes in Piriod, the Zap receives the new state and can tell the rest of your stack.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
updating the plan field in your CRM so account managers see what the customer actually pays for.
Watch out
it does not tell you which change happened unless the data shows it, so check a real test item first.
When it breaks

When a Piriod Zap breaks

Zapier links no help article to Piriod, so the cases below are the general limits, read through a billing app.

With only triggers on offer, the risks sit in what a Zap does not do by itself and in volume. If a run fails on the action side, Zapier troubleshooting covers the usual fixes.

  • History is not sent

    A Zap only reacts to events after it is published. Customers, invoices and payments that already existed in Piriod are never picked up; that backlog is a separate job.

  • A bulk import is held back

    Importing many customers or subscriptions into Piriod at once can produce a huge batch of events. Zapier's flood protection may hold those runs back.

  • Updated triggers fire often

    Customer, Payment and Subscription Updated run on every change. Each run that ends in an action costs a task, and the free plan stops at 100 a month.

  • The free plan stops at two steps

    One Piriod trigger plus one action fits the free plan. Notify a second tool or add a filter, and the Zap becomes multi-step and needs a paid plan.
Need help

Need help automating Piriod with Zapier?

A person reads every message.

FAQ

Piriod Zapier integration: FAQ

01Is the Piriod Zapier integration free?
Yes. Piriod is not a premium app, so its 11 triggers work on the free Zapier plan. That plan gives 100 tasks a month and as many Zaps as you want, but each Zap is limited to two steps: one Piriod trigger and one action in another app. Sending a failed-payment alert to team chat fits. Logging the invoice in a sheet and posting to chat in the same Zap takes two actions, so it needs a paid plan. Start with single-action Zaps to test without paying.
02How many tasks does a Piriod Zap use?
Nothing for the Piriod trigger, then one task per action that succeeds in your other apps. An invoice finalized in Piriod that adds one row to a sheet costs one task. The same invoice also posted to chat costs two. Failed actions are not counted. The volume to watch is the number of events: the Updated triggers fire on every change, so a busy account can multiply runs. Estimate how many customers, payments or invoices move each month before you pick a plan.
03Are Piriod triggers real-time?
Yes, all 11 are instant. Piriod reports each event to Zapier itself when it happens, and the Zap starts right away. The interval grid by plan, 15 minutes on Free and down to 1 minute on Team and Enterprise, only applies to polling triggers, and Piriod has none. So on this app the free plan reacts as fast as Enterprise. In the editor, Zaps built on an instant trigger show a lightning bolt, which is an easy way to check.
04What does it take to connect Piriod to Zapier?
A Piriod account you can sign in to, plus access to anything you don't own that the Zap should read. Then, from the Apps page of Zapier: click + Add connection, search for Piriod, click Add connection, sign in in the tab that opens and grant access. It is done once, and every Piriod trigger in your Zaps reuses that connection. After that, testing a trigger brings back the three most recent matching items from your account.
05Payment Created or Payment Succeeded: which one should start the Zap?
It depends on what you need to know. Payment Created fires when a new payment is created in Piriod, before you know whether it went through. Payment Succeeded fires only when the payment is successfully paid. For anything that should happen once money is in (a thank-you, access, a revenue line), use Payment Succeeded. For a complete log of attempts, Payment Created. To react to problems, pair Payment Succeeded with Payment Failed rather than relying on the created event.
06What if the Piriod operation you need is not listed?
Then this integration can't do it, and it's better to know before you build. Piriod offers 11 triggers on Zapier, no action and no search. Creating a customer, issuing an invoice or changing a subscription in Piriod from a Zap is out of reach, and so is looking something up in Piriod mid-Zap. Options: let Piriod remain the place where billing data is entered, use the triggers to feed everything else, or check whether another automation tool exposes what is missing here.
07Zapier, Make or n8n for Piriod?
Choose on criteria, not on a ranking. On Zapier the facts are these: 11 instant triggers, no action, no search, a free plan of 100 tasks a month limited to two-step Zaps. If what you need is to push Piriod's billing events into other tools without code, that covers it. If you need to write into Piriod or read from it mid-workflow, check what each tool offers for Piriod on that exact point. Count your monthly billing events first, because they drive the cost wherever you build.
Same platform

Other docs you might need on this stack.

Browse all integrations