Resources · Make integration

Scarf Club Make integrationAutomate Scarf Club with Make.

Can Make handle your Scarf Club members for you? The Scarf Club Make integration gives you 12 action modules: invites, members, tags, badges, emails. This guide is for community managers who start with Make, and walks you through connecting and building a first scenario.

Try the Scarf Club integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Scarf Club Make integration do?

The Scarf Club Make integration lets Make act on your Scarf Club account for you. You build a scenario, the automation made of modules chained together, and Make invites people, files members into lists and spaces, adds tags or badges and sends emails, without any code.

Every new customer gets a club invite. When a sale or a form entry lands in another app, Create Club Invite sends the invitation, then Create List Member files the person into the right list.

Members earn visible recognition. Create User Badge rewards someone who reached a milestone you track elsewhere, and Create Member Tag marks the segment they belong to, so your later emails target the right people.

Departures are cleaned up. When a subscription ends, Remove Space Member, Delete List Member and Delete Club Member take the person out step by step, and Send an Email confirms it.

Know the limits before you start. Scarf Club has no trigger in Make, so a scenario starts from another app or from a schedule. Its modules come without an official description either: what this page says they do is read from their names, so check each one with Run once. Make's own documentation also says it can't document this app fully for lack of public information, which leaves Execute a GraphQL Query as the way to reach anything the other modules skip. If a module behaves unexpectedly, the Make troubleshooting guide is the place to start. To weigh the platform itself, read our Make review, and if you also look at n8n, the n8n vs Make comparison sets the two side by side.

Connect

How do you connect Scarf Club to Make?

  1. 01

    Add a Scarf Club module

    In your scenario, click the +, search for Scarf Club and pick any of its modules. Then click Create a connection. A connection is your Scarf Club account linked to Make once and reused by every Scarf Club module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when you run several accounts. Then either authorize Make on the Scarf Club page that opens, or paste the key Scarf Club gives you, depending on what the window asks for.

  3. 03

    Save and reuse it

    Click Save. The module now shows your connection, and every other Scarf Club module you add later offers it in its list, so you never sign in twice for the same account.

First scenario

Your first scenario: invite and welcome a new member

GoalWhen a new person signs up in another app, Make invites them to your Scarf Club and sends them a welcome email.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the trigger from the app where your sign-ups arrive, since Scarf Club has none.

  2. 02

    Add Create Club Invite

    Click the + on the right of the trigger, search for Scarf Club and pick Create Club Invite. Click Create a connection to link your account if it isn't done yet.

  3. 03

    Map the new person

    Fill the module fields by mapping data from the trigger. Each bundle, one sign-up here, flows from the first module into the invite, so every new person gets their own invitation.

  4. 04

    Add the welcome email

    Click the + again and add Send an Email. Map the details from the earlier modules so the message goes to the person who was just invited.

  5. 05

    Test with Run once

    Click Run once, trigger a test sign-up and read the bundles each module received. Each module run counts as one operation, the unit Make counts on your plan.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or keep it instant if that app calls Make itself. Switch the scenario on and it runs by itself.

Modules

What can Scarf Club do in Make?

Scarf Club gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Scarf Club1

Create Club Invite

ActionIn the docs only

Brings a new person into your club: Make creates the invitation for you, so nobody has to send it by hand after a sale or a sign-up in another tool.

When to use it
at the start of an onboarding flow, right after the step that tells you someone should join.
Watch out
if your source app can fire twice for the same person, add a filter before this module to avoid double invites.
Scarf Club2

Create List Member

ActionIn the docs only

Puts a member into one of your Scarf Club lists, which keeps your audiences sorted without manual copy and paste each time a new profile appears.

When to use it
after an invite, when the source data already tells you which list the person belongs to, such as a plan or a region.
Watch out
the documentation doesn't describe how lists behave, so test with Run once on a single contact first.
Scarf Club3

Create Member Tag

ActionIn the docs only

Labels a member with a tag, so you can later group, filter or target people by interest, plan or event without rebuilding the segment yourself.

When to use it
when an event in another app says something about the person, like a purchase of a given product.
Watch out
its opposite is Remove Member Tag; pair the two when a tag must follow a status that changes.
Scarf Club4

Create Space Member

ActionIn the docs only

Opens a space of your club to a member, which gives paying customers or a cohort access to the room meant for them, with no admin clicking.

When to use it
when a payment, a contract or a course enrollment in another app should unlock a specific space.
Watch out
the documentation doesn't say whether the person must join the club first; placing this module after the invite step keeps the order safe.
Scarf Club5

Create User Badge

ActionIn the docs only

Awards a badge to a user, a visible reward that shows the community who reached a milestone, finished a program or helped others.

When to use it
when another tool records the achievement, such as a completed course or a closed support ticket, and you want recognition to follow.
Watch out
Delete Member Badge takes it back; think about what should happen if the achievement is cancelled.
Scarf Club6

Delete Club Member

ActionIn the docs only

Removes a person from the club entirely, the cleanest way to close access when someone leaves, cancels or asks to be taken out.

When to use it
at the end of an offboarding flow, once lists and spaces are already cleaned.
Watch out
a Delete module can't be undone by Make; test on a dummy member and add a filter so only the right people reach this step.
Scarf Club7

Delete List Member

ActionIn the docs only

Takes someone out of a list while leaving them in the club, useful when a person changes segment but should stay in the community.

When to use it
when a plan downgrade or an unsubscribe in another tool means a list no longer fits them.
Watch out
this is a deletion, not a move; add Create List Member afterwards if the person should land in another list.
Scarf Club8

Delete Member Badge

ActionIn the docs only

Withdraws a badge from a member, so the recognition shown in the club stays accurate when a status expires or was granted by mistake.

When to use it
when a certification lapses, a refund cancels a purchase, or a test scenario handed out badges it shouldn't have.
Watch out
run it only on the member concerned; a loose filter would strip badges from everyone in the bundle flow.
Scarf Club9

Execute a GraphQL Query

ActionIn the docs only

Sends a GraphQL query you write yourself to Scarf Club, your way to reach data or actions that the eleven other modules don't cover.

When to use it
when no ready-made module fits and you know which query Scarf Club expects.
Watch out
Make's documentation for this app is limited, so you need Scarf Club's own reference to write the query; test it with Run once before relying on it.
Scarf Club10

Remove Member Tag

ActionIn the docs only

Strips a tag from a member, so your segments reflect what is true today rather than what was true when the tag was added.

When to use it
when the event that justified the tag ends, such as a trial that expires or an event that is over.
Watch out
the documentation says nothing about a tag that is already gone, so read the Run once result on a member without it before switching the scenario on.
Scarf Club11

Remove Space Member

ActionIn the docs only

Closes a space to a member without removing them from the club, so access follows exactly what the person paid for or signed up to.

When to use it
when a cohort ends or a subscription tier drops, and the person keeps a basic membership.
Watch out
it doesn't touch the club membership itself; use Delete Club Member when the person should leave for good.
Scarf Club12

Send an Email

ActionIn the docs only

Sends an email through Scarf Club, which lets the welcome, the reminder or the goodbye message go out at the same moment as the change it announces.

When to use it
as the last module of a flow, to confirm an invite, a new badge or a removal to the person concerned.
Watch out
every run sends a real message; point the first Run once tests at your own address.
Need help

Need help automating Scarf Club with Make?

A person reads every message.

FAQ

Scarf Club and Make: common questions

01Is the Scarf Club Make integration free?
Yes. Scarf Club is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and count usage in credits, meaning operations, per month. Any cost on the Scarf Club side is outside what Make charges.
02What do you need to connect Scarf Club to Make?
A Scarf Club account and a Make account. Make's documentation lists no prerequisite for this app and no specific steps, so you follow the generic path: add a Scarf Club module, click Create a connection, optionally name it, authorize Make on the Scarf Club page or paste the key Scarf Club provides, then click Save. The connection is then reused by all 12 modules. If the window asks for something you can't find, look in your Scarf Club account settings.
03Does Scarf Club have a trigger in Make?
No. All 12 Scarf Club modules are actions, so nothing in Scarf Club itself can start a scenario. Two ways around it. Start with a trigger from another app, such as a form, a store or a CRM, instant when that app calls Make through a webhook, scheduled otherwise. Or start the scenario on Make's schedule, every 15 minutes by default, and let the Scarf Club modules act on what the first module returns.
04What if a Scarf Club module is missing in Make?
Use Execute a GraphQL Query. Scarf Club has no Make an API Call module, but this action sends a query you write yourself, which covers what the eleven other modules skip. Make's documentation warns it can't describe this app fully for lack of public information, so you will need Scarf Club's own reference to write the query. If that gets too technical, another app of your stack can hold the data, or the team can build the scenario with you.
05Should you use Make or n8n for Scarf Club?
It depends on what each tool offers for this app. On Make, you get 12 ready-made actions, no trigger, a GraphQL module for the rest and access from the Free plan. Before choosing, check whether n8n has a Scarf Club node and which operations it covers, then compare with the scenario you have in mind. Pick the tool whose modules match your flow without workarounds, and the one your team already knows how to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations