Resources · Make integration

Flowlu Make integrationAutomate Flowlu with Make.

Can Flowlu fill its own sales pipeline from the tools you already use? The Flowlu Make integration offers 41 modules: 33 actions and 8 searches on accounts, opportunities, pipelines, calendars and tasks. This page shows sales and ops teams how to connect Flowlu and build a first scenario.

Try the Flowlu integration on MakeSee the 41 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flowlu Make integration do for you?

The Flowlu Make integration links your Flowlu account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick, here an action or a search on Flowlu data, so records get created, updated and looked up without anyone retyping them.

Leads that land in the pipeline. A form or a chat tool hands over a new contact; Search Accounts checks whether the client exists, Create an Account adds it if needed, and Create an Opportunity opens the deal in the right pipeline.

Tasks that follow the deal. When an opportunity moves forward, Update an Opportunity sets the new stage and Create a Task gives the next step to the right person. Each item passed between modules is a bundle, and each module run on a bundle is an operation, the unit Make counts on your plan.

A tidy sales structure. Pipelines, stages, sources and account types can be created, renamed or removed by a scenario, which helps when several teams share one Flowlu workspace.

What the app does not offer in Make: any trigger. Flowlu cannot start a scenario by itself, so the flow opens on another app or on a schedule. The same app often exists on n8n as well; the n8n vs Make comparison lays out the differences, the Make training covers the editor step by step, and Make pricing explains how operations are counted.

Connect

How do you connect Flowlu to Make?

  1. 01

    Generate an API key in Flowlu

    In Flowlu, open Portal Settings, then Main Settings and API Settings. Click Create, pick Agile Projects as the application, give the key a name and save. Copy the key shown on screen.

  2. 02

    Add a Flowlu module in Make

    In your scenario, click the +, search for Flowlu and pick any module, for example Create an Account. Then click Create a connection. A connection is your Flowlu account linked to Make once and reused by every Flowlu module.

  3. 03

    Paste the key and save

    Give the connection a clear name in Connection name if you like, it is optional. Paste the API key you copied from Flowlu and confirm. Make can now list your pipelines, stages and other Flowlu objects in the module fields.

First scenario

Your first scenario: from a new lead to a Flowlu deal

GoalWhen a new lead shows up in another app, Make creates the account and opens an opportunity in Flowlu.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your leads arrive, such as your form tool, since Flowlu has no trigger of its own.

  2. 02

    Add Create an Account

    Click the + on the right of the first module, search for Flowlu and choose Create an Account. Click Create a connection and paste your API key if you have not done it yet.

  3. 03

    Map the lead data

    Fill the account fields with the values from the first module, field by field. Make shows the data of the previous module in a panel, so you click instead of typing.

  4. 04

    Open the opportunity

    Add Create an Opportunity after the account. Choose the pipeline and stage from the lists Make shows, and map the account created one step earlier so the deal is attached to the right client.

  5. 05

    Test with Run once

    Click Run once and send a test lead. Open each module's bubble to read the bundles it received, then check in Flowlu that the account and the deal both appear.

  6. 06

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on, and new leads start reaching your Flowlu pipeline.

Modules

What can you do with the Flowlu modules?

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

Flowlu1

Create a Calendar

Action

In Make“Creates a new calendar.”

Gives a team or a project its own calendar in Flowlu, set up by the scenario instead of by hand in the settings.

When to use it
A new client project opens in your sales tool and the project team needs a shared calendar before the kickoff meeting.
Watch out
every run adds one more calendar. If the same event can reach the scenario twice, run Search Calendars first and create only when it comes back empty.
Flowlu2

Create an Account

Action

In Make“Creates a new account.”

Turns a person or a company coming from another app into an account record in Flowlu, ready for opportunities and tasks to hang on it.

When to use it
A web form, a signed quote or a new invoice customer appears elsewhere and you want the client in Flowlu without retyping.
Watch out
each run creates a new record. Place Search Accounts before this module so a client who is already in Flowlu is not created a second time.
Flowlu3

Create an Account Type

Action

In Make“Creates a new account type.”

Adds a new category for your accounts, the label that separates clients from partners, suppliers or any family you use.

When to use it
Your team starts selling through resellers and you want that category to exist before the first reseller account arrives in the scenario.
Watch out
types are structure, not daily data. Most scenarios create them once; keep this module in a small setup scenario rather than in a flow that runs over and over.
Flowlu4

Create an Opportunity

Action

In Make“Creates a new opportunity.”

Opens a deal in Flowlu with the scenario, so a lead captured anywhere lands in your sales pipeline instead of an inbox.

When to use it
A demo request, a chat conversation or a form entry means someone may buy, and sales should see it in Flowlu.
Watch out
an opportunity sits in a pipeline and a stage. Map both on purpose, so each deal starts in the step your sales team expects.
Flowlu5

Create an Opportunity Source

Action

In Make“Creates a new opportunity source.”

Registers a new origin for your deals, the channel you will later read in reports: a trade show, a partner, a new ad campaign.

When to use it
Marketing launches a channel and you want every deal it brings to be tagged with the right source from the very first one.
Watch out
create the source before the deals that use it. If both happen in the same scenario, place this module first and map its output into Create an Opportunity.
Flowlu6

Create an Opportunity Stage

Action

In Make“Creates a new opportunity stage.”

Inserts a new step into a sales pipeline, for example a legal review between the proposal and the signature.

When to use it
Your sales process changes and several pipelines need the same new step, so the scenario adds it everywhere in one pass.
Watch out
a stage belongs to a pipeline. Pick the pipeline in the module, or map it from Search Pipelines, before you name the new step.
Flowlu7

Create a Pipeline

Action

In Make“Creates a new pipeline.”

Builds a whole new sales pipeline in Flowlu, the track that deals move along from first contact to signature.

When to use it
A new product line or a new country gets its own sales process, and you prefer the scenario to set it up from a template sheet.
Watch out
an empty pipeline is not usable yet. Follow this module with Create an Opportunity Stage for each step, mapping the pipeline Make just returned.
Flowlu8

Create a Task

Action

In Make“Creates a new task.”

Puts a to-do in Flowlu for the right person, with the context coming from the app where the event happened.

When to use it
A deal moves forward, a support ticket needs a callback or a contract gets signed, and someone has to act on it.
Watch out
one bundle, one task. If the module before it returns a list, you get a task per item, so check the count with Run once before you switch the scenario on.
Flowlu9

Delete a Calendar

Action

In Make“Deletes an existing calendar.”

Removes a calendar from Flowlu for good, which keeps the list clean once a project or a team no longer exists.

When to use it
A project closes in your project tool and its calendar should disappear with it.
Watch out
a deletion cannot be undone from Make. Test with Run once on a throwaway calendar, and filter hard on the ID you pass.
Flowlu10

Delete an Account

Action

In Make“Deletes an existing account.”

Erases an account record from Flowlu, the cleanup step for test entries or for a client who asked to be forgotten.

When to use it
A removal request arrives through your forms and the matching Flowlu account has to go.
Watch out
this is the most sensitive module of the list. Find the account with Search Accounts, check with Run once that exactly one record comes back, then delete.
Flowlu11

Delete an Account Type

Action

In Make“Deletes an existing account type.”

Drops an account category you no longer use, so the choice list stays short for the whole team.

When to use it
You merged two client categories and the old one should vanish once its accounts are moved.
Watch out
move or update the accounts of that type first with Update an Account; deleting the category is the last step, not the first.
Flowlu12

Delete an Opportunity

Action

In Make“Deletes an existing opportunity.”

Wipes a deal out of Flowlu, useful for spam leads or deals that were created twice by mistake.

When to use it
A lead turns out to be junk in your qualification tool and should not inflate the Flowlu pipeline.
Watch out
a lost deal is still history for your reports. Prefer Update an Opportunity to close it, and keep deletion for records that should never have existed.
Flowlu13

Delete an Opportunity Source

Action

In Make“Deletes an existing opportunity source.”

Retires a lead origin from the list, once a channel has stopped and nobody should pick it anymore.

When to use it
A partnership ends and its source label keeps confusing the people who log deals by hand.
Watch out
older deals may still point to that source. Check them with Search Opportunities before you remove it.
Flowlu14

Delete an Opportunity Stage

Action

In Make“Deletes an existing opportunity stage.”

Takes a step out of a pipeline, the mirror move of adding one when your sales process gets simpler.

When to use it
Two stages of a pipeline mean the same thing in practice and the team agreed to keep only one.
Watch out
deals sitting in that stage need a new home first. Move them with Update an Opportunity, then delete the empty stage.
Flowlu15

Delete a Pipeline

Action

In Make“Deletes an existing pipeline.”

Gets rid of a full sales pipeline in Flowlu, the track your deals used to follow.

When to use it
A pilot offer is over and its pipeline only clutters the sales view.
Watch out
run it on a test pipeline before anything else, and be careful after Search Pipelines: every pipeline it returns would go through the deletion.
Flowlu16

Delete a Task

Action

In Make“Deletes an existing task.”

Clears a task that has lost its reason to exist, so the to-do list of your team reflects real work.

When to use it
A meeting is cancelled in the calendar app and the preparation task created for it should go too.
Watch out
the scenario needs the task ID. Map it from the bundle of Create a Task when both happen in one scenario, or find it with Search Tasks.
Flowlu17

Get a Calendar

Action

In Make“Retrieves an existing calendar.”

Reads the details of one calendar when you already know its ID, so later modules can use its name and settings.

When to use it
A previous step handed you a calendar ID and you need its full record to build a message or a report.
Watch out
Get needs an exact ID. If you only have a name, use Search Calendars instead, which works from criteria.
Flowlu18

Get an Account

Action

In Make“Retrieves an existing account.”

Fetches the full record of one Flowlu account, so an email, an invoice or a document can use its data.

When to use it
An opportunity or a task gives you an account ID and the next module needs the client's details.
Watch out
one call, one account. If you loop over many IDs, each Get is one more operation on your Make plan.
Flowlu19

Get an Account Type

Action

In Make“Retrieves an existing account type.”

Returns one account category and its details, handy to turn an ID into a readable label.

When to use it
A report or a notification should show the category name rather than the raw ID stored on the account.
Watch out
types rarely change. When the same few IDs come back again and again, a Search Account Types at the start of the scenario can be enough.
Flowlu20

Get an Opportunity

Action

In Make“Retrieves an existing opportunity.”

Loads a single deal with its current values, the snapshot you need before deciding what the scenario does next.

When to use it
Another app mentions a deal ID, for instance in a quote, and you want the deal's current state from Flowlu.
Watch out
it needs the deal ID. When the other app only knows the client or the deal name, start with Search Opportunities.
Flowlu21

Get an Opportunity Source

Action

In Make“Retrieves an existing opportunity source.”

Translates a source ID into its full record, so people read the channel name and not a number.

When to use it
A deal summary sent to your chat tool should show where the lead came from.
Watch out
this is a lookup step, not a sync. Use it where the source matters to the message, not on every module of the scenario.
Flowlu22

Get an Opportunity Stage

Action

In Make“Retrieves an existing opportunity stage.”

Reads one pipeline step, which lets the scenario know exactly where a deal stands.

When to use it
The next step of the scenario depends on where a deal stands, for instance a message only when it reaches the proposal stage.
Watch out
a stage can be renamed in Flowlu while its ID stays the same. Base your checks on the ID.
Flowlu23

Get a Pipeline

Action

In Make“Retrieves an existing pipeline.”

Pulls up one pipeline and its details, the reference point when a scenario handles several sales processes.

When to use it
Deals from two pipelines go through the same scenario and the next step depends on which one they belong to.
Watch out
you need the pipeline ID. List them once with Search Pipelines during the build, then keep the right ID in the module.
Flowlu24

Get a Task

Action

In Make“Retrieves an existing task.”

Checks one task as it is right now, useful before you update it or report on it.

When to use it
A reminder scenario needs to know if a task is still open before it pings the person in charge.
Watch out
reading a task costs an operation like any module. Fetch it only on the branch that actually needs the details.
Flowlu25

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Flowlu API to your scenario, reusing the same connection, for anything the listed modules do not cover.

When to use it
You need an object or an action missing from this list and you know which Flowlu endpoint handles it.
Watch out
you write the request yourself, path and body included. Test it with Run once and read the returned bundle before building on it.
Flowlu26

Update a Calendar

Action

In Make“Updates an existing calendar.”

Changes an existing calendar, for example its name when the project behind it is renamed.

When to use it
A project gets a new title in your project tool and the Flowlu calendar should follow.
Watch out
fill only the fields you mean to change, and read the bundle after Run once to confirm the result.
Flowlu27

Update an Account

Action

In Make“Updates an existing account.”

Keeps a Flowlu account in line with the app where the client data really lives, without a copy and paste.

When to use it
A client's details change in your billing tool and Flowlu should show the same thing.
Watch out
find the right record first with Search Accounts, and test with Run once what happens when the search returns nothing or several accounts.
Flowlu28

Update an Account Type

Action

In Make“Updates an existing account type.”

Renames or adjusts an account category so every account using it shows the new label at once.

When to use it
Your team renames the category for resellers and the change should apply across Flowlu.
Watch out
a type is shared by many accounts. One update changes the label everywhere, so check the result on a test account.
Flowlu29

Update an Opportunity

Action

In Make“Updates an existing opportunity.”

Moves a deal forward or corrects its values from another app, so the pipeline tells the truth.

When to use it
A quote is signed in your e-signature tool and the deal should jump to the right stage.
Watch out
the stage must exist in the deal's pipeline. Map its ID from Search Opportunity Stages rather than typing it.
Flowlu30

Update an Opportunity Source

Action

In Make“Updates an existing opportunity source.”

Edits the record of a lead origin, typically its name, while every deal keeps pointing to it.

When to use it
A campaign gets a clearer name and your reports should use it, past deals included.
Watch out
if what you want is a different channel, create a new source instead; renaming changes history for every deal already tagged.
Flowlu31

Update an Opportunity Stage

Action

In Make“Updates an existing opportunity stage.”

Adjusts a step of a pipeline, its name or its settings, without touching the deals inside it.

When to use it
Sales agree on better wording for a stage and you manage several pipelines that share it.
Watch out
other scenarios that look for the stage by its old name will stop finding it. Point them at the ID instead.
Flowlu32

Update a Pipeline

Action

In Make“Updates an existing pipeline.”

Modifies an existing sales pipeline, the tidy way to rename a track once the offer behind it evolves.

When to use it
An offer changes name in your catalog and its pipeline should match what the team says on calls.
Watch out
the module needs the pipeline ID. Pick it from the list Make shows once the connection is in place, or map it from Search Pipelines.
Flowlu33

Update a Task

Action

In Make“Updates an existing task.”

Rewrites a task as the situation changes, so Flowlu shows where the work really stands.

When to use it
The event behind the task changes in another app, a call moved or an order delayed, and Flowlu should follow.
Watch out
the module needs the task ID and changes the task as it stands. Read it with Get a Task first when its current status matters.
Flowlu34

Search Accounts

Search

In Make“Searches for accounts or lists them all.”

Looks through your Flowlu accounts from criteria, or lists them all, and returns each match as its own bundle.

When to use it
Before any create or update, to know if the client from the other app already exists in Flowlu.
Watch out
zero, one or several results can come back. Plan all three cases, because the next module runs once per match.
Flowlu35

Search Account Types

Search

In Make“Searches for account types or lists them all.”

Lists your account categories, or finds one by criteria, so the scenario can pick the right type instead of hard-coding it.

When to use it
You map a category coming from a form to the matching Flowlu type.
Watch out
each type found becomes a bundle. Narrow the criteria, otherwise the next module repeats for every category.
Flowlu36

Search Calendars

Search

In Make“Searches for calendars or lists them all.”

Finds calendars matching your criteria, or returns the full list, to get the ID other calendar modules need.

When to use it
You know the project name but not its calendar ID, and the next step is Update a Calendar or Delete a Calendar.
Watch out
when nothing matches, no bundle comes out and the rest of the scenario does not run. Test with a name that does not exist to see it.
Flowlu37

Search Opportunities

Search

In Make“Searches for opportunities or lists them all.”

Pulls the deals that match your criteria, one bundle per deal, the starting point of most reporting scenarios in Flowlu.

When to use it
A scheduled scenario gathers open deals for a summary, or checks whether a deal already exists before creating one.
Watch out
a long list means many operations downstream. Narrow the criteria, and add an aggregator if you want a single message instead of one per deal.
Flowlu38

Search Opportunity Sources

Search

In Make“Searches for opportunity sources or lists them all.”

Collects the lead origins, all of them or the ones that match, to map a channel name to its Flowlu ID.

When to use it
Your form sends the channel as text and Create an Opportunity needs the source ID.
Watch out
names typed by people vary in spelling and case. Clean the text before the search, or offer a fixed list in your form.
Flowlu39

Search Opportunity Stages

Search

In Make“Searches for opportunity stages or lists them all.”

Surfaces the steps of your pipelines, or finds a given one, which gives the scenario the stage ID without guessing.

When to use it
Update an Opportunity must move a deal to a stage chosen by name in another app.
Watch out
the same stage name can exist in several pipelines. Add the pipeline to your criteria so the right one comes back.
Flowlu40

Search Pipelines

Search

In Make“Searches for pipelines or lists them all.”

Brings back your Flowlu pipelines, all of them or those that fit your criteria, as separate bundles.

When to use it
A scenario handles several sales processes and has to find the right pipeline ID from a name coming from another tool.
Watch out
if you only need one pipeline, make your criteria precise; each pipeline returned runs the rest of the scenario once.
Flowlu41

Search Tasks

Search

In Make“Searches for tasks or lists them all.”

Brings back the Flowlu tasks that match your criteria, or every task when you leave the search open, each one as its own bundle.

When to use it
You don't know the task ID yet and need to find the task before you change it with Update a Task.
Watch out
the search can return zero, one or many bundles, and each following module runs once per task, so each one costs operations.
Need help

Need help automating Flowlu with Make?

A person reads every message.

FAQ

Questions about the Flowlu Make integration

01Is the Flowlu Make integration free?
Yes, Flowlu 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, one per operation. Your Flowlu subscription is a separate matter handled on the Flowlu side.
02What do you need to connect Flowlu to Make?
You need an active Flowlu account and an API key from it. The key is created in Portal Settings, under Main Settings and API Settings, by clicking Create, selecting Agile Projects as the application and saving. In Make, you add any Flowlu module, click Create a connection, optionally name it, and paste the key. The same connection then serves all 41 Flowlu modules, so you only go through these steps once per Flowlu account.
03Does the Flowlu module react in real time?
No, because Flowlu has no trigger in Make: none of its 41 modules can start a scenario. The flow begins with another app, such as your form tool, or with the schedule set on the first module, every 15 minutes by default. The shortest interval is 15 minutes on the Free plan and 1 minute on paid plans. A scheduled start with Search Opportunities or Search Tasks is a simple way to pick up Flowlu records at each run.
04What if a Flowlu module is missing in Make?
Use the Make an API Call module. It reaches any endpoint of the Flowlu API with the connection you already set up, so an object or an action absent from the 33 actions and 8 searches is still within reach. You write the request yourself, then test it with Run once and read the bundle Flowlu sends back. The official documentation of this app is marked as AI-generated from Flowlu's own documentation, so check important details with Flowlu before relying on them.
05Make or n8n for Flowlu?
It depends on the tool your team already runs. On Make, Flowlu comes with 41 ready modules covering accounts, opportunities, pipelines, stages, sources, calendars and tasks, plus Make an API Call for the rest, and it works on the Free plan. The same app often has an n8n node too, so check the coverage you need on each side before choosing. Pick the platform where your other automations already live, since one connection per tool is easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations