Resources · Make integration

Flowtly Connector Make integrationAutomate Flowtly Connector with Make.

Can Make log hours in Flowtly for you? The Flowtly Connector Make integration gives you 6 action modules, with no trigger. This guide is for teams that track time in Flowtly: connect the account, build a first scenario, then pick the right module.

Try the Flowtly Connector integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Flowtly Connector Make integration do?

The Flowtly Connector Make integration links your Flowtly account to Make so a scenario, the automation you build as a chain of modules, can read and write Flowtly data for you. It offers 6 action modules and no trigger, so another app or a schedule has to start the flow.

Hours logged without retyping. When a task closes in another tool, a scenario can pass the details to Create logged hour, so the entry lands in Flowtly without anyone copying it by hand.

A project list other tools can use. Get all Projects pulls the projects from your Flowtly account, and Get all Employees does the same for people. Judging by their names, both return a list, and each item would move on as a bundle, one element passed to the next module, ready to feed a spreadsheet or a report.

Time data for review. Get all logged hours reads the entries already saved, which helps when a manager wants hours next to billing or planning data.

Know the limits before you start. The official documentation for this app is marked as limited, so field names and behavior are not described there: test each module with a real account first. The Make troubleshooting guide helps when a run fails, and the Make training covers scenario basics. If you are still choosing a platform, the n8n vs Make comparison lays out the differences.

Connect

How do you connect Flowtly Connector to Make?

  1. 01

    Add a Flowtly Connector module

    In your scenario, click the + and search for Flowtly Connector. Pick any of its modules, then click Create a connection. A connection is your Flowtly account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when several Flowtly accounts or workspaces end up in the same Make organization. Pick something your teammates will recognize at a glance.

  3. 03

    Authorize and save

    Authorize Make on the Flowtly page if one opens, or paste the key Flowtly gives you, then click Save. The documentation does not list prerequisites, so use an account that can see the projects and hours you plan to automate.

First scenario

Build your first scenario with Flowtly Connector

GoalWhen a task is finished in another app, Make looks up your Flowtly projects and logs the hours in Flowtly.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Flowtly Connector has no trigger, this first module comes from the app where tasks get finished.

  2. 02

    Add Get all Projects

    Click the + on the right of the first module, search Flowtly Connector and pick Get all Projects. Click Create a connection to link your account, then fill the module fields.

  3. 03

    Add Create logged hour

    Click the + again and choose Create logged hour. Map the task details and the project into its fields. It runs once per bundle received, so in the test check it logs one entry, not one per project.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received, then check in Flowtly that the new entry looks right.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.

Modules

What can the Flowtly Connector modules do?

Flowtly Connector gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Flowtly Connector1

Create logged hour

ActionIn the docs only

Adds a time entry to Flowtly from data another module hands over, so nobody has to type hours twice. Going by the names, it is the only module here built to write.

When to use it
a task or ticket closes in another tool and its time should appear in Flowtly as a logged hour.
Watch out
the documentation does not list its fields, so run it once with test data and check the result in Flowtly.
Flowtly Connector2

Generic Request

ActionIn the docs only

Gives you a catch-all option when none of the named modules covers the job. The documentation says nothing about how it works, so treat what it can reach as something to test rather than assume.

When to use it
the five other modules do not fit your case and you want to explore what else the connector accepts.
Watch out
without documentation, try it in a separate test scenario before touching real data.
Flowtly Connector3

Get all Employees

ActionIn the docs only

Returns the people in your Flowtly account, which is handy when another step needs to know who the hours belong to. Each person comes out as its own bundle for the next module.

When to use it
you sync a team list to a spreadsheet or match people between Flowtly and another app.
Watch out
every bundle that the following modules process costs an operation, so a long list adds up.
Flowtly Connector4

Get all Projects

ActionIn the docs only

Brings back the projects saved in Flowtly, giving the rest of the scenario a list to pick from or to copy elsewhere. Each project becomes one bundle.

When to use it
before Create logged hour, to find the project an entry should belong to, or to mirror projects in a planning tool.
Watch out
the next module runs once per project it receives, so check after Run once how many bundles come out before chaining a write.
Flowtly Connector5

Get all logged hours

ActionIn the docs only

Reads the time entries already recorded in Flowtly, so you can reuse hours in a report or an invoice draft without exporting them by hand.

When to use it
a manager wants logged hours next to billing figures in a sheet or a dashboard.
Watch out
the documentation gives no detail on filters or volume, so run it once and look at what comes back before building on it.
Flowtly Connector6

Get organization instance

ActionIn the docs only

Fetches information about your Flowtly organization, which is useful when a scenario needs account-level context rather than a project or a person.

When to use it
you want to check which Flowtly organization a connection points to, for example when a team runs more than one.
Watch out
the documentation does not say which details it returns, so read the bundle after a Run once test.
Need help

Need help automating Flowtly Connector with Make?

A person reads every message.

FAQ

Flowtly Connector and Make: common questions

01Is the Flowtly Connector Make integration free?
Yes, Flowtly Connector is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and count usage in credits, which are operations, each month. Any cost of the Flowtly subscription itself is a separate matter between you and Flowtly.
02What do you need to connect Flowtly Connector to Make?
A Flowtly account and a Make account are enough to start, since the documentation lists no other prerequisite. Add any Flowtly Connector module, click Create a connection, give it a name if you like, authorize Make on the Flowtly page or paste the key Flowtly provides, and click Save. Because the documentation for this app is marked as limited, use an account that can see the projects and hours you want to automate, and test the connection with a single module first.
03Does Flowtly Connector trigger scenarios in real time?
No, Flowtly Connector has no trigger module at all, neither scheduled nor instant. A scenario that uses it has to start another way: with a trigger from a different app, such as a task tool or a form, or with a schedule set on the first module, which runs every 15 minutes by default. On the Free plan, 15 minutes is the shortest interval, and paid plans go down to 1 minute. The Flowtly modules then run as steps inside that scenario.
04What if a Flowtly Connector module is missing in Make?
It depends on what you need. Flowtly Connector offers 6 modules and no Make an API Call module, so there is no universal fallback built into the app. The Generic Request module may help, but the documentation does not describe it, so test it before relying on it. When nothing fits, another app in your stack may cover part of the job, or the team at Hack'celeration can look at your case and suggest a route.
05Should you use Make or n8n for Flowtly Connector?
It depends on the tool your team already uses and on what each one offers for Flowtly. On Make, Flowtly Connector brings 6 action modules and runs on the Free plan, with the limits of that plan. The same app often has a node in n8n too, so check what that node covers before choosing. Compare the modules each side offers for your exact need, such as logging hours or reading projects, rather than picking on reputation alone.
Same platform

Other docs you might need on this stack.

Browse all integrations