Resources · Make integration

FinImpulse Make integrationAutomate FinImpulse with Make.

Need asset data from FinImpulse inside your other tools? The FinImpulse Make integration gives you 13 modules: 9 searches and 4 actions, with no trigger. This page shows how to link your API key and build a first scenario that reads data.

Try the FinImpulse integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the FinImpulse Make integration do?

The FinImpulse Make integration lets a Make scenario (the automation you build, a chain of steps) ask FinImpulse for data about an asset and pass the answer to another app. Each step is a module, and your FinImpulse account is linked once through a connection that every module reuses.

A watchlist that fills itself. Start with Search assets to find the asset, then Get key metrics and Search risk metrics to bring its figures into a spreadsheet or database of your choice.

An analyst digest for your team. Search analyst ratings, Search analyst actions and Get recommendation trends collect what analysts say about an asset, ready to send in a chat or email module from another app.

A news and earnings brief. Search news and Search earnings data feed a short report, while Search price history and Search annual returns add the longer view.

Know the limits before you start. FinImpulse has no trigger, so Make never learns on its own that something changed: the scenario runs on a schedule or is started by another app. The official documentation is also flagged as AI-generated, so check each field against your FinImpulse account. The same app may have an n8n node too; the n8n vs Make comparison helps you pick, and the Make pricing page explains what each plan allows.

Connect

How do you connect FinImpulse to Make?

  1. 01

    Copy your API key

    Log in to FinImpulse, open the API panel from your account dashboard and copy the API key shown on screen. You need an active FinImpulse account and a personal API token for this.

  2. 02

    Add a FinImpulse module

    In your Make scenario, add any FinImpulse module and click Create a connection. The Connection name field is optional, but a clear name helps when you later link a second account.

  3. 03

    Paste the key and save

    Paste the credentials you copied from FinImpulse, or follow the on-screen instructions, then save. From now on every FinImpulse module in any scenario can pick this connection from a list.

First scenario

Your first scenario with FinImpulse

GoalWhen the scenario's schedule comes around, Make finds an asset in FinImpulse and reads its summary for the next app.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Since FinImpulse has no trigger, this first module will be a search.

  2. 02

    Add Search assets

    Search for FinImpulse, pick Search assets and select the connection you created. Fill in what you are looking for so the module knows which asset to return.

  3. 03

    Chain Get asset summary

    Click the + on the right of the search and add Get asset summary. Map the asset returned by the search into it, so each bundle (one item passed along) gets its own summary.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open them and check that the asset and its summary are the ones you expected.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What can the FinImpulse modules do?

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

FinImpulse1

Get asset summary

ActionIn the docs only

Get asset summary gives you the overview FinImpulse holds for a single asset, the quickest way to put a readable snapshot into a sheet, a message or a report.

When to use it
after a search has identified the asset, when you want one compact block of information rather than a detailed metric set.
Watch out
it works on one asset per bundle, so each asset you pass in costs one operation.
FinImpulse2

Get key metrics

ActionIn the docs only

With Get key metrics, a scenario reads the main figures FinImpulse tracks for one asset and hands them to the next module, ready to map into columns of a spreadsheet or fields of a database.

When to use it
when you keep a watchlist and want the numbers refreshed on each run instead of copied by hand.
Watch out
the documentation is AI-generated, so confirm which metrics come back with a Run once test before you map them.
FinImpulse4

Make an API call

ActionIn the docs only

Make an API call lets you reach any endpoint of the FinImpulse API from your scenario, reusing the same connection, so nothing is out of reach when the listed modules stop short.

When to use it
when FinImpulse offers data that none of the other 12 modules returns.
Watch out
you write the request yourself, so keep the FinImpulse API documentation open and test with Run once before scheduling.
FinImpulse5

Search analyst actions

SearchIn the docs only

Search analyst actions lists what analysts have done on an asset, one bundle per action, so you can see recent moves at a glance instead of reading reports one by one.

When to use it
when an alert in your team chat should mention each new analyst move on the assets you follow.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
FinImpulse6

Search analyst ratings

SearchIn the docs only

You get the individual analyst ratings FinImpulse has for an asset, each arriving as its own bundle that you can count or write to a row in a sheet.

When to use it
when a report must show who rates the asset and how, rather than the overall trend.
Watch out
one line per asset? Add a Make aggregator (the module that groups bundles back into one) right after the search.
FinImpulse7

Search annual returns

SearchIn the docs only

Search annual returns brings back the yearly return records FinImpulse holds for an asset, a simple way to feed a performance table without typing a figure.

When to use it
when you prepare a fact sheet or a portfolio review document and need the long view next to current metrics.
Watch out
each year may come back as a separate bundle, so check the output with Run once before mapping it into a template.
FinImpulse8

Search asset profile

SearchIn the docs only

The profile search returns descriptive information about an asset, the kind of context a reader needs before looking at any number, straight into your scenario.

When to use it
when you create a record for a new asset in your CRM or database and want its background filled in automatically.
Watch out
it returns bundles like any search, so plan for the case where nothing matches and the rest of the scenario receives nothing.
FinImpulse9

Search assets

SearchIn the docs only

Search assets is usually the entry point: it finds the assets that match what you ask for, and the result gives the other modules something to work on.

When to use it
as the first module of a scheduled scenario, since FinImpulse has no trigger to start the flow.
Watch out
a broad search can return many bundles, and each one multiplies the operations of every module that follows.
FinImpulse10

Search earnings data

SearchIn the docs only

This search collects the earnings records FinImpulse has for an asset, so a finance team can drop them into a shared sheet or an earnings note without copying anything by hand.

When to use it
when an earnings season brief has to cover several assets and you want the data gathered in one place.
Watch out
confirm the returned fields with Run once, since the documentation behind this module is AI-generated.
FinImpulse11

Search news

SearchIn the docs only

Search news pulls news items linked to what you search for, each as a bundle, which turns a manual reading routine into a feed you can post or store.

When to use it
when a sales or advisory team wants headlines about the assets their clients hold, delivered to a channel they already read.
Watch out
a news search often returns many items, and each one becomes a message unless an aggregator from Make groups them first.
FinImpulse12

Search price history

SearchIn the docs only

Price history lands in your scenario as a set of bundles, ready to append to a sheet that draws a chart or to a database behind a dashboard.

When to use it
when a dashboard needs past prices for an asset and you would rather not export them by hand.
Watch out
long histories mean many bundles, and on the Free plan a run stops after 5 minutes, so keep the scope narrow.
FinImpulse13

Search risk metrics

SearchIn the docs only

Search risk metrics fetches the risk indicators FinImpulse holds for an asset, useful when a compliance or portfolio team must keep them in its own tools.

When to use it
next to Get key metrics in a watchlist, so every asset row shows both its figures and its risk side.
Watch out
treat the values as FinImpulse data to verify, and compare a first Run once result with your FinImpulse account.
Need help

Need help automating FinImpulse with Make?

A person reads every message.

FAQ

FinImpulse and Make: common questions

01Is the FinImpulse Make integration free?
Yes, on the Make side. FinImpulse is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes per run and 512 MB of data transfer. Paid plans go down to 1 minute and remove the scenario limit. You still need an active FinImpulse account with an API token, and FinImpulse sets its own subscription terms on its pricing page.
02What do you need to connect FinImpulse to Make?
An active FinImpulse account and a personal API key. Open the API panel from your FinImpulse dashboard and copy the key shown on screen. In Make, add any FinImpulse module, click Create a connection, give it a name if you like, paste the key and save. Every FinImpulse module then reuses that connection, so you only do this once per account. If you run several FinImpulse accounts, give each connection a clear name so you pick the right one in every module.
03Can the FinImpulse Make integration start a scenario in real time?
No. FinImpulse has no trigger module, so it cannot tell Make that something changed. You start the scenario another way: set a schedule on the first module, every 15 minutes by default, and let it open with Search assets. Or place a trigger from another app first, such as a new row in a sheet, and let the FinImpulse modules run for that item. Keep in mind that every module in the run, from the search to the last step, counts as one operation per bundle it processes.
04What if the FinImpulse module you need is missing in Make?
Use Make an API call. It calls any endpoint of the FinImpulse API with the connection you already have, so data the 13 listed modules do not return is still reachable. You write the request yourself from the FinImpulse API documentation. Keep in mind that the Make documentation for this app is marked as AI-generated, so test every module with Run once before relying on it. Before scheduling, run the request once and read the bundle it returns, so you know exactly which values you can map into the next module.
05Should you use Make or n8n for FinImpulse?
It depends on the tool your team already runs. In Make, FinImpulse offers 13 modules, 9 searches and 4 actions including a generic API call, all built for a visual scenario editor. The same app may also exist as an n8n node. Compare the modules each side offers for your use case, and pick the platform where your other automations already live rather than splitting them. If you are new to both, start with a two-module scenario, test it with Run once, then add the other searches one at a time.
Same platform

Other docs you might need on this stack.

Browse all integrations