Resources · Zapier integration

Pike13 Zapier integrationAutomate Pike13 with Zapier.

The Pike13 Zapier integration gives you 7 triggers, 4 actions and 2 searches. Every trigger is instant, so clients, invoices and payments reach your other tools straight away, and none of it needs a paid plan as long as the Zap stays at two steps.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pike13 Zapier integration is for

Linking Pike13 to Zapier lets the studio software talk to the rest of your tools without anyone copying data across. A new client, a fresh invoice or a settled payment in Pike13 can start work elsewhere, and other tools can create or update people in Pike13 in return. Every Pike13 event reaches Zapier the moment it happens.

Three concrete results, each built on real operations:

A roster note before every session. Event Occurrence Upcoming fires ahead of a scheduled session, 24 hours by default, and Post Roster Note pins a staff-only or public note on it.

Sign-ups that land in Pike13 on their own. A form or a sales tool starts the Zap, Find Person checks whether the client already exists, and Create Person adds the ones who do not, with or without the invite email.

Money events your bookkeeping sees. Invoice Created, Transaction Created and Transaction Updated (voided or settled) push billing activity to a sheet or an accounting tool.

What Zapier does not do here: nothing deletes a person, an invoice or a note, and there is no action that writes invoices or transactions, only triggers and a search that read them. A Zap also ignores whatever already sat in Pike13 before you switched it on.

Picking between platforms? The n8n vs Zapier comparison is a sensible next stop.

Vocabulary

Zapier vocabulary in one minute

A few Zapier words come back on every line below. Here they are, in plain English.

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, like a new client in Pike13. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that creates, updates or posts something for you, in Pike13 or elsewhere.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those, nothing else.
Instant vs polling trigger
Instant: the app tells Zapier the moment the event happens. Polling: Zapier checks on a timer. All seven Pike13 triggers are instant.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a Pike13 client, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A search, a filter or a second action makes one, and it needs a paid plan.
Cost

What Pike13 on Zapier costs in practice

Pike13 is not a premium app, so it runs on the free plan. Everything is counted in tasks, and only finished actions spend them.

  • Trigger firing0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, unlimited Zaps, two steps per Zap
  • Premium appNo, Pike13 works on the free plan

A Pike13 trigger firing costs nothing. Each action that goes through, say Create Person or Post Roster Note, counts as one task; an action that fails is not charged. The free plan builds two-step Zaps only. The moment you put Find Person in front of Create Person, or add a filter, the Zap is multi-step and needs a paid plan. Since every Pike13 trigger is instant, the interval grid below does not slow them down on any plan.

Connect

Connect your Pike13 account to Zapier

  1. 01

    Start from the Apps page

    Open Apps in your Zapier account and click + Add connection. You need an existing Pike13 login, ideally one with access to every business you plan to automate.

  2. 02

    Choose Pike13

    Search for Pike13 in the dialog, select it and click Add connection. A new tab opens on the Pike13 sign-in page, where you use your usual Pike13 login.

  3. 03

    Sign in and allow access

    Sign in with your Pike13 account in that tab, then grant Zapier access. From now on every Zap step that uses Pike13 can reuse this connection without asking you again.

First Zap

Build your first Pike13 Zap

GoalPost a public note on the roster of each upcoming session, but only for the classes you pick.

  1. 01

    Pick the trigger

    Create a Zap, choose Pike13 and the Event Occurrence Upcoming event, then select your Pike13 connection. This trigger is instant, so no interval applies.

  2. 02

    Test it on a real session

    Run the test: Zapier brings back the three most recent items from your account. Pick one, so the next steps are mapped on a real session instead of a blank.

  3. 03

    Add a filter

    Add a Filter step from the plus icon and set the field, the rule and the value. Use a text rule for text. The filter makes the Zap multi-step, so a paid plan is required.

  4. 04

    Add Post Roster Note

    Add Pike13 again with Post Roster Note. Pick the Business, map the Event Occurrence ID from the trigger, choose the Note Type and write the Note itself.

  5. 05

    Test, then publish

    Test the action once and check the note on the session in Pike13. Then click Publish to switch the Zap on; sessions that were already announced stay untouched.

Triggers

Pike13 triggers on Zapier

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

1

Event Occurrence Upcoming

Instant trigger

In Zapier“Triggers when an Event Occurrence is about to be notified, 24 hours by default.”

Pike13 warns Zapier ahead of a scheduled event occurrence, with a lead time Pike13 sets by default. It is the one trigger here that looks forward rather than back, which makes it the natural starting point for reminders and prep work.

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 yoga studio that wants a text reminder sent to the instructor the day before each class.
Watch out
the warning comes ahead of the session, so anything the Zap posts goes out before the class itself has happened.
2

Invoice Created

Instant trigger

In Zapier“Triggers when a new invoice is added to your business.”

A brand-new invoice in your Pike13 business starts the Zap, carrying that invoice into whatever step comes next. Billing data leaves Pike13 without anyone exporting a report.

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 gym owner who logs every new invoice in a shared spreadsheet for the accountant.
Watch out
only invoices created after you publish the Zap are sent; last month's invoices never come through on their own.
3

Invoice Updated

Instant trigger

In Zapier“Triggers when an invoice is updated.”

Whenever an existing invoice changes in Pike13, Zapier hears about it and runs the Zap with the updated version. Use it to keep a copy of your invoices in step with what Pike13 shows.

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 finance sheet that must reflect corrections made to invoices at the front desk.
Watch out
one invoice edited several times starts the Zap several times, and each run spends its own tasks.
4

Person Created

Instant trigger

In Zapier“Triggers when a new person is added to your business.”

Someone new gets added to your Pike13 business, and the Zap starts with that person in hand. It is the trigger Zapier itself puts forward for this app.

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 pilates studio that adds every new client to its newsletter list on the day they join.
Watch out
do not pair it with Create Person on the same business, or each new person creates another one.
5

Person Updated

Instant trigger

In Zapier“Triggers when a person is updated in your business.”

This one reacts to changes on an existing person in your Pike13 business and hands the updated record to the Zap. Your other tools stop drifting away from what Pike13 knows about each client.

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 CRM that has to stay aligned with the client records of the studio software.
Watch out
an Update Person step on the same business would fire this trigger again and loop.
6

Transaction Created

Instant trigger

In Zapier“Triggers when a new transaction is made.”

Each new transaction made in Pike13 starts the Zap, so payments can flow into reporting or follow-up steps without a manual export at the end of the week.

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 climbing gym that posts each sale to a team chat channel so the floor staff sees the day's activity.
Watch out
a transaction can later be voided, so pair this with Transaction Updated if your figures must stay right.
7

Transaction Updated

Instant trigger

In Zapier“Triggers when a transaction is voided or settled.”

Pike13 calls Zapier when a transaction is voided or settled, the two moments when a payment's status really changes. That keeps any copy of your takings honest after the fact.

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 owner who marks payments as cleared or cancelled in a bookkeeping sheet.
Watch out
voided and settled both start the same Zap, so add a filter if only one of them matters, which needs a paid plan.
Actions

Pike13 actions on Zapier

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

1

Post Roster Note

Action

In Zapier“Add a new note to an event occurrence.”

Pins a note to one event occurrence on the roster. You choose who reads it: staff only, enrolled clients too, or website visitors as well.

When to use it
a coach's change of plan, typed elsewhere, that should appear on the session before clients arrive.
Watch out
the Note Type decides visibility, and a Website note is readable by anyone who visits.
2

Create Person

Action

In Zapier“Add a new Person to a Pike13 Business.”

Adds someone new to a Pike13 business from data another tool collected, with a first and last name as the minimum.

When to use it
a trial-class form on your website that should turn each sign-up into a Pike13 client.
Watch out
Pike13 emails an account invite by default; set Send Invite? to no to stay quiet, and Skip Complimentary Passes to yes to hold back welcome passes.
3

Update Person

Action

In Zapier“Update an existing Person in a Pike13 business.”

Changes the record of someone who already exists in your Pike13 business, picked by their Person ID.

When to use it
a client corrects their details in your CRM and Pike13 should follow.
Watch out
without a Person ID nothing happens, so put Find Person before it when the earlier step only knows a name or an email.
4

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 action that sends a hand-built request to Pike13 through your existing connection, for whatever the three other actions do not cover.

When to use it
someone on the team knows exactly what Pike13 expects and needs one request the menu lacks.
Watch out
it is still in beta, and the Stop on error setting decides whether a failure halts the Zap or lets it carry on.
Searches

Pike13 searches on Zapier

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

A search step finds a person or an invoice that already lives in Pike13 and passes it to the next steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the search does not find exactly one match.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as it is, a search that finds nothing stops the Zap and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Pike13 Zap breaks

Zapier ties no help article and no published limit to Pike13. What goes wrong comes from Zapier's general rules and from a few required fields.

Six cases come back again and again, and most of them never show a red error. Read them before you publish, and keep the Zapier troubleshooting page close for the rest.

  • Older clients and invoices never arrive

    A Zap only reacts to what happens after it is switched on. People, invoices and payments already in Pike13 are not sent, and moving them is a separate job.

  • Person Created feeds Create Person

    A Zap that writes into the place its own trigger watches sets itself off again and again. Creating or updating people from a person trigger can loop and burn tasks.

  • A bulk import gets held back

    After importing a client list in one go, the trigger can return a huge batch at once, and Zapier's flood protection may hold it back instead of running it all.

  • Update Person without an ID

    Update Person needs a Person ID. When the previous step only carries a name or email, add Find Person first, which makes the Zap multi-step.

  • A search with every box empty

    Find Person and Find Invoice each need at least one search field filled in. Left blank, the step has nothing to look for and the Zap goes no further.

  • API Request keeps going after an error

    With Stop on error set to No, API Request (Beta) carries on even when Pike13 refuses the request, so the next steps run on nothing useful.
Need help

Need help automating Pike13 with Zapier?

A person reads every message.

FAQ

Pike13 Zapier integration: common questions

01Is the Pike13 Zapier integration free?
Yes, for simple Zaps. Pike13 is not a premium app, so it works on Zapier's free plan, which includes 100 tasks a month and unlimited Zaps. The limit is the shape of the Zap: one trigger and one action. A Zap that looks a client up with Find Person before creating them, or that uses a filter, becomes multi-step and needs a paid plan. A trigger such as Person Created followed by one action elsewhere stays free.
02How many tasks does a Pike13 Zap use?
One task per action that completes. A Pike13 trigger firing never costs anything, and an action that fails is not counted either. In a Zap with several actions, each successful one counts on its own: Find Person followed by Create Person and a welcome email spends more than a single-step Zap. Watch the triggers that fire often, like Person Updated or Invoice Updated, since every edit in Pike13 means another run and more tasks.
03Is the Pike13 Zapier integration real time?
Yes. All seven Pike13 triggers are instant: Pike13 tells Zapier itself when the event happens, so nothing waits for a check on a timer. That holds on every plan, including the free one, and the editor shows a lightning bolt on Zaps built this way. The interval grid of 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise does not apply to these triggers. Event Occurrence Upcoming is the special case: it fires ahead of the session, 24 hours by default.
04What does it take to connect Pike13 to Zapier?
A Pike13 account with access to the business you want to automate. You connect it once from the Apps page of Zapier with + Add connection, sign in to Pike13 in the tab that opens and grant access. Every Pike13 action and search then asks you to pick a Business from a list, and only the businesses your login can reach appear there. If you manage several, connect with an account that covers all of them.
05Will Create Person send an email to the new client?
Yes, unless you turn it off. By default Pike13 sends every person created through the Zap an invite to set up their Pike13 account. Set the Send Invite? option to no if you would rather stay silent, for example while importing people who already know the studio. The same action also has Skip Complimentary Passes: set it to yes if your business hands out free passes to new people and you do not want them assigned here.
06What if the Pike13 operation you need is missing?
Check API Request (Beta) first. It is an advanced action that sends a custom request to Pike13 through your existing connection, so it can reach features the menu does not list, provided someone knows how Pike13 expects that request. Otherwise the integration stops at seven triggers, four actions and two searches: nothing deletes records, and no action writes invoices or transactions. Another automation tool may cover the gap, so compare before you build.
07Zapier, Make or n8n for Pike13?
Decide on criteria rather than a ranking. On Zapier, the facts to weigh are clear: seven instant triggers that fire right away on every plan, four actions including an advanced custom request, two searches with a find-or-create option on people, and a free plan limited to two-step Zaps. If your flows need searches or filters, budget for a paid plan. Then check whether the other tools reach the same Pike13 operations before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations