Resources · Make integration

FLOWii Make integrationAutomate FLOWii with Make.

Can FLOWii exchange data with your other tools without a line of code? The FLOWii Make integration offers 116 action modules and no trigger. This page is for ops teams who run FLOWii: connect your account, build a first scenario and see what each module is for.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FLOWii Make integration automate?

The FLOWii Make integration links your FLOWii account to Make, where you build a scenario: the automation itself, a chain of modules. Each module is one brick of that chain. The 116 FLOWii modules are all actions that create, read, update, delete or list partners, orders, business cases, tasks and cash flows.

Three setups show where it pays off. A sales intake: a web form feeds Create partner, then Create business case, and the new client lands in FLOWii with a first case already open. A finance mirror: payments confirmed in another tool become entries through Create cash flow, and Get cash flow list sends them back out to a spreadsheet for checks. A file relay: Get business case attachments pulls the files of a case, and a storage app keeps a copy where the project team works.

What Make does not do here: FLOWii has no trigger in Make, so a change inside FLOWii never starts a scenario by itself. The start comes from a schedule or from another app's trigger. The FLOWii doc on Make also warns that it was generated by AI from FLOWii's documentation and may contain errors, so test each module with Run once before relying on it.

The same app often has an n8n node too. If you hesitate between the two tools, the n8n vs Make comparison lays out the criteria. To learn the editor step by step, Make training is the next stop, and Make pricing explains the plans.

Connect

How do you connect FLOWii to Make?

  1. 01

    Copy your FLOWii API key

    In FLOWii, open the settings, go to Extensions, select API and choose New FLOWii REST API. Your unique API key is shown there. Copy it, you will paste it into Make.

  2. 02

    Add a FLOWii module in Make

    In a scenario, add any FLOWii module and click Create a connection. A connection is your FLOWii account linked to Make once and reused by every FLOWii module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Enter your credentials

    Paste the credentials you copied from FLOWii, or follow the on-screen instructions, then save. From now on, Make can list what it reads in FLOWii while you fill a module's fields.

First scenario

Your first FLOWii scenario

GoalWhen a new client fills in your website form, Make creates the partner in FLOWii and a follow-up task for your team.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the app that collects your form answers: FLOWii has no trigger, so the start comes from another app.

  2. 02

    Add Create partner

    Click the + on the right of the first module, search FLOWii and pick Create partner. Click Create a connection if FLOWii is not linked yet, then map the form answers into the fields Make shows.

  3. 03

    Add Create task

    Add one more module with the + and choose Create task. Map what you need from the form and from the new partner, so whoever picks up the task knows which client it is about.

  4. 04

    Test with Run once

    Send a test answer through the form, then click Run once. Open each module to read the bundle it received. A bundle is one item passed from module to module, here one form answer.

  5. 05

    Schedule and switch it on

    Open the clock on the first module and set the schedule: every 15 minutes by default, never shorter than 15 minutes on the Free plan. Switch the scenario on. Each module run on a bundle counts as one operation.

Modules

What the FLOWii modules do

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

FLOWii1

Create attendance event

ActionIn the docs only

Logs a new attendance event in FLOWii from data the scenario already holds, so presence records stop depending on someone typing them in.

When to use it
a badge scan or a check-in form from another app reaches the scenario and the attendance record should follow without a manual step.
Watch out
every Run once writes a real event, so test with a colleague who knows the entry is a trial.
FLOWii2

Create business case

ActionIn the docs only

Opens a fresh business case in FLOWii straight from an incoming request, filled with details mapped from the module before it.

When to use it
a quote request arrives through a website form and sales should find it in FLOWii without copying anything.
Watch out
if the same request can reach the scenario twice, you get two cases; run Get business case list first to spot one that already exists.
FLOWii3

Create cash flow

ActionIn the docs only

Adds a cash flow entry in FLOWii from a payment or an expense recorded elsewhere, which keeps the money view in FLOWii in line with your other tools.

When to use it
your payment tool confirms a transfer and treasury wants to see it in FLOWii.
Watch out
when you are unsure how FLOWii names the account involved, read it first with Get bank account list and map the value it returns.
FLOWii4

Create communication

ActionIn the docs only

Records a communication in FLOWii, so a message sent or received in another tool also lives in the FLOWii history of the client.

When to use it
an important customer email lands in your inbox app and the account manager wants it traced in FLOWii.
Watch out
types and categories come from lists your company set up; Get communication type list shows the exact options before you map one.
FLOWii5

Create order

ActionIn the docs only

Turns data coming from another app into a new order in FLOWii, so nobody retypes an order that was already confirmed elsewhere.

When to use it
your online shop confirms a purchase and the team that prepares it works from FLOWii.
Watch out
if the order should point to a customer FLOWii does not know yet, place Create partner earlier in the scenario and map its result here.
FLOWii6

Create partner

ActionIn the docs only

Creates a partner record in FLOWii from a contact collected elsewhere, which spares the team a second round of data entry.

When to use it
a new client signs through your e-signature or form tool and should exist in FLOWii right after.
Watch out
when the same company can come in twice, check Get partner list before this module, or FLOWii ends up with two records for one client.
FLOWii7

Create planned absence

ActionIn the docs only

Books a planned absence in FLOWii from a request approved somewhere else, so the schedule kept in FLOWii matches the decision.

When to use it
a leave request gets approved in your HR form or chat tool and nobody should have to enter it again.
Watch out
the absence created during a Run once test is a real record, so run the test on a user who expects it.
FLOWii8

Create task

ActionIn the docs only

Adds a task in FLOWii each time the scenario receives work to hand out, so to-dos stop living in chat threads and inboxes.

When to use it
a ticket gets escalated in your helpdesk and someone has to follow up inside FLOWii.
Watch out
task categories come from Get task category list; read its result with Run once to see the exact labels before you map one.
FLOWii9

Create task activity interval

ActionIn the docs only

Adds a time interval to a task activity in FLOWii, handy when hours are tracked in another tool and should land on the right task.

When to use it
a timer stops in your time-tracking app and the work it measured belongs to a task that exists in FLOWii.
Watch out
attach the interval to the right activity; Get task activity list shows which activities exist before this module runs.
FLOWii10

Delete business case

ActionIn the docs only

Removes a business case from FLOWii, for scenarios that clean up test entries or cases opened by mistake.

When to use it
an earlier Get business case list step spotted a duplicate and one copy has to go.
Watch out
a deletion cannot be taken back from Make, so put a filter before this module and let only the case you meant go through.
FLOWii11

Delete cash flow

ActionIn the docs only

Erases a cash flow entry in FLOWii when the payment behind it was cancelled in another tool, so the figures stay honest.

When to use it
a transfer is refunded or cancelled and should not linger in FLOWii's cash view.
Watch out
once removed, the entry is gone; run Read cash flow first and write the result to a spreadsheet if you need a trace.
FLOWii12

Delete communication

ActionIn the docs only

Takes a communication out of FLOWii's history, useful when a message was logged twice or against the wrong record.

When to use it
your scenario logged an email with Create communication and a later check shows it went to the wrong partner.
Watch out
Run once executes the deletion for real, so test it on a communication you created for that purpose.
FLOWii13

Delete order

ActionIn the docs only

Deletes an order in FLOWii, the counterpart of a cancellation handled in your shop or your sales tool.

When to use it
a customer cancels before anything leaves the warehouse and the order should disappear from FLOWii too.
Watch out
if you want to keep the order's files, fetch them with Get order attachments and Get order documents before this step.
FLOWii14

Delete partner

ActionIn the docs only

Removes a partner from FLOWii, for the rare cleanup where a record should not exist at all.

When to use it
a test contact or a duplicate company slipped into FLOWii through an earlier scenario.
Watch out
a partner can carry orders and business cases; look at them with Get partner orders and Get partner business cases before you decide to delete.
FLOWii15

Delete task

ActionIn the docs only

Clears a task from FLOWii once another tool says the work is no longer needed, so assignees do not chase ghosts.

When to use it
a request is withdrawn in your helpdesk and the matching FLOWii task would only confuse the person holding it.
Watch out
map the task from the module that created or listed it; a guessed value can hit the wrong task, and deletions are final.
FLOWii16

Delete task activity interval

ActionIn the docs only

Removes one time interval from a task activity, the clean way to correct hours logged by mistake.

When to use it
Create task activity interval pushed the same interval twice and the total on the task looks too high.
Watch out
this module targets the interval, not the whole activity; pick the right one with Get task activity activity interval list first.
FLOWii17

Get activity type list

ActionIn the docs only

Brings back every activity type set up in FLOWii, one bundle per type, so you see the exact values your account holds.

When to use it
you are building a scenario that logs task activities and need to know which types your company uses.
Watch out
every module placed after it runs once per type, and each of those runs counts as an operation on your plan.
FLOWii18

Get attendance summary

ActionIn the docs only

Pulls an attendance summary out of FLOWii, a quick way to feed presence figures into a report or a team message.

When to use it
a manager wants the attendance picture posted to the team chat without logging into FLOWii.
Watch out
the doc does not describe what the summary contains, so read the bundle after a Run once before mapping anything.
FLOWii19

Get bank account list

ActionIn the docs only

Lists the bank accounts stored in FLOWii, one bundle each, so finance scenarios can point to the right account.

When to use it
just before Create cash flow, when you need to know which account a payment belongs to.
Watch out
in the middle of a scenario, it multiplies what follows by the number of accounts; add a filter that keeps only the one you need.
FLOWii20

Get business case attachments

ActionIn the docs only

Fetches the files attached to one business case in FLOWii, ready to be copied into cloud storage or sent on.

When to use it
a case reaches a decision and its supporting files should go to the shared drive of the project.
Watch out
the Free plan caps data transfer at 512 MB, and a scenario that moves many attachments uses it up quickly.
FLOWii21

Get business case emails

ActionIn the docs only

Returns the emails linked to a business case, so a scenario can read the whole exchange without anyone opening FLOWii.

When to use it
before a client meeting, a salesperson wants the messages on a case gathered into one document.
Watch out
several emails mean several bundles; an aggregator module groups them into one before you write the document.
FLOWii22

Get business case events

ActionIn the docs only

Retrieves the events recorded on a business case, which lets you rebuild its history somewhere else.

When to use it
a manager asks for the timeline of a case in a spreadsheet, one row per event.
Watch out
it works on one case at a time; take that case from Get business case list or Read business case earlier in the flow.
FLOWii23

Get business case failure list

ActionIn the docs only

Lists the business case failure values configured in your FLOWii account, one bundle per value.

When to use it
a scenario records why a case failed and the value has to match one FLOWii already holds, not free text.
Watch out
you only need this list while building; calling it on every run spends operations for nothing new.
FLOWii24

Get business case list

ActionIn the docs only

Returns business cases from FLOWii as separate bundles, the usual starting point for reports, checks and bulk updates.

When to use it
a scheduled scenario reviews the cases and posts the ones that need attention to the sales channel.
Watch out
each case travels through the rest of the scenario on its own, so a long result eats operations; filter as early as you can.
FLOWii25

Get business case source list

ActionIn the docs only

Shows the source values FLOWii offers for business cases, so each new case can say where it came from.

When to use it
several web forms create cases and each one should carry its own source.
Watch out
copy the value FLOWii returns instead of retyping it; a spelling that differs by one letter may not match.
FLOWii26

Get business case state list

ActionIn the docs only

Gives the states a business case can take in your FLOWii account, as one bundle per state.

When to use it
your report groups cases by state and the labels must match what the team sees in FLOWii.
Watch out
the doc lists no states, only your account holds them, so read the result with Run once before mapping.
FLOWii27

Get business case tasks

ActionIn the docs only

Collects the tasks attached to a given business case, so you know what is still on the table for it.

When to use it
a case is about to be closed and a scenario should first check whether tasks remain.
Watch out
plan for a case without tasks; test that situation with Run once to see how the rest of the scenario behaves.
FLOWii28

Get cash flow list

ActionIn the docs only

Pulls cash flow entries out of FLOWii, one bundle each, for reports, reconciliations or exports.

When to use it
finance wants the cash movements recorded in FLOWii copied into a spreadsheet to compare with the bank statement.
Watch out
map each bundle into the add-a-row module of your spreadsheet app, and keep an eye on the operation count when the list is long.
FLOWii29

Get communication attachments

ActionIn the docs only

Downloads the files attached to a FLOWii communication so another app can store or forward them.

When to use it
a signed document came in as an attachment and should end up in the client folder of your cloud drive.
Watch out
on the Free plan, Make handles files up to 5 MB; heavier attachments call for a paid plan.
FLOWii30

Get communication category list

ActionIn the docs only

Lists the communication categories defined in FLOWii, so logged messages land in the category your team expects.

When to use it
right before you set up Create communication, to pick a category that already exists.
Watch out
run it once in a separate test scenario and note the values; keeping it in the live scenario only spends operations.
FLOWii31

Get communication list

ActionIn the docs only

Returns the communications stored in FLOWii as a series of bundles, one per logged message or exchange.

When to use it
a support lead wants every communication about a partner pushed into a shared document.
Watch out
the result can be long; after a first Run once, add a filter on what you saw so only the useful ones continue.
FLOWii32

Get communication type list

ActionIn the docs only

Lists the communication types your FLOWii account knows, useful to label each logged message the same way every time.

When to use it
a form, an inbox and a chat tool all feed Create communication and each needs its own type.
Watch out
note the type values once while building rather than calling this module on every run of the scenario.
FLOWii33

Get company access list

ActionIn the docs only

Lists the company access entries tied to your FLOWii connection, a way to see which companies the scenario works with.

When to use it
before you build anything, to confirm the connection points at the company you expect.
Watch out
run it with Run once right after creating the connection; it doubles as a quick check that the credentials work.
FLOWii34

Get company data list

ActionIn the docs only

Returns the company data records held in FLOWii, the details a document or an email template may need.

When to use it
a scenario that writes emails or documents should pull your company's own details from FLOWii instead of hard-coding them.
Watch out
the doc describes none of the content, so map only what you actually see in the bundle after Run once.
FLOWii35

Get country list

ActionIn the docs only

Lists the countries FLOWii accepts, one bundle each, to match the value a partner or an order needs.

When to use it
a form collects the country as free text and you must turn it into a value FLOWii holds.
Watch out
free text rarely matches on the first try; a filter on the country name keeps the right bundle and drops the rest.
FLOWii36

Get delivery type list

ActionIn the docs only

Brings back the delivery types configured in FLOWii, for orders that must say how goods travel.

When to use it
your shop passes a shipping option to Create order and it has to match a FLOWii delivery type.
Watch out
when the shop gets a new shipping option, FLOWii needs the matching type too, or the scenario has nothing to map it to.
FLOWii37

Get document category list

ActionIn the docs only

Lists the document categories in FLOWii, the labels you need to file a document in the right place.

When to use it
documents coming from another tool should be sorted in FLOWii the way the team already sorts them.
Watch out
categories and subcategories are two separate lists; Get document subcategory list gives the second level.
FLOWii38

Get document numbering sequence list

ActionIn the docs only

Returns the document numbering sequences set up in FLOWii, useful to review which series exist before an automation creates paperwork.

When to use it
your accountant wants to know which series is available before orders start arriving from a scenario.
Watch out
this module only reads the sequences; Make lists no FLOWii module that changes them, so edits stay in FLOWii.
FLOWii39

Get document subcategory list

ActionIn the docs only

Gives the second level of document classification in FLOWii, the subcategories that refine a category.

When to use it
a scanned supplier invoice needs both a category and a subcategory to be filed where the team looks for it.
Watch out
read the categories first with Get document category list and keep the pair consistent when you map them.
FLOWii40

Get file with content

ActionIn the docs only

Fetches a file from FLOWii together with its content, so the next module can store it, send it or read it.

When to use it
a document kept in FLOWii has to reach a client by email or land in a cloud folder.
Watch out
the Free plan handles files up to 5 MB and runs a scenario for 5 minutes at most; large files call for a paid plan.
FLOWii41

Get good category list

ActionIn the docs only

Pulls the categories your FLOWii catalog of goods is sorted into, so a scenario can work with the same labels your team uses in FLOWii.

When to use it
you are filtering products by category and want the exact category values instead of typing them by hand.
Watch out
the Make doc gives no description for this module, so click Run once and read the bundle before mapping anything from it.
FLOWii42

Get good list

ActionIn the docs only

Brings the goods recorded in FLOWii into your scenario, one bundle per item, ready to feed a price sheet, a stock report or another app.

When to use it
you want your product catalog outside FLOWii, for example to rebuild a price list in a spreadsheet after a change.
Watch out
each item that reaches the next module counts as an operation there, so a large catalog quickly adds up on your plan.
FLOWii43

Get good subcategory list

ActionIn the docs only

Gives you the finer level of your product classification, the subcategories that sit under each good category in FLOWii.

When to use it
your reporting splits goods deeper than the main category, and you need the subcategory values to match or group items correctly.
Watch out
pair it with Get good category list when you need both levels; the name alone does not say how the two are linked, so check the bundle.
FLOWii44

Get home summary

ActionIn the docs only

Going by its name, it hands your scenario the overview of your FLOWii home page, which is handy when you want those headline figures somewhere else.

When to use it
you are posting a status digest to a chat channel or a dashboard and want it to start from what FLOWii already sums up.
Watch out
Make documents no fields here; run the module once and look at what the summary really contains before you promise it to anyone.
FLOWii45

Get my company user

ActionIn the docs only

Returns the FLOWii user behind the API Key your connection uses, which tells you whose rights the scenario runs with.

When to use it
a scenario behaves oddly and you want to confirm which account the connection belongs to before digging deeper.
Watch out
the connection (your FLOWii account linked to Make once) is shared by every FLOWii module, so this answer holds for the whole scenario.
FLOWii46

Get my notifications

ActionIn the docs only

Collects the notifications waiting for your FLOWii user so a scenario can route them to the place where you actually read things.

When to use it
your team lives in email or chat rather than in FLOWii, and you want those alerts to follow them there.
Watch out
FLOWii has no trigger in Make, so this module only runs when the scenario runs; Make checks on its schedule, 15 minutes by default, not the moment an alert appears.
FLOWii47

Get notifications summary

ActionIn the docs only

As its name says, it gives a condensed view of your FLOWii notifications rather than each one, which suits a short digest message.

When to use it
you only need a quick count or overview to decide whether someone should open FLOWii, not the full detail of every alert.
Watch out
the doc does not describe the summary, so compare it with Get my notifications during a test before choosing one.
FLOWii48

Get order attachments

ActionIn the docs only

Lists the files attached to a FLOWii order, so a scenario can back them up, forward them or check that paperwork is there.

When to use it
an order moves forward and you want its attached files copied to a shared drive where the rest of the team can reach them.
Watch out
you need to know which order to ask for; map its identifier from an earlier module such as Get order list.
FLOWii49

Get order documents

ActionIn the docs only

Retrieves the documents FLOWii links to an order, a separate module from Get order attachments.

When to use it
you want the business documents tied to an order, for instance to archive them with the customer file in another tool.
Watch out
FLOWii keeps attachments and documents apart in Make, so test both modules on one order to see which holds what you need.
FLOWii50

Get order emails

ActionIn the docs only

Pulls the email history FLOWii keeps for an order, giving you the conversation around a sale inside your scenario.

When to use it
a dispute or a question comes up and you want the order's messages collected in one place for whoever handles it.
Watch out
emails can carry personal data; think about where you send them before mapping their content to another app.
FLOWii51

Get order events

ActionIn the docs only

Returns the events recorded on a FLOWii order, a way to see what happened to it and bring that timeline elsewhere.

When to use it
you are building an order history for a report or a customer update and want the steps FLOWii logged.
Watch out
make's doc for FLOWii gives no event format, so read one real bundle with Run once before building filters on it.
FLOWii52

Get order list

ActionIn the docs only

Fetches your FLOWii orders into the scenario, the usual starting point when you want to act on several orders at once.

When to use it
a scenario starts on Make's schedule and needs the current orders before it copies, checks or reports on them.
Watch out
each order that flows on becomes a bundle (one item passed from module to module), and every later module spends an operation per bundle.
FLOWii53

Get order state list

ActionIn the docs only

Gives you the states an order can take in your FLOWii setup, the values you need to test where an order stands.

When to use it
you add a filter such as "only orders in a given state" and want to pick the state from the real list, not guess it.
Watch out
states differ from one FLOWii company to another, so read them from your own account rather than copying them from someone else's scenario.
FLOWii54

Get order subtype list

ActionIn the docs only

Returns the order subtypes configured in FLOWii, the second level under the order types.

When to use it
your reports or routing rules separate orders more finely than by type, and the scenario has to use the same subtype values.
Watch out
use it together with Get order type list; on its own, a subtype value may be hard to read without its parent type.
FLOWii55

Get order tasks

ActionIn the docs only

Lists the tasks FLOWii has attached to a given order, so you can see what remains to do on a sale.

When to use it
before closing or invoicing an order, you want to check whether open work is still hanging on it.
Watch out
you must point it at one order; if you start from a list of orders, each order becomes its own bundle and its own call.
FLOWii56

Get order type list

ActionIn the docs only

Hands you the order types defined in your FLOWii account, the main split between kinds of orders.

When to use it
a scenario treats orders differently depending on their kind and needs the exact type values to branch on.
Watch out
values set up by an admin can change; if a filter suddenly lets nothing through, check this list again.
FLOWii57

Get partner attachments

ActionIn the docs only

Collects the files stored on a FLOWii partner record, such as a contract or a signed form.

When to use it
you onboard a partner in another tool and want the files already gathered in FLOWii to follow the record there.
Watch out
files count toward the Free plan limits (5 MB per file, 512 MB of transfer), so a heavy partner folder can hit them.
FLOWii58

Get partner business cases

ActionIn the docs only

Shows the business cases FLOWii ties to one partner, the sales opportunities you have open or past with that company.

When to use it
an account manager wants a quick view of every deal with a customer before a call, in a doc or a chat message.
Watch out
map the partner from an earlier module; for the full details of one case, follow with Read business case.
FLOWii59

Get partner contacts

ActionIn the docs only

Retrieves the people recorded under a FLOWii partner, so their names and contact details can reach your mailing or CRM tool.

When to use it
you keep FLOWii as the reference for customer data and want the contacts of a partner copied to another app.
Watch out
test on a partner with several contacts to see how Make returns them before you connect a module that creates records.
FLOWii60

Get partner documents

ActionIn the docs only

Brings back the documents FLOWii links to a partner, distinct from the files dropped on the record as attachments.

When to use it
you need the paperwork produced for a customer, for example to file it in a folder named after that partner.
Watch out
if you expected a file and got nothing, try Get partner attachments; the two modules read different places.
FLOWii61

Get partner emails

ActionIn the docs only

Pulls the emails FLOWii holds for a partner, the whole exchange with a customer or supplier in one call.

When to use it
someone takes over an account and needs the message history handed over outside FLOWii.
Watch out
only send those messages to tools and people allowed to see them; Make copies whatever you map.
FLOWii62

Get partner events

ActionIn the docs only

Returns the events recorded on a FLOWii partner, a timeline you can reuse in a report or a handover note.

When to use it
you want to show what happened with a customer lately without asking people to open FLOWii.
Watch out
make's doc for FLOWii does not describe what an event holds, so check a real bundle before you promise a format to the reader.
FLOWii63

Get partner list

ActionIn the docs only

Fetches the partners stored in FLOWii, customers or suppliers depending on how you use FLOWii, as a starting set for a scenario.

When to use it
you want to sync your partner base to another app or check each partner against a rule in a single run.
Watch out
a long list means many bundles, and each later module costs one operation per partner; add a filter early to keep only those you need.
FLOWii64

Get partner orders

ActionIn the docs only

Lists the orders placed by one FLOWii partner, so you can see a customer's buying history in one step.

When to use it
before a renewal or a follow-up call, you want that customer's orders pasted into a note or a sheet.
Watch out
it works on one partner at a time; to cover several, start from Get partner list and let Make handle each bundle.
FLOWii65

Get partner subtype list

ActionIn the docs only

Gives the partner subtypes set up in FLOWii, the finer classification under each partner type.

When to use it
your segmentation uses subtypes and the scenario must send partners to the right list or owner based on them.
Watch out
Read it alongside Get partner type list so a subtype value never gets used without knowing its parent.
FLOWii66

Get partner tag list

ActionIn the docs only

Returns the tags available for partners in FLOWii, the free labels your team puts on customers and suppliers.

When to use it
you mirror FLOWii tags in a marketing tool and want the exact spelling of each tag instead of retyping it.
Watch out
tags are often added on the fly; a scenario built on a tag that was later renamed will quietly stop matching.
FLOWii67

Get partner tasks

ActionIn the docs only

Lists the tasks FLOWii attaches to a partner, the to-dos your team logged for that customer or supplier.

When to use it
you prepare a review of a key account before a meeting and want its open tasks in the same message.
Watch out
point it at one partner; the result says nothing about tasks on that partner's orders, which Get order tasks covers.
FLOWii68

Get partner type list

ActionIn the docs only

Hands you the partner types set up in your FLOWii account, the main way your partners are classified.

When to use it
a scenario treats one kind of partner differently from another and needs the type values to branch on.
Watch out
the labels come from your own setup; read them from your account instead of assuming names you saw elsewhere.
FLOWii69

Get payment method list

ActionIn the docs only

Retrieves the payment methods defined in FLOWii, so cash flow records built by a scenario use values FLOWii accepts.

When to use it
you create or post cash flow entries from another tool and need to map a payment method that exists in FLOWii.
Watch out
a value typed by hand that does not match this list is a common source of errors; map it from the list instead.
FLOWii70

Get task activity activity interval list

ActionIn the docs only

Returns the time intervals logged on a task activity in FLOWii, which, as the label suggests, break down the time spent.

When to use it
you bill or report time and want the detailed slices rather than a single total for an activity.
Watch out
the name repeats "activity" on purpose, it matches Make's label; you need the activity to query first, often from Get task activity list.
FLOWii71

Get task activity list

ActionIn the docs only

Lists the activities recorded under FLOWii tasks, the work actually done rather than the task itself.

When to use it
you want a view of who did what on a task, for a timesheet export or a project update.
Watch out
test it on a task you know well so you can tell from the bundle which activity is which.
FLOWii72

Get task attachments

ActionIn the docs only

Brings back the files attached to a FLOWii task, whatever your team dropped on it.

When to use it
when a task is done, you want its files copied to the project folder where the client can see them.
Watch out
big files count against the Free plan transfer (512 MB); keep an eye on it if tasks carry many attachments.
FLOWii73

Get task category list

ActionIn the docs only

Gives the task categories used in your FLOWii account, the top level for sorting work.

When to use it
you route tasks to a team or a board in another tool depending on their category.
Watch out
categories are account-specific; read them from your FLOWii rather than hard-coding a label in a filter.
FLOWii74

Get task list

ActionIn the docs only

Fetches the tasks stored in FLOWii into your scenario, the base for reminders, syncs or workload reports.

When to use it
you want tasks from FLOWii to show up in the tool your team checks first, a chat channel or a board.
Watch out
without a filter, every task becomes a bundle and every later module an operation, so narrow the list as early as you can.
FLOWii75

Get task subcategory list

ActionIn the docs only

Returns the subcategories that sit under FLOWii task categories, the finer level of your work classification.

When to use it
your reports split tasks deeper than their category and must reuse the same subcategory values.
Watch out
Read it after Get task category list so each subcategory stays attached to the right parent.
FLOWii76

Get unit of measure list

ActionIn the docs only

Lists the units of measure set up in FLOWii, the units your goods and orders are counted in.

When to use it
you prepare order lines in another tool and need units FLOWii will recognize on the way back.
Watch out
a unit spelled differently from this list will not match; map it rather than typing it.
FLOWii77

Get user list

ActionIn the docs only

Retrieves the users of your FLOWii company, handy to assign work or check who exists before a scenario writes data.

When to use it
you map an owner onto a task or a case and need the user as FLOWii knows it, not just a name.
Watch out
the list shows who has an account, not what they may do; for rights, use Get user permissions.
FLOWii78

Get user permissions

ActionIn the docs only

Shows what a FLOWii user is allowed to do, useful when a scenario fails because the connected account lacks a right.

When to use it
a module returns an error on an action that works for a colleague and you suspect a permission gap.
Watch out
everything a scenario does happens with the rights of the account behind the connection; checking them here saves guessing.
FLOWii79

Make an API Call

ActionIn the docs only

Lets you call any FLOWii API endpoint yourself, with the same connection, when none of the 116 listed modules does what you need.

When to use it
you need an operation of the FLOWii REST API that has no ready-made module in Make.
Watch out
you write the request yourself, so keep the FLOWii API documentation open; Make supplies the connection, the request is yours to shape.
FLOWii80

Post cash flow transaction

ActionIn the docs only

Records a transaction on a FLOWii cash flow, the step that turns a payment seen elsewhere into an entry in FLOWii.

When to use it
a payment lands in another app and you want the matching movement written in FLOWii without retyping it.
Watch out
it writes data; test it with Run once on a test entry first, and map the payment method from Get payment method list.
FLOWii81

Read activity type

ActionIn the docs only

Gives your scenario the details of one FLOWii activity type, so a later module can show a readable label instead of a bare reference.

When to use it
a task activity arrives from an earlier module and you need its type spelled out before sending a summary to your team.
Watch out
make's doc lists no fields for this module; open it after creating the connection to see what FLOWii actually returns.
FLOWii82

Read bank account

ActionIn the docs only

Pulls one bank account record out of FLOWii and hands it to the rest of the scenario as a single bundle (one item passed between modules).

When to use it
a cash flow entry points to an account and the next step, a finance report or a message, needs that account's details next to the amount.
Watch out
banking data is sensitive: check who can see the app you send it to before mapping anything.
FLOWii83

Read business case

ActionIn the docs only

Brings back one FLOWii business case, the commercial opportunity your sales team follows, ready to be mapped into later modules.

When to use it
a form or a CRM in another app gives you a case reference and you want the full case before deciding what to do next.
Watch out
as an action, it works on one case per run; for several cases, start from Get business case list and let each item flow through.
FLOWii84

Read business case failure

ActionIn the docs only

Shows you one of the failure entries FLOWii keeps for business cases, so a lost deal can carry its label into a report or a notification.

When to use it
your sales review needs the reason attached to a closed case written in plain words rather than as a reference.
Watch out
make's doc does not say how failures link to cases; test with Run once and read the bundle before building on it.
FLOWii85

Read business case source

ActionIn the docs only

Fetches one business case source from FLOWii, which helps you know where your opportunities come from when you pass them to another tool.

When to use it
you copy new cases into a spreadsheet and the source column should hold a readable name, not an internal value.
Watch out
make's doc gives no list of sources; read what your own FLOWii account holds before mapping.
FLOWii86

Read business case state

ActionIn the docs only

Returns one business case state from FLOWii, giving your scenario the words behind a stage so messages and reports stay easy to read.

When to use it
you alert a manager when a case moves and the alert should name the stage rather than show a code.
Watch out
mind the difference with Get business case state list: this module reads one state, the list module returns all of them.
FLOWii87

Read cash flow

ActionIn the docs only

Loads one cash flow entry from FLOWii into the scenario, so its details can travel to accounting, a sheet or a chat message.

When to use it
an earlier step hands you the entry you care about and you need the whole record, not only its reference.
Watch out
pair it with Update cash flow only after checking the bundle with Run once: Make's doc documents no field.
FLOWii88

Read communication

ActionIn the docs only

Opens one FLOWii communication record inside your scenario, so the exchange it holds can be summarised, archived or forwarded elsewhere.

When to use it
a partner or a case refers to a communication and you want its content in a helpdesk or a shared inbox.
Watch out
one communication per operation (one run of one module on one bundle); many records mean many operations counted on your Make plan.
FLOWii89

Read communication category

ActionIn the docs only

Hands back one communication category from FLOWii, useful to sort messages by their label once they leave the app.

When to use it
you route communications to different channels and each branch of the scenario depends on the category name.
Watch out
a filter built on a label breaks if someone renames the category in FLOWii; keep that in mind when you set conditions.
FLOWii90

Read communication type

ActionIn the docs only

Gets one communication type from FLOWii, so your scenario knows what kind of exchange it is handling before choosing a path.

When to use it
a router in Make should treat some kinds of communication differently and needs the type in readable form.
Watch out
category and type are two separate modules; Make's doc does not explain how FLOWii tells them apart, so check both in your account.
FLOWii91

Read company data

ActionIn the docs only

Returns one company data record from FLOWii, handy when a document or an email built in Make must show your company's own details.

When to use it
you generate an outgoing message in another tool and want its signature block filled from FLOWii rather than typed by hand.
Watch out
make's doc does not say what this record contains; run it once and read the bundle before mapping anything.
FLOWii92

Read delivery type

ActionIn the docs only

Brings one delivery type from FLOWii into the scenario, so shipping-related steps can use a clear name instead of an internal code.

When to use it
an order moves on to a logistics tool and the carrier or warehouse needs to know how the goods leave.
Watch out
only one type per run; to show every option in a form, reach for Get delivery type list instead.
FLOWii93

Read document category

ActionIn the docs only

Looks up one document category in FLOWii and passes it on, so files you move elsewhere keep a meaningful folder or tag.

When to use it
you copy order documents into cloud storage and want the category to decide where each file lands.
Watch out
folder names built from categories are fragile if categories change; test with Run once after any change in FLOWii.
FLOWii94

Read good

ActionIn the docs only

Gets you the full record of one good, a product or item in the FLOWii catalogue, ready to be reused by the next module.

When to use it
a quote or an online shop in another app mentions an item and you want FLOWii's version of it before continuing.
Watch out
make's doc lists no product fields; do not assume a price or a stock value is there until a test run shows it.
FLOWii95

Read good category

ActionIn the docs only

Returns one good category from FLOWii, so products carried to other tools stay grouped the way your team already knows.

When to use it
you publish items to a shop or a catalogue sheet and each one should sit under the right category name.
Watch out
categories and subcategories come from different modules; Get good subcategory list covers the finer level.
FLOWii96

Read order

ActionIn the docs only

Pulls one FLOWii order with its record into the scenario, so billing, shipping or a customer message can start from accurate data.

When to use it
a payment or a shipment in another app tells you which order changed and you need the order itself to act.
Watch out
it reads, it never changes anything; attachments and documents of the order come from Get order attachments and Get order documents.
FLOWii97

Read order state

ActionIn the docs only

Tells your scenario the name of one order state in FLOWii, which keeps customer updates and internal alerts easy to understand.

When to use it
a customer message should say in plain words where an order stands instead of quoting an internal code.
Watch out
this module does not change the state of any order; it only reads the state itself, and Make lists no FLOWii module that sets it.
FLOWii98

Read order type

ActionIn the docs only

Retrieves one order type from FLOWii so the scenario can tell kinds of orders apart and send each to the right follow-up.

When to use it
some orders need a different path, a separate team or a separate sheet, and the type is what decides.
Watch out
your account defines its own types; list them first with Get order type list.
FLOWii99

Read partner

ActionIn the docs only

Returns one FLOWii partner, the customer or supplier on the other side of your cases and orders, as a bundle you can map anywhere.

When to use it
you sync contacts with a CRM or a mailing tool and need the partner's current record before writing it elsewhere.
Watch out
to edit the partner afterwards, chain Update partner; reading first lets you compare before you overwrite.
FLOWii100

Read partner type

ActionIn the docs only

Fetches one partner type in FLOWii, so the scenario can treat customers, suppliers or any other kind you use each in its own way.

When to use it
your CRM keeps separate lists and each FLOWii partner must land in the list that matches its type.
Watch out
the kinds of partner are whatever your account defines; Make's doc names none, so read them before building filters.
FLOWii101

Read payment method

ActionIn the docs only

Brings one payment method from FLOWii into your scenario, so invoices, reminders or reports can state how a customer pays.

When to use it
a billing tool downstream needs the method written out when you pass it an order or a cash flow entry.
Watch out
one method per run; for a dropdown or a full reference table, Get payment method list is the better fit.
FLOWii102

Read task

ActionIn the docs only

Loads one FLOWii task with its record, so the next module can post it to a chat, a calendar or a project board.

When to use it
a teammate is assigned work in FLOWii and another tool should show the same task without anyone copying it.
Watch out
its activities and attachments live in other modules, Get task activity list and Get task attachments.
FLOWii103

Read task category

ActionIn the docs only

Returns one task category from FLOWii, giving your scenario a clear label to sort work across boards, channels or people.

When to use it
tasks leave FLOWii for a team tool and each category should open its own column or channel.
Watch out
subcategories need Get task subcategory list; this module stops at the category level.
FLOWii104

Read unit of measure

ActionIn the docs only

Hands your scenario one unit of measure from FLOWii, so quantities sent to a shop, a sheet or a supplier keep their meaning.

When to use it
a quantity leaves FLOWii with an order or a good and the receiving tool must know whether it counts pieces, hours or something else.
Watch out
make's doc names no unit; check the ones your account uses before mapping quantities.
FLOWii105

Read user

ActionIn the docs only

Gets one FLOWii user record, useful to turn an assignee or an author into a name and contact that other tools understand.

When to use it
a task or a case carries a user and your notification should reach that person in chat or by email.
Watch out
permissions are a separate module, Get user permissions; this one does not tell you what the user may do.
FLOWii106

Update cash flow

ActionIn the docs only

Changes an existing cash flow entry in FLOWii from your scenario, so figures corrected elsewhere reach FLOWii without retyping.

When to use it
a bank tool or a sheet holds the corrected amount or note and FLOWii should match it once the change is confirmed.
Watch out
writing to finance data is risky: read the entry first with Read cash flow and test on a dummy record with Run once.
FLOWii107

Update communication

ActionIn the docs only

Edits a communication that already exists in FLOWii, keeping its content in step with what happened in your inbox or helpdesk.

When to use it
a reply or a status arrives in another tool and the FLOWii communication should reflect it for the rest of the team.
Watch out
to add a file, use Upload communication attachment; Make's doc does not say this module handles files.
FLOWii108

Update notification

ActionIn the docs only

Changes one of your FLOWii notifications from Make, which lets a scenario tidy up alerts once they have been dealt with somewhere else.

When to use it
you handle a FLOWii alert in a chat tool and want its counterpart in FLOWii updated so nobody acts on it twice.
Watch out
make's doc does not list what can change on a notification; read it with Get my notifications and test before switching the scenario on.
FLOWii109

Update partner

ActionIn the docs only

Writes changes to an existing FLOWii partner, so a new address, contact or detail entered in another tool reaches FLOWii without manual copying.

When to use it
your CRM or a form collects fresher partner data and FLOWii should hold the same version.
Watch out
syncing both ways can make two scenarios feed each other endlessly; let only one tool be the source for each detail.
FLOWii110

Update task activity

ActionIn the docs only

Edits an activity logged on a FLOWii task, keeping the record of work done accurate when the correction comes from another app.

When to use it
time or notes recorded in a tracker elsewhere must replace what was first entered on the task in FLOWii.
Watch out
activity and activity interval are different records; intervals change through Update task activity interval.
FLOWii111

Update task activity interval

ActionIn the docs only

Adjusts one activity interval on a FLOWii task, which keeps the logged span of work right when they were corrected elsewhere.

When to use it
a time tracker or a calendar holds the corrected span of work and FLOWii should show the same.
Watch out
make's doc gives no date format for intervals; check the bundle from Read task or Get task activity activity interval list before mapping.
FLOWii112

Upload business case attachment

ActionIn the docs only

Attaches a file to a FLOWii business case from your scenario, so proposals or signed papers end up where the sales team looks.

When to use it
a signature tool or an email returns a document for a deal and it belongs on that case in FLOWii.
Watch out
on the Make Free plan, files are capped at 5 MB; larger documents need a paid plan.
FLOWii113

Upload communication attachment

ActionIn the docs only

Adds a file to an existing FLOWii communication, keeping the exchange and its documents together for whoever opens it later.

When to use it
an email arrives with an attachment and the matching FLOWii communication should carry the same file.
Watch out
make's doc says nothing about accepted file types; test with a real file using Run once.
FLOWii114

Upload order attachment

ActionIn the docs only

Puts a file on a FLOWii order from Make, so delivery notes, customer files or photos sit next to the order they concern.

When to use it
a shipping tool or a customer form produces a document tied to an order you already track in FLOWii.
Watch out
each file is one operation on your plan; a scenario that sends many files uses many operations.
FLOWii115

Upload partner attachment

ActionIn the docs only

Stores a file on a FLOWii partner, keeping contracts, certificates or other papers of a customer or supplier in one place.

When to use it
a supplier sends a document by email or through a portal and it should be filed on that partner in FLOWii.
Watch out
Make lists the partners it can read once the connection exists; pick the right one or map it from Read partner.
FLOWii116

Upload task attachment

ActionIn the docs only

Sends a file to a FLOWii task, so the person doing the work finds the brief, the photo or the form right on the task.

When to use it
a form submission or a shared folder produces the file someone needs to finish a task already open in FLOWii.
Watch out
the Free plan caps files at 5 MB and data transfer at 512 MB; heavy files need a paid Make plan.
Need help

Need help automating FLOWii with Make?

A person reads every message.

FAQ

FLOWii and Make: common questions

01Is the FLOWii Make integration free?
Yes. FLOWii is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes per execution, 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 execution. You still need your own FLOWii account, and this page gives no price for FLOWii itself.
02What do you need to connect FLOWii to Make?
An active FLOWii account and its API key. The key sits in FLOWii under settings, Extensions, API, then New FLOWii REST API. In Make, add a FLOWii module, click Create a connection, give it a name if you like and paste the credentials. If the connection asks for a bearer token, the doc says to request an access_token with your API key, your FLOWii email and your password. You create the connection once, and every FLOWii module reuses it.
03Does the FLOWii Make integration react in real time?
No. FLOWii has no trigger in Make, neither scheduled nor instant, so nothing that happens in FLOWii can start a scenario on its own. There are two ways to start anyway. Put another app's trigger at the head of the scenario, such as a form or a shop app. Or set a schedule on the first module, every 15 minutes by default, and open the scenario with Get business case list or Get task list to process what they return on each run.
04What if a FLOWii module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the FLOWii API from your scenario, with the same connection as every other FLOWii module, so you are not stuck when the listed modules fall short. Keep one caveat in mind: the FLOWii doc on Make says it was generated by AI from FLOWii's own documentation and may contain errors. Check the behavior with Run once, and ask FLOWii directly when their API does something you did not expect.
05Is Make or n8n the better fit for FLOWii?
It depends on what you need to automate. In Make, FLOWii comes with 116 action modules, including Make an API Call, but no trigger. The same app often has an n8n node, so compare what each tool offers for FLOWii with the actions your scenario needs, and check how the automation would start in each one. Neither tool wins in every case; your criteria decide, and the comparison linked higher on this page sets them out side by side.