Resources · Make integration

Finolog Make integrationAutomate Finolog with Make.

Can Make keep Finolog in step with the rest of your tools? The Finolog Make integration gives you 34 modules: 7 scheduled triggers, 21 actions and 6 searches. This guide is for finance and ops leads who build their own automations, and it takes you from connection to a working first scenario.

Try the Finolog integration on MakeSee the 34 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Finolog Make integration automate?

The Finolog Make integration links your Finolog account to Make so records move on their own. You build a scenario, the automation itself, out of modules: each module is one brick that watches, creates, reads, updates or deletes accounts, companies, contractors, categories or transactions in Finolog.

Contractors created from your sales tools. When a client signs in your CRM, Create a Contractor opens the matching record in Finolog, and Update a Contractor keeps it current when the client's details change on the sales side.

Transactions pushed to the team. Watch Transactions picks up transactions on the scenario's schedule and hands each one to a chat, a spreadsheet or a report builder, so the people who need the numbers stop asking for exports.

Cleaner reference data. List Categories and List Companies return what already exists, which lets a scenario check before it calls Create a Category or Create a Company and avoid duplicates.

What Make does not give you here: an instant trigger. All 7 Finolog triggers are scheduled, and when a listed module falls short, Make an API Call reaches the rest of the Finolog API with the same connection. The docs also warn that their Finolog pages are AI-generated from vendor material, so test each module with Run once. Before you commit, the Make review and Make pricing pages explain the platform and its plans, and n8n vs Make helps if you are weighing both tools.

Connect

How do you connect Finolog to Make?

  1. 01

    Copy your API key in Finolog

    Open Finolog, go to your profile through the user menu and copy the API key shown there. You need an active Finolog account for this key to exist, so sort out your Finolog subscription first if it has lapsed.

  2. 02

    Add a Finolog module in Make

    In your scenario, add any Finolog module and click Create a connection. A connection is your Finolog account linked to Make once, then reused by every Finolog module you add later.

  3. 03

    Paste the key and save

    Give it a name in the Connection name field if you like, which helps when a client and your own company each have an account. Paste the API key, confirm, and Make now reads your Finolog data.

First scenario

Your first scenario with Finolog

GoalWhen a deal is won in another app, Make creates the matching contractor in Finolog.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. This is where the flow starts.

  2. 02

    Pick the starting app

    Search the app where deals are closed, your CRM or a form tool, and choose its trigger. Connect that account so Make can see the new clients it hands over.

  3. 03

    Add Create a Contractor

    Click the + to the right of the first module, search Finolog and pick Create a Contractor. Choose your Finolog connection, or create it with the API key from your profile.

  4. 04

    Map the client data

    Fill the module fields by mapping values from the first module, such as the client's name. Make lists what it can read from Finolog once the connection works.

  5. 05

    Test with Run once

    Click Run once, then trigger a test deal. Open each module's bubble to read the bundles it received, and check the contractor now exists in Finolog.

  6. 06

    Schedule and switch it on

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

Triggers

Finolog triggers: what starts a scenario

7 modules start a scenario when something happens in Finolog. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Finolog as soon as it happens.

Finolog1Watch Accounts

Watch Accounts

triggerIn the docs only

Watch Accounts hands the accounts it picks up in Finolog to your scenario, one bundle each, so an account your finance team adds can reach a spreadsheet or a chat without anyone retyping its details. A bundle is simply one item passed from a module to the next.

How it fires
scheduled. Make checks Finolog on the scenario's schedule, so an account shows up at the next check rather than the instant it is saved.
When to use it
when opening an account should notify the people who reconcile it.
Watch out
the docs give this module no description, so run it once and read the bundles before you rely on it.
Finolog2Watch Categories

Watch Categories

triggerIn the docs only

Categories shape every Finolog report, and Watch Categories tells your other tools when that structure changes. Each category it finds leaves the module as one bundle, ready to be copied into a budget sheet or a reporting tool that uses the same labels.

How it fires
scheduled. Make polls Finolog at the interval set on the scenario, 15 minutes by default and never faster than that on the Free plan.
When to use it
when an accountant adds a category and a shared budget file must follow.
Watch out
an update to a category may not count as something new to watch; test that case first.
Finolog3Watch Companies

Watch Companies

triggerIn the docs only

With Watch Companies, the companies you track in Finolog become a starting point for automation. Each company the module returns travels down the scenario as its own bundle, which is handy when you run several legal entities and each needs its own setup elsewhere.

How it fires
scheduled. Make asks Finolog for companies each time the scenario's schedule comes around, so nothing moves between two checks.
When to use it
when a new entity in Finolog should open a folder, a project or a checklist in another tool.
Watch out
this module has no official description; confirm what it returns with Run once.
Finolog4Watch Contractors

Watch Contractors

triggerIn the docs only

Your clients and suppliers live in Finolog as contractors, and Watch Contractors lets the rest of your stack learn about them without copy and paste. The module passes each contractor it detects to the next step, where you can create a CRM contact or post a message to the sales team.

How it fires
scheduled. Make queries Finolog on the scenario's schedule; paid plans allow checks as often as every minute.
When to use it
when accounting registers a supplier and purchasing needs the same record.
Watch out
pair it with List Contractors elsewhere, never with Create a Contractor on the same data, or records can loop back.
Finolog5Watch Projects

Watch Projects

triggerIn the docs only

Projects are the only Finolog object in this app that you can watch but not create or edit from Make, which makes Watch Projects your one way to react to them. Each project it catches flows on as a bundle to whatever tool your team plans work in.

How it fires
scheduled. Make looks at Finolog projects whenever the scenario's schedule runs, not as soon as a project is saved.
When to use it
when a project opened in Finolog should appear in a task board or a team channel.
Watch out
no listed module edits a project; Make an API Call is the only route, and only if the Finolog API allows it.
Finolog6Watch Requisites

Watch Requisites

triggerIn the docs only

Watch Requisites follows the requisites stored in Finolog and pushes each one into your scenario, so payment details that finance records do not stay locked in a single tool. What arrives is one bundle per requisite, which a later module can file or share.

How it fires
scheduled. On every tick of the scenario's schedule, Make asks Finolog for requisites and passes on what it finds.
When to use it
when accounts payable keeps a separate register and it must match Finolog.
Watch out
the docs say nothing about the fields a requisite carries, so read one real bundle before mapping anything.
Finolog7Watch Transactions

Watch Transactions

triggerIn the docs only

Watch Transactions follows the money itself: it sends the transactions it picks up to the next module, one bundle per transaction. From there, a scenario can post a line to a chat, add a row to a sheet or feed a dashboard.

How it fires
scheduled. Make checks Finolog when the scenario's schedule comes due, so a transaction reaches your tools at the following check.
When to use it
when managers want to see money movements without opening Finolog.
Watch out
each transaction costs at least one operation per module it passes through, so busy accounts use your plan faster.
Modules

Finolog modules: what Make can do in your account

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

Finolog1

Create a Category

ActionIn the docs only

Create a Category adds a new category to Finolog from a scenario, so your reporting structure can grow with the business instead of waiting for someone to add labels by hand.

When to use it
a new cost center is approved in another tool and Finolog should gain the matching category.
Watch out
run List Categories first and add a filter, otherwise each run can create a duplicate.
Finolog2

Create a Company

ActionIn the docs only

For groups that run several entities, Create a Company sets up a new company in Finolog straight from the data of an earlier module, without a trip through the Finolog screens.

When to use it
legal registers a subsidiary in a form or a tracker, and finance needs it ready in Finolog.
Watch out
this is rare enough that a manual approval step in front of it, such as a filter on a status value, keeps mistakes out.
Finolog3

Create a Contractor

ActionIn the docs only

This is the module that saves the most retyping: it opens a contractor record in Finolog from a client or supplier that already exists in your CRM, form or e-shop.

When to use it
a deal is marked won and the client should exist in Finolog before the first invoice goes out.
Watch out
check with List Contractors before creating, since two runs on the same client produce two contractors.
Finolog4

Create a Transaction

ActionIn the docs only

Create a Transaction records a money movement in Finolog from an event elsewhere, which keeps your cash picture complete when payments happen in tools Finolog does not see.

When to use it
a payment platform confirms a sale and the amount should land in Finolog under the right account.
Watch out
test with Run once on a single real payment and check the result in Finolog before you switch the scenario on.
Finolog5

Create an Account

ActionIn the docs only

Opening an account in Finolog can follow automatically from a decision taken somewhere else: Create an Account adds it with the values you map from the previous module.

When to use it
finance approves a new account in a request form and wants it in Finolog without a second data entry.
Watch out
accounts anchor transactions, so a wrongly named one spreads; test on a copy of the data first.
Finolog6

Delete a Category

ActionIn the docs only

Delete a Category removes a category from Finolog, the clean-up step for a scenario that keeps your list of categories aligned with a master list kept elsewhere.

When to use it
a cost center is closed in your budgeting tool and its category should disappear too.
Watch out
a delete cannot be undone from Make, and transactions may still use that category; check before the module runs.
Finolog7

Delete a Company

ActionIn the docs only

When an entity is wound down, Delete a Company takes it out of Finolog from the scenario, instead of leaving a stale company in every report and drop-down.

When to use it
legal marks a company as closed and finance has already moved or archived what it held.
Watch out
nothing brings the company back from Make, so place a filter before this module and test on a dummy entry.
Finolog8

Delete a Contractor

ActionIn the docs only

Duplicate or obsolete contractors clutter every payment screen, and Delete a Contractor lets a scenario remove the ones you have flagged, one bundle at a time.

When to use it
a cleanup sheet lists contractors to retire and you want Finolog to match it.
Watch out
the deletion is final; map the exact contractor from Get a Contractor or List Contractors, never a guessed value.
Finolog9

Delete a Transaction

ActionIn the docs only

Delete a Transaction erases a transaction from Finolog, which is useful when the source of truth cancels an operation that a scenario had already recorded.

When to use it
a payment is refunded and cancelled on your payment platform, and the Finolog entry must go.
Watch out
removing money movements changes balances; keep a log step, like a sheet row, before this module so you can trace every deletion.
Finolog10

Delete an Account

ActionIn the docs only

Of the five delete modules, this one has the widest effect: Delete an Account takes a whole account out of Finolog, together with its place in your reports.

When to use it
an account is closed at the bank and the closure is confirmed in your approval tool.
Watch out
no undo exists in Make; keep this module behind a filter and a manual confirmation, and never run it on a schedule without one.
Finolog11

Get a Category

ActionIn the docs only

Get a Category fetches one category you already point to, so later modules can use its details instead of a bare reference passed along by the trigger.

When to use it
a transaction arrives from Watch Transactions and your report needs the category's full label.
Watch out
it returns a single category; to browse all of them, List Categories is the right module.
Finolog12

Get a Company

ActionIn the docs only

With Get a Company, a scenario reads the details of one Finolog company it already knows, which is how you enrich a message or a document with the entity's own data.

When to use it
an approval email should name the company involved rather than show a code.
Watch out
map the company from an earlier module; without that value, the module has nothing to fetch.
Finolog13

Get a Contractor

ActionIn the docs only

Pulling one contractor's record into a scenario takes a single module: Get a Contractor returns that client or supplier so you can reuse its details downstream.

When to use it
before a Slack alert about a large payment, you want the contractor's name in the message.
Watch out
each call counts as one operation, so skip it when the trigger bundle already carries what you need.
Finolog14

Get a Transaction

ActionIn the docs only

Get a Transaction reads back one transaction from Finolog, which is the safe way to check what is stored before you update or delete it.

When to use it
a refund request comes in and the scenario must confirm the original transaction first.
Watch out
it works on one transaction you identify; to find transactions by searching, List Transactions returns zero, one or many results.
Finolog15

Get an Account

ActionIn the docs only

Get an Account brings the details of one Finolog account into your scenario, handy when a transaction points to an account and you want more than that pointer.

When to use it
a cash alert should state which account moved, in words your managers recognize.
Watch out
the docs list no fields for this module, so run it once and look at the bundle before mapping anything from it.
Finolog16

List Accounts

SearchIn the docs only

List Accounts is a search: it returns every account that matches, each as its own bundle, so one run can feed a whole overview sheet or a loop of checks.

When to use it
a finance lead wants a sheet that lists all Finolog accounts, rebuilt whenever the scenario runs.
Watch out
a search can return zero, one or many bundles; with many, each following module runs once per bundle and uses operations.
Finolog17

List Categories

SearchIn the docs only

Before creating anything, List Categories shows what already exists: it returns the categories in Finolog as separate bundles you can compare or copy.

When to use it
a scenario must check whether a category is there before calling Create a Category.
Watch out
when the search finds nothing, the modules after it do not run, so plan a route for the empty case.
Finolog18

List Companies

SearchIn the docs only

List Companies returns the companies set up in Finolog, one bundle each, the natural base for any scenario that works across all your entities.

When to use it
a group controller wants one report line per company, pulled together in a spreadsheet.
Watch out
the results arrive as separate bundles; add an aggregator from Make if you need them merged into one message.
Finolog19

List Contractor Requisites

SearchIn the docs only

This search is specific to one contractor: List Contractor Requisites returns the requisites stored for that client or supplier, one bundle each.

When to use it
before paying a supplier from another tool, you want the details recorded in Finolog next to the payment request.
Watch out
a contractor can have zero requisites, in which case nothing flows on; route that case to a reminder for finance.
Finolog20

List Contractors

SearchIn the docs only

List Contractors searches your Finolog clients and suppliers and returns the matches as bundles, which is how a scenario avoids creating the same contractor twice.

When to use it
a new customer arrives from your CRM and you check Finolog before calling Create a Contractor.
Watch out
an empty result stops the modules that follow, so decide what happens when no contractor matches.
Finolog21

List Transactions

SearchIn the docs only

Where Watch Transactions reacts, List Transactions looks things up: it returns the transactions that match as bundles, whenever a scenario needs them mid-flow.

When to use it
a request for a statement arrives by email and the scenario gathers the transactions to attach to the reply.
Watch out
many results mean many bundles and many operations downstream; aggregate them before sending anything.
Finolog22

Make an API Call

ActionIn the docs only

Make an API Call covers everything the listed modules leave out: it calls any endpoint of the Finolog API with the connection you already set up.

When to use it
you need something no listed module does, such as touching a project, provided the Finolog API offers it.
Watch out
you build the request yourself from the Finolog API reference, so read that reference and test with Run once.
Finolog23

Update a Category

ActionIn the docs only

Renaming or adjusting a category no longer needs a trip into Finolog: Update a Category changes an existing one with the values mapped from your scenario.

When to use it
your budgeting tool renames a cost center and Finolog should show the same label.
Watch out
fields you leave empty may be sent as empty; run a test on one category and check what stays.
Finolog24

Update a Company

ActionIn the docs only

Update a Company edits the record of a company in Finolog, so a change made in your legal or admin tool reaches finance without an email in between.

When to use it
an entity changes its registered details and Finolog should match the admin register.
Watch out
map the right company from Get a Company or List Companies first, since a wrong mapping edits another entity.
Finolog25

Update a Contractor

ActionIn the docs only

Client details change often, and Update a Contractor keeps Finolog in line with the tool where those changes happen first, usually your CRM.

When to use it
a sales rep corrects a client record and accounting should see the same version.
Watch out
do not start this scenario from Watch Contractors while another scenario pushes the same changes back, or the two can feed each other.
Finolog26

Update a Transaction

ActionIn the docs only

Update a Transaction corrects a transaction already in Finolog, the fix for entries created too early, before a payment platform confirmed the final state.

When to use it
a payment that was pending is confirmed and its Finolog entry needs the new information.
Watch out
avoid starting this from Watch Transactions on the same records, since each update can be picked up again at the next check.
Finolog27

Update an Account

ActionIn the docs only

Update an Account changes an existing Finolog account from the scenario, keeping names and settings aligned when the decision is taken outside Finolog.

When to use it
finance renames an account in its approval tool and wants Finolog to follow at once.
Watch out
get the account first with Get an Account and compare, so the module only runs when something actually differs.
Need help

Need help automating Finolog with Make?

A person reads every message.

FAQ

Finolog and Make: frequent questions

01Is the Finolog Make integration free?
Yes, on the Make side. Finolog is a standard app, so its 34 modules are available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. You still need an active Finolog account, which Finolog bills on its own terms.
02What do you need to connect Finolog to Make?
An active Finolog account and its API key. In Finolog, open your profile from the user menu and copy the API key displayed there. In Make, add any Finolog module to a scenario, click Create a connection, optionally name the connection, then paste the key. The connection is saved once and every Finolog module in your scenarios reuses it, so there is nothing to repeat when you add a second or third module. If the key is refused, copy it again from the profile and confirm the Finolog account is still active.
03Do Finolog triggers in Make react in real time?
No. All 7 Finolog triggers are scheduled: Make checks Finolog on the scenario's schedule rather than being called by Finolog when something happens. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you check as often as every minute, which brings the delay down without making it instant. If you need to react faster to an event that starts outside Finolog, begin the scenario in that other app and use the Finolog action modules to write the result.
04What if a Finolog module is missing in Make?
Use Make an API Call. Finolog has this module in Make, and it reaches any endpoint of the Finolog API with the connection you already created. For example, the listed modules only watch projects, so any other work on a project goes through this module, if the Finolog API supports it. You write the request from the Finolog API reference, then test it with Run once. Note that Make's own documentation for Finolog is marked as AI-generated from vendor material and may contain mistakes, so verify important behavior directly and contact Finolog for questions on its API.
05Should you use Make or n8n for Finolog?
It depends on the tool your team already builds in. Make offers 34 Finolog modules, from scheduled triggers to searches and a universal API call, and the visual editor suits people who are new to automation. Many apps also have an n8n node, so check whether Finolog is covered there before choosing. Compare the criteria that matter to your case: who maintains the scenarios, which other apps they touch and how your plan counts usage. The n8n vs Make comparison on this site walks through those points without ranking either one.
Same platform

Other docs you might need on this stack.

Browse all integrations