Paid community with a tier per space
A Plandalf checkout sells a basic and a founding membership. The sequence for each Offer adds the buyer to its own space, so the founding space stays closed to basic members.
Native integration
Pay in a Plandalf checkout through Stripe and the buyer lands in the Circle space they paid for. If Stripe refunds the payment, they leave that space.
No credit card required. No coding required.
CirclePlandalf connects them with native Circle steps, not a direct Stripe-to-Circle sync. Stripe takes the payment in a Plandalf checkout, then a sequence finds or creates the Circle member and adds them to a space. A refund that succeeds in Stripe can remove them from the space again. Circle's Admin API needs a Business plan or above.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → Circle | Native step | Find or Create Member invites the buyer to the community if they are new, and Add Member to Space then puts them in the space. The order matters because a person has to be in the community before a space will take them. |
| Upsell accepted | Plandalf (paid via Stripe) → Circle | Native step | A buyer who accepts the upsell can be added to a second, premium space, while everyone else stays in the first. |
| Invoice paid | Plandalf (paid via Stripe) → Circle | Native step | Update Member Fields can write a profile field such as headline or location on the member, using the member_id from Find or Create Member. |
| Invoice refunded | Stripe → Circle | Native step | Remove Member from Space takes the buyer out of the space after a full refund in Stripe. They remain a member of the community, and a person who was never in the space is skipped. |
| Member created | Circle → Plandalf | Webhook | Circle has no webhook API, so this one is wired by hand: a Circle workflow posts to the URL Plandalf shows on the trigger. Send to webhook is an Enterprise feature in Circle, and other plans use Zapier or Make for the same request. |
You need a Stripe account, and a Circle community on a plan with the Admin API (Business and above) where you are an admin.
Authorize your Stripe account in Plandalf, attach the Stripe price for your membership to an offer and publish it. Stripe collects the payment and pays out to your own Stripe account.
In your Circle community open Developers, then Tokens, create a token called Plandalf and choose Admin V1 as its type. Only community admins can see this page. Copy the token.
In Plandalf go to Automation, then Marketplace, and click Connect on Circle. Paste the token into API Key and leave Community ID blank. If the token can see several communities, Plandalf lists them and you enter the right ID under My apps.
Make a sequence on Plandalf, Checkout Completed for your checkout. Add Circle, Find or Create Member with Email Address {{trigger.customer_email}} and Name {{trigger.customer_name}}. Add Circle, Add Member to Space with the same email and your members-only Space.
Add the Remove access on refund template for the same checkout under Automation, then Templates. Pick the Space in the Remove Member from Space step, and add another removal step for each extra space the checkout grants.
Switch on Run on test purchases, buy through the test link with a Stripe test card, and check the Circle member list. New members receive Circle's invitation email, so run it with an address you control and then switch the setting off.
A Plandalf checkout sells a basic and a founding membership. The sequence for each Offer adds the buyer to its own space, so the founding space stays closed to basic members.
One checkout sells a course and a year of the community. The same payment can run a Circle sequence for the community and a course-platform step beside it, and the refund template removes both.
Each cohort has a private space and its own checkout. When a student is refunded in full, they leave that space, so it only holds people who still have a paid seat.
Checked October 26, 2026 against Plandalf's own setup guides.