Skip To Content
Atlasby MeetCal
  • TrainingWrite the program on the web, log it set by set on the phone.
  • Messaging & Video ReviewLift videos, voice memos and frame-by-frame reviews.
  • GroupsOne program for a whole team.
  • Meets & CompetitionMeet results from MeetCal, and a plan for the next one.
  • AnalyticsCharts from logged training, and where every PR came from.
  • QuestionnairesSession check-ins, and questions you send after a meet.
  • DocumentsWaivers and forms athletes sign in the app.
  • Youth AthletesSafeSport and MAAPP compliant messaging, with guardians.
  • DesktopThe coach console as an app for Mac, Windows and Linux.
  • AI AssistantsAdd Atlas to Claude, ChatGPT, Gemini or Grok, and hand it roster admin and program edits.
  • ConnectionsOura, FatSecret and the Coach API.
All Features →
PricingDownloadDocsBlog
Sign InSchedule A DemoStart Free

Blog

How to Add Paying Athletes to an Atlas Group Program Automatically from Stripe, Shopify, or Your Own Website

November 12, 2026Maddisen15 min read

On This Page

  1. What the connection actually does
  2. Before you start
  3. Step 1: Make the private URL
  4. The simplest way for Stripe (no Make, no Zapier)
  5. Stripe steps
  6. The simplest way for Shopify (no Make, no Zapier)
  7. Shopify steps
  8. Why other stores still need a helper
  9. The free way for other stores: Make
  10. Scenario 1: Add buyers (Squarespace or WooCommerce)
  11. Scenario 2: Remove people who cancel
  12. Stripe through Make (optional)
  13. Shopify subscription cancellations through Make
  14. The paid convenience option: Zapier
  15. Zap 1: Add buyers
  16. Zap 2: Remove people who cancel
  17. Test it with a spare address
  18. Other ways that cost nothing
  19. Your group's join link
  20. Your own AI assistant
  21. What the buyer sees
  22. When something goes wrong
  23. Try it
  24. Sources

If you sell a weightlifting group program on your own club website, you keep every dollar. Atlas takes no cut.

The selling part is easy. The admin after it is what wears you down.

Someone pays at 11 PM, and you have to add them to the group. Someone cancels, and you have to remember to take them off. Miss one and you've got a paying athlete with no program, or a former athlete still training on a program they stopped paying for.

Every Atlas group program can take those adds and removals on its own. When a buyer's email lands, Atlas sends them an invitation and adds them to the group. When a cancellation lands, Atlas takes them off. This post starts with the direct paths for Stripe and Shopify sellers (straight from the store into Atlas, no middle tool), then the free Make setup for other stores, then Zapier if you'd rather pay for the convenience.

What the connection actually does

Atlas needs three pieces of information:

  • action: add or remove
  • email: the buyer's email
  • name: the buyer's name (only needed for adds)

That's it. A few details from the Atlas docs that matter in practice:

  • Adding someone twice doesn't send a second email. Removing someone who isn't in the group changes nothing. So if your store sends the same order twice, nothing breaks.
  • Removing someone keeps their history. If they buy again later, adding them brings their history back.
  • If no name comes through, Atlas makes one from the email. jane.doe@example.com joins as Jane Doe.
  • Atlas logs every delivery. The group's Settings lists the last 50 deliveries and how each one ended, including the reason for any that were refused.

There's no password to set up. The private URL itself is the key, so treat it like a password. If it ever gets out, make a new one and the old one stops working.

Before you start

  • You need a group program in Atlas. You have to be the group's coach or a club admin to turn this on.
  • Check your seats. Group members don't count toward your plan's athletes. Every plan includes 10 group members. Past that, paid plans add seats in blocks as people join, and drop the ones you don't need at renewal. If your plan has no room, Atlas refuses the add.
  • Know which email buyers will use. The buyer signs in to the Atlas app with the same email they paid with. That's how their program finds them.

Step 1: Make the private URL

In the coach console, open the group, then go to Settings, then Webhook, and choose Make Webhook URL.

Copy it right away. Atlas shows it only once. Paste it somewhere safe, like your password manager.

If you lose it, choose Make Webhook URL again (or New URL if one is already on) and paste the new one everywhere you used the old one. The old URL stops working as soon as you make a new one.

The simplest way for Stripe (no Make, no Zapier)

If you sell through Stripe (Payment Links, Checkout, or your own Stripe checkout), Atlas has a direct Stripe path. You copy Atlas's Stripe URL into Stripe, save Stripe's signing secret back into the group, and that's it. No Make. No Zapier. No middle step rewriting the sale into three fields.

This is the newest and simplest option for Stripe sellers. Shopify has the same kind of direct path, covered next. Other stores (Squarespace, WooCommerce) still need a helper in the middle, covered further down.

What it handles:

  • A paid checkout (checkout.session.completed, or checkout.session.async_payment_succeeded for payments that clear a little later) adds the buyer. Atlas takes the email and name from Stripe's customer details on that checkout.
  • An ended subscription (customer.subscription.deleted) removes the member whose checkout started that subscription. Atlas remembers the subscription when the buyer joins, so you don't give it a Stripe key. If a buyer has another running subscription to the same group, they stay.
  • The buyer has to check out with the same email they'll use to sign in to Atlas.
  • Every other Stripe event is ignored. One-time Payment Links that aren't a subscription won't fire a removal later, so you'd take those people off yourself if they shouldn't stay.
  • Each Stripe event is acted on once, so a repeat delivery won't add anyone twice.

Stripe steps

  1. In Atlas, open the group, then Settings, then Webhook, and make the private URL if you haven't already (Make Webhook URL). In the Stripe section below it, choose Copy Stripe URL. It's your webhook URL with /stripe on the end.
  2. In Stripe, open the Webhooks page. Stripe's current docs put this under Workbench → Webhooks. The older Developers → Webhooks path still works too (Stripe webhooks docs).
  3. Choose Create an event destination (or add an endpoint, depending on which Stripe page you're on).
  4. Set the Endpoint URL to the Stripe URL you copied from Atlas.
  5. Select these events:
    • checkout.session.completed (someone finishes paying, including through a Payment Link)
    • checkout.session.async_payment_succeeded (a delayed payment finally goes through)
    • customer.subscription.deleted (a subscription ends)
  6. Save it. On the endpoint's settings, Reveal the Signing secret (it starts with whsec_). Copy it.
  7. Back in the group's Webhook settings in Atlas, paste it into Signing Secret in the Stripe section and choose Save Stripe. Atlas confirms with "Signing secret saved." and from then on shows only the last four characters.
  8. Optional: if you sell more than one thing from the same Stripe account, paste the Payment Link IDs (each starts with plink_, up to 20) into Payment Links. Leave it empty to add every buyer. With IDs saved, only checkouts from those links add members.
  9. Run a test purchase with a spare email (see the test section below). In Atlas, the group's Settings should show the add in Webhook Deliveries. In Stripe, the endpoint's event deliveries should show a successful delivery.

To stop using it, choose Remove Stripe in the same section. Stripe deliveries then stop adding and removing members.

Once that's on, every Stripe sale and cancellation for that checkout updates the group on its own.

The simplest way for Shopify (no Make, no Zapier)

If you sell through Shopify, Atlas has a direct path too. You copy Atlas's Shopify URL into Shopify, save Shopify's signing secret back into the group, and that's it. No Make. No Zapier. No middle step rewriting the sale into three fields.

What it handles:

  • A paid order adds the buyer. Atlas takes the email from the order and the name from the customer on that order.
  • Cancelling that same order removes them. Atlas remembers the paid order when the buyer joins, so cancelling an order Atlas never saw paid removes nobody (it shows as Refused). If a buyer has another paid order for the same group, they stay.
  • A refund does not cancel the order. Cancel the order in Shopify to take the member off.
  • The Order payment and Order cancellation webhooks this path uses have no subscription-ended event. If a subscription app bills your members, take them off from the group's members list when their subscription ends, or use Make or Zapier for that part, further down.
  • Each paid order and each cancellation is acted on once, so a repeat delivery won't add anyone twice.

Shopify steps

  1. In Atlas, open the group, then Settings, then Webhook, and make the private URL if you haven't already (Make Webhook URL). In the Shopify section below it, choose Copy Shopify URL. It's your webhook URL with /shopify on the end.
  2. In the Shopify admin, open Settings, then Notifications, then Webhooks.
  3. Create two webhooks, both in JSON format, both with the Shopify URL you copied. For each one, choose the latest Webhook API version, then save:
    • Order payment
    • Order cancellation
  4. The same Shopify page shows the signing secret your webhooks are signed with. Copy it.
  5. Back in the group's Webhook settings in Atlas, paste it into Signing Secret in the Shopify section and choose Save Shopify. Atlas confirms with "Signing secret saved." and from then on shows only the last four characters.
  6. Optional: if you sell more than one thing from the same Shopify store, paste the product IDs (the number at the end of the product's address in the Shopify admin, up to 20) into Product IDs. Leave it empty to add every buyer. With IDs saved, only orders that include one of those products add members.
  7. Run a test purchase with a spare email (see the test section below). In Atlas, the group's Settings should show the add in Webhook Deliveries. Then cancel that test order, and it should show the removal.

To stop using it, choose Remove Shopify in the same section. Shopify deliveries then stop adding and removing members.

Once that's on, every paid Shopify order and cancellation updates the group on its own.

Why other stores still need a helper

Your first thought for Squarespace or WooCommerce might be to paste the Atlas URL straight into the store's own webhook settings. That won't work today. Those stores send a different shape of data than Atlas's plain add/remove message.

In plain terms, Atlas looks for an email right at the top of the message. Squarespace and WooCommerce tuck the buyer's email somewhere else, and neither of them says "add" or "remove."

So something has to sit in the middle and turn "new order" into the three fields Atlas wants. The good news is that this can cost nothing. (Stripe and Shopify sellers can skip this section and use the direct paths above, except for a Shopify subscription app's cancellations, which still need a helper.)

The free way for other stores: Make

Make is an automation tool that we support. It's the free way to connect stores that can't post to Atlas directly. As of November 2026, Make's Free plan comes with 1,000 credits a month, and its HTTP module (the part that sends data to a web address) is on every plan, including Free. The Free plan lets you have two scenarios switched on at once, which is exactly what you need: one to add buyers and one to remove people who cancel.

How far 1,000 credits go. Each step that runs uses a credit. Adding a buyer is two steps (the sale coming in, then the message to Atlas), so the Free plan has room for hundreds of sales a month.

One thing to watch. Some store triggers in Make are "instant," which means the store tells Make the moment a sale happens. Others check your store on a schedule, and every check uses a credit even when there's no new order. Stripe's trigger is instant, if you still want Make for Stripe for some reason. If your store's trigger isn't marked instant, set it to check a few times a day, not every 15 minutes, or the checks alone will eat your credits.

Scenario 1: Add buyers (Squarespace or WooCommerce)

  1. Sign up for Make and start a new scenario.
  2. Add your store's module for a new paid order (Squarespace, WooCommerce, or another store Make supports). Prefer an instant trigger when the store has one.
  3. Add the HTTP module to make a request. Set it to POST, paste your Atlas webhook URL, and send a JSON body with three fields: action set to add, email mapped to the buyer's email from the order, and name mapped to the buyer's name.
  4. Run it once and make a test purchase (see the test section below), then switch the scenario on.

Scenario 2: Remove people who cancel

This one only matters if you sell a subscription.

  1. Start a second scenario with your store's "subscription ended" or "subscription cancelled" trigger.
  2. If that event only gives you a customer ID, add a step that looks up the customer so you get their email.
  3. Add the HTTP module: POST, the same Atlas URL, and a JSON body with action set to remove and email mapped to that email.
  4. Test it and switch it on.

Stripe through Make (optional)

If you'd rather not use the direct Stripe path yet, Make still works. Use Stripe's Watch Events for checkout.session.completed to add, and customer.subscription.deleted plus Retrieve a Customer to remove, then the same HTTP step to Atlas.

Shopify subscription cancellations through Make

Shopify's direct path already handles paid orders and cancelled orders. If a subscription app bills your members, and that app has a Make trigger for a subscription ending, use Scenario 2 above for those cancellations. Paid orders should still go through the direct Shopify path.

The paid convenience option: Zapier

If you already pay for Zapier, or you'd rather click through the setup the Atlas docs walk through step by step, Zapier works well. Stripe and Shopify sellers who want zero middle tools should use the direct paths above instead.

Shopify's direct path already handles paid orders and cancelled orders. If a subscription app bills your members, and that app has a Zapier trigger for a subscription ending, use Zap 2 below for those cancellations. Paid orders should still go through the direct Shopify path.

What it costs. The step that sends data to Atlas is called Webhooks by Zapier. Zapier lists it as a premium app, so it only works on paid plans (Professional and up) or during a trial. Zapier's Free plan won't do it. As of November 2026, Professional starts at $19.99 a month when billed annually, or $29.99 billed monthly, and new accounts get a 14-day trial of Professional.

Zap 1: Add buyers

  1. In Zapier, make a new Zap.
  2. Trigger: pick your store and its "new sale" event. For Squarespace, WooCommerce, or another store, pick its event for a new paid order. Stripe and Shopify sellers should use the direct paths above.
  3. Action: pick Webhooks by Zapier, then POST.
  4. URL: paste your Atlas webhook URL.
  5. Payload type: json.
  6. Data: add three rows:
    • action = add
    • email = the buyer's email from the trigger
    • name = the buyer's name from the trigger
  7. Test it, then turn the Zap on.

Zap 2: Remove people who cancel

  1. Make a second Zap.
  2. Trigger: the event for a subscription ending. The Atlas docs give Stripe's Canceled Subscription as the example. Other stores name this event differently, so look for the one that fires when a subscription ends.
  3. Action: Webhooks by Zapier, then POST, same URL, payload type json.
  4. Data: two rows:
    • action = remove
    • email = the customer's email
  5. Test it and turn it on.

Test it with a spare address

Whichever path you use, test with an email that has no Atlas account. Your own email will be refused, because you already coach in the club.

The Atlas docs suggest a plus address. If you use Gmail, adding a plus sign and a word before the @ still lands in your inbox, so you+atlastest@gmail.com works as a test buyer. Not every email provider supports this. If yours doesn't, use any spare address you can check.

After the tests, open the group's Settings in Atlas. The add should show as Invited and the removal as Removed under Webhook Deliveries.

Other ways that cost nothing

Your group's join link

This one needs no extra tools at all. Every group program has a join link, and it's switched on when you make the group. Put that link on your store's thank-you page or in the order confirmation email, and buyers join from there.

The catch: anyone with the link can join. If a buyer forwards it to a friend, the friend gets in too. And nobody is removed automatically when they cancel, so you take people off yourself from the group's members.

If the link gets passed around, you can make a new one in the group's settings, and the old link stops working. The docs say it plainly: use the paid signup connection when only paying athletes should get in.

Your own AI assistant

If you already let an AI assistant use Atlas for you, it can add and remove group members by email. That works well for a weekly catch-up: "Here are this week's new orders and cancellations, update the group." It isn't automatic, though, because someone has to ask. Taking people off also needs a permission that's off by default, which you'd have to turn on when you sign the assistant in.

What the buyer sees

When the add goes through, the buyer gets an email invitation to Atlas. They download the app and sign in with the same email they paid with, and the group's program is there from that day.

A couple of edge cases from the docs:

  • Someone who trains with another club gets asked in the app before moving to yours.
  • Someone your club already coaches one-on-one is refused. Move them into the group yourself from their Settings in Atlas.

When something goes wrong

The delivery log in the group's Settings tells you what happened. Here's what Atlas sends back, in plain terms:

  • Done: invited, restored, already a member, removed, or not a member. All fine.
  • Refused: a bad email, a message that's too large, or someone your club already coaches individually. Sending the same thing again gets refused again, so fix the data first.
  • Not found: the URL was turned off or replaced, or the group has ended. Paste in your newest URL.
  • Too many: Atlas takes at most 300 adds and removals an hour per group, and 10 an hour for the same email. Wait and try again.
  • Atlas couldn't take it: try again later. If it keeps happening, email me.

For the Stripe direct path, also check Stripe's event deliveries on that endpoint. A failed signature usually means the signing secret in Atlas doesn't match the one Stripe shows for that endpoint.

For the Shopify direct path, also check Shopify's webhook deliveries. A failed signature usually means the signing secret in Atlas doesn't match the one Shopify shows on that page.

Try it

Make a group in Atlas, make its private URL, and run one test buyer through. After that, paid sales and cancellations update your group on their own, with the limits above for refunds, one-time Payment Links, and Shopify subscription apps. Start Free at atlas.meetcal.app, and if you get stuck, email me at maddisen@meetcal.app.

Sources

All facts checked November 9, 2026, with Stripe and Shopify direct paths rechecked November 12, 2026.

  1. Atlas Coach API Reference, Group Programs (webhook, Connect Stripe Directly, Connect Shopify Directly, Sell A Group Program On Your Website): https://atlas.meetcal.app/docs/api
  2. Atlas Pricing (group program members): https://atlas.meetcal.app/pricing
  3. Make Pricing: https://www.make.com/pricing
  4. Make, Stripe modules (Watch Events, Retrieve a Customer): https://apps.make.com/stripe
  5. Make Community, Free plan active scenarios: https://community.make.com/t/free-status/113295
  6. Zapier Pricing: https://zapier.com/pricing
  7. Zapier, How to get started with Webhooks by Zapier: https://help.zapier.com/hc/en-us/articles/8496083355661-How-to-get-started-with-Webhooks-by-Zapier
  8. Zapier, What is a premium app: https://help.zapier.com/hc/en-us/articles/37982571569421-What-is-a-premium-app
  9. Stripe, Receive events with webhooks (Workbench → Webhooks, Create an event destination, signing secret): https://docs.stripe.com/webhooks
  10. Atlas PR 1826 (Stripe direct webhooks, merged November 11, 2026): https://github.com/memohnsen/Atlas/pull/1826
  11. Atlas PR 1855 (Shopify direct webhooks, merged November 11, 2026): https://github.com/memohnsen/Atlas/pull/1855

Keep Reading

  • November 16, 2026 · 9 min readBring your own AIA weightlifting coach on built-in AI in coaching apps like CoachLogik, BridgeAthletic, CoachRx and Everfit: what it costs you whether you use it or not, what it can't reach, and why an open platform that works with your own AI gives you more. Checked Nov 16, 2026.
  • November 14, 2026 · 11 min readMCP vs CLI, two ways to plug your AI into AtlasA weightlifting coach explains the two ways to connect your own AI assistant to Atlas: the MCP connector for chat apps like Claude, ChatGPT, Grok and Gemini, and the CLI for agents like Claude Code and Codex. What each is good at, step by step setup, and how you stay in control.
  • November 13, 2026 · 8 min readAtlas vs CoachRx: same "every feature on every plan" promise, built for different coachesA weightlifting coach compares Atlas and CoachRx on the free plan vs the 14-day trial, the 2% Business Suite fee, built-in AI vs bringing your own, and who each platform is built for. CoachRx facts checked November 13, 2026.
Atlas
MeetCalBlogSchedule A DemoPrivacy PolicyTerms Of UseSupportPowered by fatsecret Platform API© 2026 MeetCal LLC