Resources · Make integration

SectorFlow.AI Make integrationAutomate SectorFlow.AI with Make.

Can Make send your requests to SectorFlow.AI on its own? Yes: the SectorFlow.AI Make integration gives you 14 modules, 10 actions and 4 searches, for chats, images and experts. This guide shows you how to link your account and build a first working scenario.

Try the SectorFlow.AI integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SectorFlow.AI Make integration do?

The SectorFlow.AI Make integration lets a Make scenario (the automation you build, a chain of modules) talk to your SectorFlow.AI workspace for you. It sends chats, creates images, reads your threads and experts, and you never write a line of code to get there.

Questions that ask themselves. A form, a ticket or a spreadsheet row lands in another app, and Send Chat forwards it to SectorFlow.AI so the conversation starts without anyone copying and pasting.

Visuals on demand. A marketer drops a product description somewhere, and one of the image modules, such as Create an Image using Dall-E 3 or Create an Image using Google Imagen 3 Fast, turns it into a picture.

A tidy archive. List Chats and Get Chat Thread pull your conversations back out, and Update a Chat Thread Title gives each one a name people can search later.

Know the limits before you start. The app has no trigger, so SectorFlow.AI cannot wake a scenario up by itself: something else has to start it. The official Make documentation for this app also warns that it was written by AI and may contain mistakes, so check anything critical against SectorFlow.AI directly. If you are still weighing the two tools, the n8n vs Make comparison lays out the criteria, Make pricing explains what each plan allows, and Make training helps if you want to go further.

Connect

How do you connect SectorFlow.AI to Make?

  1. 01

    Create an API key in SectorFlow.AI

    In SectorFlow.AI, click your initials in the top right corner, open My Account and scroll to API Keys. Click Create a token, give it a Service Token Name, pick an Expiration time, click Save and copy the key shown on screen.

  2. 02

    Add a SectorFlow.AI module in Make

    Open your scenario in Make, add any SectorFlow.AI module and click Create a connection. A connection is your SectorFlow.AI account linked to Make once, then reused by every SectorFlow.AI module you add afterwards.

  3. 03

    Paste the key and save

    Type a name in Connection name if you like (it is optional, but handy when you run several accounts), paste the API key you copied, and follow the instructions on screen to finish the connection.

First scenario

Build your first scenario with SectorFlow.AI

GoalWhen a new request shows up in another app, Make passes it to SectorFlow.AI with Send Chat.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Since SectorFlow.AI has no trigger, the first module comes from the app where your requests live, a form tool or a helpdesk for instance.

  2. 02

    Set up the starting module

    Search that app by name, pick the module that watches for new entries, and connect its account. Make then lists the forms, folders or boards it can read, so you only have to choose one.

  3. 03

    Add Send Chat

    Click the + on the right of the first module, search SectorFlow.AI and pick Send Chat. Connect your account, then map the text of the request from the first module into the message.

  4. 04

    Test with Run once

    Create one test entry in the source app, then click Run once. Each module shows the bundles it received (a bundle is one item passed along, here one request), so you can see exactly what reached SectorFlow.AI.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule: a new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Then flip the scenario on and let it run.

Modules

What each SectorFlow.AI module does

SectorFlow.AI gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SectorFlow.AI1

Analyze Images (Vision)

ActionIn the docs only

Going by its name, this module hands an image to the vision side of SectorFlow.AI and brings the result back into your scenario, ready for the next module.

When to use it
photos arrive in a shared folder or an inbox and someone currently describes them by hand.
Watch out
the app documentation in Make lists no accepted file type or size, so test with a real sample before you rely on it.
SectorFlow.AI2

Create an Image using Dall-E 3

ActionIn the docs only

A text prompt from your scenario becomes a finished picture, generated with Dall-E 3 through your SectorFlow.AI account, so nobody has to open an image tool and type the same request again.

When to use it
you already know Dall-E 3 gives the look you want, for blog headers or social posts.
Watch out
each image is one operation, meaning one run of one module counted on your Make plan.
SectorFlow.AI3

Create an Image using Google Imagen 2

ActionIn the docs only

Pick this one to have Google Imagen 2 draw the picture instead of another model, while the rest of your scenario stays the same: same connection, same prompt mapped from the previous module.

When to use it
your team compared models and prefers what Imagen 2 produces for its visuals.
Watch out
swapping models means swapping the module, so keep the prompt in one place you can remap quickly.
SectorFlow.AI4

Create an Image using Google Imagen 3 Fast

ActionIn the docs only

Your scenario gets an image from Google Imagen 3 Fast, the variant whose name puts speed first, which suits a flow where many prompts come in and each one needs a picture back.

When to use it
you produce draft visuals in volume and a quick result matters more than a polished one.
Watch out
the documentation gives no figure on speed or quality, so compare a few outputs with the other image modules first.
SectorFlow.AI5

Create an Image using Topic Selected Image LLM

ActionIn the docs only

Instead of naming a model yourself, you let the image model chosen for a SectorFlow.AI topic do the drawing, so your scenario follows whatever setting the topic already carries in the app.

When to use it
an admin manages model choices in SectorFlow.AI and the scenario should not hardcode one.
Watch out
run List Topics first to find the topic you need, then map it here.
SectorFlow.AI6

Get Chat Thread

ActionIn the docs only

This module brings one whole SectorFlow.AI conversation into your scenario, so you can reuse what was said somewhere else, in a document, a CRM note or a message to a colleague.

When to use it
a conversation reaches a conclusion and the result has to leave SectorFlow.AI.
Watch out
it needs to know which thread you mean, so place List Chats before it or map a thread from an earlier module.
SectorFlow.AI7

List Chats

SearchIn the docs only

You see your SectorFlow.AI conversations inside Make, one bundle per chat, which is the easiest way to pick up threads and hand them to the modules that read or rename them.

When to use it
you want to archive, sort or review conversations without scrolling through the app.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per bundle.
SectorFlow.AI8

List Experts

SearchIn the docs only

Your SectorFlow.AI experts show up as bundles in the scenario, so you can pick the right one by name instead of copying an identifier out of the app.

When to use it
right before Update a File on a SectorFlow Expert, to point that module at the expert that should receive the file.
Watch out
if the search returns several experts, add a filter so the next module only gets the one you mean.
SectorFlow.AI9

List Models

SearchIn the docs only

This search shows which models your SectorFlow.AI account can reach, straight in Make, so you build on what is really there rather than on a guess or an old screenshot.

When to use it
you set up a new scenario and want to check the options before choosing a chat or image module.
Watch out
one bundle comes out per model, so it is a check you run in testing more than a step to keep live.
SectorFlow.AI10

List Topics

SearchIn the docs only

Here you get the topics set up in your SectorFlow.AI account, one bundle each, which feeds any module that works from a topic rather than from a model you name yourself.

When to use it
before Create an Image using Topic Selected Image LLM, to hand it the right topic.
Watch out
a topic renamed in SectorFlow.AI may no longer match a filter you wrote on its old name.
SectorFlow.AI11

Make an API Call

ActionIn the docs only

When the thirteen other modules stop short, this one lets you call any endpoint of the SectorFlow.AI API from your scenario, reusing the same connection, so you never have to handle the key twice.

When to use it
you need something SectorFlow.AI offers in its API that no listed module covers.
Watch out
you write the request yourself, so keep the vendor API documentation open while you set it up.
SectorFlow.AI12

Send Chat

ActionIn the docs only

A message from your scenario goes to SectorFlow.AI as a chat, so questions coming from forms, tickets or spreadsheets reach the AI without anyone pasting them in by hand.

When to use it
it is the natural first module to try, right after whatever app collects your requests.
Watch out
each request sent is one operation, so a busy source app adds up quickly on your plan.
SectorFlow.AI13

Update a Chat Thread Title

ActionIn the docs only

Your SectorFlow.AI conversations get names that say what they are about, set by the scenario from the data it already holds, like a customer name or a ticket subject.

When to use it
threads created by automation all look alike in the app and your team struggles to find one.
Watch out
the module needs the thread to rename, so map it from List Chats or from the module that created it.
SectorFlow.AI14

Update a File on a SectorFlow Expert

ActionIn the docs only

This keeps the files behind a SectorFlow.AI expert current: when a document changes elsewhere, the scenario pushes the new version to the expert that relies on it.

When to use it
a price list, a policy or a product sheet is edited in a storage app and the expert should answer from the latest copy.
Watch out
the Free plan caps files at 5 MB, so check the size of your documents before you automate the upload.
Need help

Need help automating SectorFlow.AI with Make?

A person reads every message.

FAQ

SectorFlow.AI and Make: common questions

01Is the SectorFlow.AI Make integration free?
Yes, on the Make side. SectorFlow.AI is a standard app, so it works on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. Your SectorFlow.AI account is a separate matter: the app asks for an active account, and its own pricing page covers the subscription.
02What do you need to connect SectorFlow.AI to Make?
An active SectorFlow.AI account and an API key. You create the key in SectorFlow.AI: click your initials, open your account page, go to the API Keys section and click Create a token. Give it a name, choose an expiration time, save, and copy the key displayed. In Make, add any SectorFlow.AI module, click Create a connection, paste the key, and the connection is reused by every other SectorFlow.AI module in your scenarios.
03Does SectorFlow.AI trigger Make scenarios in real time?
No. SectorFlow.AI has no trigger module in Make, scheduled or instant, so it cannot start a scenario by itself. You start the scenario another way: with a trigger from the app where your requests come from, or with the schedule on the first module, every 15 minutes by default. On a paid plan the interval can go down to 1 minute. Either way, the SectorFlow.AI modules then run as the next steps.
04What if a SectorFlow.AI module is missing in Make?
Use Make an API Call. It is part of the 14 modules and lets your scenario reach any endpoint of the SectorFlow.AI API with the same connection, so you are not limited to the chat, image, list and update modules. Keep in mind that the Make documentation for this app says it was generated by AI and may contain mistakes, so confirm anything important with SectorFlow.AI before you build around it.
05Should you use Make or n8n for SectorFlow.AI?
It depends on where your other automations already live. On Make, SectorFlow.AI comes with 14 ready modules and a way to call its API, through Make an API Call. Many apps also have an n8n node, so check whether SectorFlow.AI does before you decide. The fair test is to build the same small scenario in both and keep the tool your team finds easier to maintain. The n8n vs Make comparison linked above lists the criteria in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations