Resources · Make integration

Flenski Make integrationAutomate Flenski with Make.

Can Make create Flenski profiles and hand out plans for you? The Flenski Make integration gives you 5 action modules, from profile creation to plan changes. This guide walks you through the connection, a first scenario and each module.

Try the Flenski integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Flenski Make integration do?

The Flenski Make integration links your Flenski account to Make so a scenario, the automation you build in Make, can act on Flenski without code. Each module is one brick of that scenario. Flenski brings 5 of them, all actions, so the scenario starts from another app or from a schedule.

Open an account the moment someone signs up. A form or a store in another app starts the scenario, then Create a Profile sets up the person in Flenski and Add a Plan for a Profile attaches the right plan, so nobody copies details by hand.

Take a plan back when access ends. When a cancellation lands in your billing tool, Revoke a Plan for a Profile removes the plan from that profile, and the change happens even if nobody on the team remembers it.

Reach what the list leaves out. Make an API Call calls any endpoint of the Flenski API with the same connection, which covers the requests the four named modules do not.

A word of caution: the Flenski documentation on Make gives no description for these modules and says its content is AI-generated, so test every module with Run once before you trust it. If you get stuck, the Make troubleshooting guide helps, and the n8n vs Make comparison explains how the two tools differ. For a guided start, see our Make training.

Connect

How do you connect Flenski to Make?

  1. 01

    Copy your Flenski API key

    Sign in to Flenski and open the profile settings page. Your API key is displayed on that screen: copy it and keep it at hand, because Make asks for it in the next step. No Flenski account yet? Create one first.

  2. 02

    Add a Flenski module in Make

    In your scenario, search for Flenski, pick any of its modules and click Create a connection. A connection is your Flenski account linked to Make once and reused by every Flenski module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied from Flenski, or follow the on-screen instructions, then save the connection.

First scenario

Build your first scenario with Flenski

GoalWhen a new customer signs up in another app, Make creates their Flenski profile and gives it a plan.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Flenski has no trigger, so pick the module of the app where signups arrive, such as your form tool.

  2. 02

    Add Create a Profile

    Click the + on the right of that first module, search for Flenski and choose Create a Profile. Select your connection or click Create a connection.

  3. 03

    Map the signup data

    Fill the module fields by mapping data from the first module. Each bundle, one item passing from one module to the next, carries one new customer into Flenski.

  4. 04

    Give the profile a plan

    Add Add a Plan for a Profile with the next + and map the profile that Create a Profile just returned, so the plan goes to the right person.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time, then open each module to read the bundles it received. Fix any empty field before going further.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What can each Flenski module do?

Flenski gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Flenski1

Add a Plan for a Profile

ActionIn the docs only

This action attaches a plan to a profile that already exists in Flenski, so the profile carries the plan you chose without anyone opening Flenski.

When to use it
right after a payment succeeds or a deal closes, placed behind the module that tells you which profile to upgrade.
Watch out
the documentation describes no fields for this module, so check with Run once which profile and which plan it expects.
Flenski2

Create a Profile

ActionIn the docs only

You get a new profile in Flenski built from data another app already holds, with no copy and paste between tools and fewer typos in names or emails.

When to use it
as the first Flenski step after a signup form, a new order or a new row in a sheet.
Watch out
each run is meant to add a profile, so feeding the same person twice could leave you with two; check what Run once returns.
Flenski3

Make an API Call

ActionIn the docs only

This module opens the whole Flenski API to your scenario: any endpoint can be called, and it reuses the connection you already created, so there is no second key to manage.

When to use it
when the task you have in mind is not one of the four named Flenski modules.
Watch out
you write the request yourself, so keep the Flenski API documentation open next to the editor while you set it up.
Flenski4

New Profile Events

ActionIn the docs only

Going by its name, this module deals with the events of a Flenski profile, since the documentation adds no description. Careful: it is an action, so it never starts a scenario by itself.

When to use it
when a later step needs the events of a profile, placed after the module that identifies that profile.
Watch out
no official description exists for it, so read the bundles returned by Run once before you map anything from them.
Flenski5

Revoke a Plan for a Profile

ActionIn the docs only

With this action a plan comes off a Flenski profile as soon as your scenario reaches it, so the profile stops carrying a plan your records say has ended.

When to use it
when a subscription is cancelled or a refund goes through in another tool.
Watch out
a revoked plan cannot be assumed to come back on its own, so run the scenario once on a test profile before you switch it on for everyone.
Need help

Need help automating Flenski with Make?

A person reads every message.

FAQ

Flenski and Make: common questions

01Is the Flenski Make integration free?
Yes, on the Make side. Flenski is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Flenski itself needs its own account and subscription, described on the Flenski pricing page; this guide does not quote any price.
02What do you need to connect Flenski to Make?
You need a Flenski account and its API key. Open the profile settings page in Flenski and copy the key shown there. In Make, add any Flenski module to a scenario, click Create a connection, optionally fill the Connection name field, then paste the key or follow the on-screen instructions. The connection is created once and every Flenski module in your scenarios reuses it, so you never paste the key twice for the same account.
03Does Flenski trigger a Make scenario in real time?
No, because Flenski has no trigger module in Make: its 5 modules are all actions. The scenario has to start elsewhere. You can open it with the trigger of another app, such as a form or a store, and let Flenski act after it. Or you can run it on a schedule set on the first module, every 15 minutes by default, down to 1 minute on paid plans. Either way, Flenski modules do their work once the scenario reaches them.
04What if a Flenski module you need is missing in Make?
Use Make an API Call. It exists for Flenski and lets a scenario call any endpoint of the Flenski API with the connection you already set up, so what the four named modules do not cover remains reachable. You write the request yourself, so keep the Flenski API documentation at hand. Also note that the Flenski documentation on Make describes itself as AI-generated and may contain mistakes, so check important details with Flenski directly.
05Make or n8n for Flenski?
It depends on the tool you already use. On Make, Flenski comes with 5 modules, all actions, plus Make an API Call for the rest, and it runs from the Free plan. The same app often has an n8n node too, so check the n8n side before you decide. This page does not rank the two tools or compare their prices; the n8n vs Make comparison linked above goes through the criteria that set them apart.
Same platform

Other docs you might need on this stack.

Browse all integrations