Send your club's registrations, members, sessions and invoices from Abler into Mailchimp, Google Sheets, Airtable, Slack and thousands of other apps — automatically, and without writing code.
Early access · by invitation
What you need
Zapier is a service that connects apps together. You pick something that happens in Abler — a new registration, say — and choose what should happen in another app as a result. Zapier calls each of these automations a Zap.
To connect Abler you need three things: an Abler plan that includes API access, an Abler API key for your club, and a Zapier account. Zapier's free plan is enough to get started.
Anyone holding your club's API key can read your club's data. Only paste it into Zapier, never into emails or shared documents, and ask us to replace it if you think it has been exposed.
Six steps to your first Zap
1. Check your plan includes API access
Your Abler contact can confirm this in a minute. If it does not, they can tell you what the upgrade involves.
2. Ask Abler for an API key
We issue one key per club. For attendance reports and member profile exports, ask for a key with club-admin rights — the standard key does not cover those.
3. Create or sign in to Zapier
Go to zapier.com and sign up, or sign in to the account your club already uses. If several people at the club will manage Zaps, use a shared club account rather than someone's personal one.
4. Open your invitation link
While the integration is in early access it does not appear in Zapier's public search. We send you an invitation link; opening it while signed in adds Abler to your Zapier account.
5. Connect your Abler account
In Zapier, start a new Zap and choose Abler as the trigger app. When prompted, paste your API key and give the connection a name you will recognise, such as your club's name. Zapier tests the key straight away.
6. Build, test, switch on
Pick the Abler event that should start the Zap, pick the app and action that should follow, then use Zapier's test step — it pulls a real sample record from your club so you can map fields correctly. Turn the Zap on when the test looks right.
Start with New or Updated Club Member → Mailchimp Add/Update Subscriber. It uses one trigger, one action, and you will see the result in your mailing list within minutes of switching it on.
How the connection behaves
A few things about the way Zapier and Abler work together are worth knowing before you build, so nothing surprises you later.
It runs on a schedule
Zapier checks Abler for changes at a fixed interval — every 1 to 15 minutes depending on your Zapier plan. Updates arrive within a few minutes, not the same second.
It starts from today
Switching on a Zap does not send your existing members or past registrations. If you need your history in the other app, ask us about a one-off import.
Every record carries its Abler ID
Each member, registration, programme and session comes with its Abler ID. Use it as the matching key in your spreadsheet or CRM so records stay linked even when a name or email changes.
Attendance arrives once a day
The attendance report covers the previous day and is designed to run each morning. It is a complete, corrected record rather than a live register.
Members' own emails only
The mailing-list trigger sends a member's own email address and skips members who do not have one. A guardian's address is never substituted for a child's.
Some setups are guided
Attendance and profile exports need a club-admin key, and writing registrations back into Abler currently needs our help to configure. We set those up with you.
Triggers, lookups and actions
A trigger is something in Abler that can start a Zap. A lookup finds a record part-way through a Zap. An action asks Abler to do something or hand over a report. Two ideas matter when choosing a trigger:
A registration is a member's place in a programme or membership. The people and registration triggers all follow this chain — it is what a CRM or mailing list wants.
Attendance is recorded against sessions, separately from registrations. It comes from the daily attendance report action, not a trigger.
| Trigger | What it sends | Good for |
|---|---|---|
| People | ||
| New or Updated Member / Player | One record for every registered person, including children without their own email. Includes links to their guardians. | A complete people list in Airtable or a CRM |
| New or Updated Parent / Guardian | One record per guardian with the IDs of the children they are linked to. Two guardians sharing an email stay separate. | Parent contact lists, family views |
| New or Updated Club Member | One record per unique member email address. Members without their own email are left out. | Mailchimp and other mailing lists |
| Trigger | What it sends | Good for |
|---|---|---|
| Registrations and memberships | ||
| New or Updated Membership | Every registration with its member, programme, product, start and end dates, and status. | Keeping a registrations sheet or CRM in step with Abler |
| Membership Started | Registrations that are active and whose start date has arrived. | Welcome emails, onboarding tasks |
| Membership Cancelled | Registrations whose status has become cancelled. | Slack alerts to coaches, follow-up tasks |
| New Club Subscription · New Service Subscription | Simpler feeds of new registrations for the whole club, or for one programme you choose. | Notifying a specific team's coach |
| New Subscriptions (Last 7 Days) | Registrations created in the past week. | Weekly digests |
| Trigger | What it sends | Good for |
|---|---|---|
| Programmes and sessions | ||
| New Service | Programmes, courses and membership types for your club or a division. | Publishing your programme list on a website or sheet |
| New or Updated Event | Training sessions and other events for one group you choose, with time, place and changes. | Shared calendars, session reminders |
| Event Cancelled | A session that has been cancelled for the whole group — not an individual's cancelled booking. | Telling parents a session is off |
| Trigger | What it sends | Good for |
|---|---|---|
| Invoices and payments | ||
| New Invoice (Past 7 Days) | Invoices raised in your club or a division over the past week. | Reconciliation in Google Sheets or accounting tools |
| New or Updated Payment Transaction | Payment transactions as they change. Status is passed through as Abler's status code; a new invoice is not the same as a completed payment. | Payment tracking sheets |
| Lookup or action | What it does | Good for |
|---|---|---|
| Lookups | ||
| Find User | Finds a person by their Abler ID (or by kennitala where your club is authorised to use it). | Adding member details to a registration before it reaches your CRM |
| Find Service · Find Club | Finds a programme or club by ID, with a dropdown of your own programmes and clubs. | Adding programme names to records |
| Actions | ||
| Get Daily Attendance Report club-admin key | The complete attendance record for the previous day, one line per person per session. A player's RSVP and the coach's presence mark are kept separate. Up to 3 runs per hour. | A morning attendance sheet |
| Get Member and Guardian Profiles club-admin key | One page of member profiles with guardian links at a time, for a full export. Up to 10 runs per hour. | One-off exports, periodic full syncs |
| Create Subscription · Update Subscription guided setup | Registers a person into a programme, or changes an existing registration, from another app. | Registrations from your own web form or CRM |