Resources · Zapier integration

Naamly Zapier integrationAutomate Naamly with Zapier.

Naamly Zapier integration: 2 triggers, 1 action, 0 searches. Naamly can start a Zap when a group or a source type is created, and it can receive leads from your other tools through one action. Both triggers are checked on a timer, never instantly.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Naamly Zapier integration does for you

The Naamly Zapier integration links Naamly, a tool gym business owners use to talk to and manage their clients, with the rest of your apps. It works both ways, in a narrow lane: two events in Naamly can start an automation, and one action lets other tools hand Naamly a lead.

Three results come out of it. Leads that land in Naamly on their own: Create or Update Lead takes the entries of your lead form and turns them into leads in Naamly, without retyping, as long as each entry carries the first name the action requires. A log of new groups: Group Repository starts a Zap each time a group is created, so the next step can note it in a shared sheet. A record of new source types: Source Type Repository does the same when a new source type is created, so it can be noted outside Naamly too.

What Zapier does not do here: no search, no trigger on new leads, nothing to delete or move. A Zap cannot look up a lead in Naamly before acting, and it cannot react when a lead is added there. If those gaps matter, see our n8n vs Zapier comparison before you build.

Speed is the other thing to know: both triggers are polling triggers, so on the free plan a new group or source type reaches your Zap at the next check, not when it happens.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, 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. Once the Zap is on, Zapier waits for it. Naamly has two of them.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you. Naamly offers one.
Task
The unit Zapier bills: one action your Zap completes successfully. The number attached to your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen yet.
Instant trigger
A trigger the app reports by itself, the moment the event happens. Neither Naamly trigger works this way.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there 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 a Naamly Zap really costs

Zapier bills actions, not triggers. With Naamly, the line that costs you is mostly Create or Update Lead, one task each time it goes through.

  • Premium appNo, it works on the free plan
  • Free plan100 tasks a month, Zaps of two steps
  • Cost of a trigger0 tasks

A task is counted each time your Zap carries out an action and it works. The trigger costs nothing, and neither does the checking, however often Zapier looks. An action that fails is not counted. In a Zap with three actions, each success counts on its own, so it eats three times more than a one-action Zap. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. A filter or a second action calls for a paid plan. Both Naamly triggers follow the interval grid below.

Connect

Connect Naamly to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page. A connection is your Naamly account linked to Zapier once, then reused by every step that needs it. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Add the connection

    Click + Add connection, type Naamly in the search box of the dialog and pick it from the results. Then click Add connection to open the Naamly sign-in in a new tab.

  3. 03

    Sign in and grant access

    In that tab, sign in to Naamly with the account your gym business uses, then grant Zapier access to it. Back in the editor, the connection can be picked in any Zap that uses Naamly, as a trigger or as the lead action.

First Zap

Your first Zap: a task for each new group

GoalEach group created in Naamly that matches your condition opens a task in your task tool, so someone follows it up.

  1. 01

    Create the Zap and pick the trigger

    Build a new Zap, choose Naamly as the app that starts it and Group Repository as the event. Select the Naamly connection you set up earlier.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so the rest of the Zap is mapped on a real group and the fields it really carries.

  3. 03

    Add the filter

    From the plus icon, add a Filter step and set its three boxes: the field to look at, the rule, the value. A filter makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the task action

    Add the action in your task tool, pick the event that creates a task, and map the values the trigger returned into its title and description. Test this step too and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only groups created after that moment open a task, and each one reaches the Zap at the next check.

Triggers

Naamly triggers on Zapier

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

1

Group Repository

Polling trigger

In Zapier“Triggers when a group is created.”

Creating a group in Naamly starts this Zap, and what the trigger returns about it can feed every step that follows; the test shows which fields.

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
keep a shared list of the groups your team sets up in Naamly, or open a task each time a new one appears.
Watch out
groups created before you publish are not picked up; only the ones that appear afterwards start the Zap, at the next check.
2

Source Type Repository

Polling trigger

In Zapier“Triggers when a new source type is created.”

Whenever a new source type is created in Naamly, Zapier picks it up and runs your Zap with it, so the change shows up outside the app too.

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
keep a list of the source types created in Naamly in a shared sheet, readable outside the app.
Watch out
the trigger has no required field, so test it once and read the fields it returns before you map them.
Actions

The Naamly action on Zapier

Naamly gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create or Update Lead

Action

In Zapier“Creates a Lead OR Updates a lead”

This step hands Naamly a lead: it creates one, or updates one, from the values your earlier steps bring in.

When to use it
send the people who fill in your lead form straight into Naamly, so nobody copies them by hand.
Watch out
First Name is required; map the first name of your lead form into it, then check at the test whether a lead was created or updated.
When it breaks

When a Naamly Zap breaks

Zapier links no help article and no documented limit to Naamly, so the cases below come from how Zapier itself works.

Four of them are worth knowing before you publish. If a Zap does not behave the way you planned, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. Groups, source types and form entries that already existed stay out; moving them is a separate job.
  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your task count. Check where each step writes.
  • Flood protection

    After a bulk import or a migration, a trigger may suddenly return a huge batch, and Zapier's flood protection can hold that batch back.
  • The same item never runs twice

    Both Naamly triggers are polling triggers: Zapier keeps track of what it has already seen, so the same group or source type does not start the Zap twice.
Need help

Need help automating Naamly with Zapier?

A person reads every message.

FAQ

Naamly and Zapier: your questions

01Is the Naamly Zapier integration free?
Yes. Naamly is not a premium app, so its two triggers and its action work on the free plan of Zapier. That plan gives you 100 tasks a month and as many Zaps as you like, with one condition: each Zap holds two steps, one trigger and one action. A form entry sent to Create or Update Lead fits exactly, and so does a Naamly trigger followed by one action elsewhere. Add a filter or a second action and the Zap needs a paid plan.
02How many tasks does a Naamly Zap use?
Nothing for the trigger: Zapier can check Group Repository or Source Type Repository as often as your plan allows without counting anything. Each action that completes successfully counts as one task, so every lead that Create or Update Lead handles costs one. A Zap with three actions spends three per run. An action that fails is not counted against your plan. A few apps take more than one task for some actions, so keep an eye on the other app in your Zap.
03Does Naamly start Zaps in real time?
No. Both Naamly triggers are polling triggers: Zapier checks for new groups and source types at regular intervals, every 15 minutes on Free, every 2 on Professional and every minute on Team and Enterprise. On the paid plans you can also run a check by hand from the editor. The action side is different: Create or Update Lead runs when the step before it hands over its data, whatever triggered the Zap.
04What does connecting Naamly to Zapier require?
An account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once, from the Apps page of your Zapier account, then reused by every Zap that uses Naamly, whether as a trigger or for the lead action. If you plan to send leads in, make sure the source of those leads carries a first name, since Create or Update Lead requires one.
05Why does Create or Update Lead ask for a first name?
Because First Name is the one required field of that action: the step cannot run without it. In practice that means the trigger before it must bring a first name to map, which is why a lead form feeding Naamly should always ask for one. When you test the step, look at the result in Naamly as well, to see whether the action created a new lead or updated an existing one.
06What if the Naamly operation you need is missing?
Then the editor cannot offer it. The Naamly page on zapier.com shows the current list of operations, and only those can be picked when you build a Zap. Before giving up, test what exists: Group Repository and Source Type Repository may already return the information you are after, and the fields of Create or Update Lead are listed when you set up the step. Only the test tells you what each one really returns.
07Zapier, Make or n8n for Naamly?
Decide on criteria rather than on a winner. Coverage first: on Zapier, Naamly offers two triggers and one lead action, with no search, so compare what each tool offers for this app. Then the billing model: Zapier counts each successful action as a task and never bills the trigger or its checks. Then speed: both triggers are polling triggers, so the interval of your plan sets the pace. Finally the shape of your flows, since anything beyond two steps needs a paid plan on Zapier.