Recipes

Each recipe has a request that works, the sequence of tools the assistant should use and what shows up in Memberfy at the end. Swap the names and values for yours. The assistant may vary the order of the reads; what matters is the result.

All of them assume a connection with the Owner or Admin role, unless stated otherwise.

In Claude, six of these recipes are ready in the + › Connectors › Memberfy menu, already in your language: A course with a sales page, An event with tickets, Invite a class, Issue certificates to the class, Create a template with the brand's art and Create a call for papers, along with the monthly report and reviewing a call's proposals. See Ready-made recipes in the menu.

#1. A course with a sales page

For: an online school or an expert selling a recorded course.

Request:

Build the course "Excel from Scratch" in a new section called Learn: 4 modules (Basics, Formulas, Pivot tables, Charts), with 3 video lessons of about 10 minutes in each. Create the course product for R$ 297 in up to 10 installments, sellable by direct link. Leave everything as a draft and tell me what's missing to start selling.

Tools, in order:

Result: the Learn section, the Courses space Excel from Scratch, the course with 4 modules and 12 lessons, and the Excel from Scratch product as a draft, unlocking the space. The assistant points out that the lesson content (in the dashboard) and publishing are still missing.

To start selling: "Go ahead and publish the product." (publish_product). With the direct link on, the product shows up in the community's /products catalog, and the buyer pays at checkout.

#2. Group mentoring with recurring meetings

For: a mentor with a cohort that meets every week.

Request:

I want to launch Career Mentoring: a monthly subscription of R$ 390, with a 3-month minimum contract, that unlocks an events space only for mentees. Create the Career Mentoring space in the Programs section, and the 4 meetings in November, on Tuesdays, from 8 to 9:30 p.m., online, with the link https://meet.exemplo.com/mentoria. Leave the plan as a draft.

Tools, in order:

Result: the space, unlocked only for subscribers; the plan with the monthly option as a draft; the four meetings in the space.

Notes: there are no recurring events: the assistant creates one event per date. For the following months, ask again ("create the December meetings, same as November's"). See Contract length.

#3. An event with tickets

For: a community that runs paid in-person meetups.

Request:

Create the November Meetup: in person, 11/15 from 7 to 10 p.m., at Espaço Paulista, Rua Augusta 1500, Consolação, São Paulo, SP. 80 tickets at R$ 60, in up to 2 installments. Use the events space that already exists and publish the ticket.

Tools, in order:

Result: the event in the space, and the ticket on sale with 80 units.

Notes: ticket buyers get access to the space, but aren't yet added to the participant list on their own: ask them to confirm attendance at the event, or follow sales through the ticket.

#4. A plan with monthly, annual and add-ons

For: a SaaS, school or coworking with subscriptions.

Request:

Create the Growth plan: monthly at R$ 129 and annual at R$ 1,188 in up to 12 installments, both with a 7-day trial, unlocking the Customer Area space. Link the existing Coworking Extension as an add-on. Plan address: growth. Leave it as a draft.

Tools, in order:

Result: the Growth plan with both options as drafts and the add-on linked. Once published, the link is /pricing/growth.

Notes: in annual in installments, paying in installments carries Memberfy's installment interest, paid by the buyer by default. To change who pays, use the dashboard.

#5. The community's weekly summary

For: any community. Works with the Moderator role.

Request:

Put together the week's summary: who joined, the posts with the most comments, the upcoming events with how many confirmed. Then write a summary post for the Feed, in a light tone, and show it to me before publishing.

Tools, in order:

Result: the summary in the conversation and, once you approve it, the post in the Feed.

#6. Replying to comments

For: anyone who does live sessions or posts that draw questions.

Request:

Look at the comments on the post "Tuesday's live: questions" and reply to every question I haven't answered yet, thanking them and saying I'll cover it in the next live. React with 👍 to the ones that just said thanks.

Tools, in order:

Result: the replies under each comment, with your name.

Notes: the replies go out with your name, right away. Ask to see the texts first if you prefer: "show me the replies before publishing".

#7. The revenue chart

For: owner, admin or Finance.

Request:

Make a bar chart of monthly revenue over the last 12 months, and a table of revenue by product for the period. Tell me how many subscribers are past due.

Tools, in order:

Result: the assistant builds the chart and the table in the conversation (in Claude, as an artifact). The amounts are the same as in Monetization › Dashboard, with the platform fee; internal costs don't appear.

With the Reports and charts tools, the same request comes from sales_report with group_by: plan (revenue per month per plan, taken from the statement), and the weekly summary from community_overview and engagement_report.

#8. Spaces with icons and posts with images

For whom: whoever is setting up the community and wants each space recognizable in the menu.

Request:

In the Community section, create three Feed spaces: Introductions, Jobs and Technical questions, each with an icon that matches its theme. Then publish in Introductions a welcome post with this cover image: https://example.com/welcome.png. And put this photo from the last meetup in the Meetups gallery: https://example.com/meetup.jpg.

Tools, in order:

Result: the three spaces in the menu, each with its own icon; the post with its cover; the photo in the gallery. The images are stored in Memberfy: the original link can go offline later.

Notes: if the assistant uses the same icon everywhere, ask "use a different icon for each space, matching its theme". To change it later: "swap the Jobs icon for a briefcase" (update_space). See Images.

#9. Editing what already exists

For whom: whoever published something and wants to fix it.

Request:

In the post "How the community works", swap the cover for an image you generate yourself, with the community's name in green, and pin the post to the top. Then delete the duplicate post with the same title.

Tools, in order:

Result: the post with the new cover, pinned; the duplicate deleted.

Notes: you can also paste the post's link: "Edit this post: https://…". See Content and engagement.

#10. Invite a class

For whom: a school, course or program that takes in a whole class at once.

Request:

Invite these people as members, all in the March class group (create the group if it doesn't exist) and with the tag Student 2026: Ana Souza, [email protected]; Bruno Lima, [email protected]; Carla Dias, [email protected]. Show me the summary before sending.

Tools, in order:

Result: each person gets the invite e-mail (someone without an account gets the link to set a password) and joins the group with the tag. The assistant shows the result line by line: invited, already a member or error, with the reason.

Notes: up to 100 people per call; for a bigger class, the assistant splits it. Someone who was already a member doesn't stop the rest. To paste a spreadsheet, ask "read these names and e-mails from the table below". See Members.

#11. Issue certificates to the class

For whom: a school, course or event that certifies people who completed it.

Request:

Issue the completion certificate to the March class group, subject Excel from Scratch, 40 hours. Tell me first how many people will receive it.

Tools, in order:

Result: each person in the class receives the certificate, with the PDF, the image and the verification page, and the email "Your certificate is here". Under Issued, in the Certificates space, the issuing shows up with its progress.

Notes: you can mix people, groups and tags in the same issuing; someone in more than one gets a single certificate. For people who already hold a valid one and should get it again, ask "issue it even to those who already have it". See Certificates.

#12. Create a template with the brand's art

For whom: anyone with ready-made artwork from their designer.

Request:

Create a certificate template with this artwork: https://…/certificate.png. Title Certificate of participation, text "{nome} participou[ de {assunto}]". Show me how it looks.

Tools, in order:

Result: the template, active in the Certificates space, ready to issue.

Notes: the artwork must be at least 2,000 px wide, PNG or JPEG; the certificate comes out in A4 landscape. See Certificates.

#13. Create a call for papers

For whom: an association, a tech community or a company that builds an event's program from outside proposals: a call for papers.

Request:

Open the call for papers for Congress 2027: in person in São Paulo, March 12 and 13, from 9 a.m. to 6 p.m. Tracks Product, Data and Career, each with a short purpose. Proposals until November 30, talks of 20 or 40 minutes and 90-minute workshops. We cover lodging and meals; the speaker covers travel; no speaking fee. Committee review, blind. Make Ana and Bruno reviewers for Data. Leave it as a draft and show me before publishing.

Tools, in order:

Result: the call published in the Call for papers space, with the three tracks, the two days and the Data committee. Proposals start coming in; you follow them with get_review_progress and decide with decide_proposal.

Notes: the call starts as a draft and doesn't show up for members until it's published. Whoever opens the call becomes its owner. Opening a call depends on who can open a call in the space, so a member can use this recipe too, if the space allows it. In Claude, the Open a call for papers recipe in the menu builds the same request from the event, the deadline and the tracks. See Call for papers and Call for papers (the space).

#14. Who did what

For whom: an owner or admin who wants to understand what happened.

Requests:

Notes: the arguments of assistant calls come summarized, with no codes or images. See list_activity_logs.

#Tips for asking well

• Say what already exists. "In the courses space that already exists" keeps the assistant from creating another one.
• Ask for drafts. Review in the dashboard, then ask to publish.
• Ask to see it first. For posts and replies, "show me before publishing" makes the assistant stop for your approval.
• Dates with a time zone. "11/15 at 7 p.m., Brasília time" avoids surprises.
• One community per conversation. If you have two connections, turn on only the right one.

#Related

• Tools
• Money and confirmation
• Common problems