Resources · Make integration

Currency Make integrationAutomate Currency with Make.

Need amounts in another currency before they land in your tools? The Currency Make integration gives you 2 action modules, built into Make, with no account to link. This page shows what they do, where they fit in a flow and how to test your first build.

Try the Currency integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Currency Make integration do for you?

The Currency Make integration is a small built-in app that turns an amount from one currency into another in the middle of a scenario, the automation you build in Make as a chain of modules. A module is one brick of that chain. Currency has 2 of them, both actions, and it needs no account or key to work.

Prices shown in the buyer's currency. A store that sells abroad can send each new order through Convert an amount between currencies, then write the converted total into a table. If that table is in Airtable, the Airtable Make integration covers the saving part.

One reporting currency for finance. Invoices come in from several countries; put the conversion step before the line that records them, so every figure in your sheet speaks the same money.

Cleaner CRM data. A deal logged in a foreign currency can be converted before its value goes into your pipeline, so forecasts stop mixing apples and oranges.

What Currency does not do: it has no trigger, so it never starts a scenario on its own. Another app's module or the schedule on the first module has to launch the flow. It also has no Make an API Call module. If you are still weighing tools, the n8n vs Make comparison lays out the criteria, and Make training walks through scenarios like these from zero.

Connect

How do you connect Currency to Make?

  1. 01

    Add a Currency module

    In your scenario, click the +, search for Currency by name and pick the module you want. It sits among the apps built into Make, next to the other tools of the editor.

  2. 02

    Skip the connection step

    A connection is usually your account of an app linked to Make once. Currency is the exception: the documentation says you do not need one, so there is no Create a connection button to click and nothing to authorize.

  3. 03

    Fill the fields and map data

    Fill the module fields directly. Where a value comes from an earlier module, such as an order total, click into the field and map it from the data that module produced.

First scenario

Your first scenario with Currency

GoalWhen another app sends an amount into the scenario, Make converts it with Currency and passes the result to the next module.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Currency has no trigger, this first bubble belongs to another app.

  2. 02

    Pick the starting module

    Choose the app that holds the amounts, for example your store or your CRM, and create its connection. Each bundle it sends, one order or one deal, carries the amount you want to convert.

  3. 03

    Add Convert an amount between currencies

    Click the + on the right of the first module, search Currency and pick Convert an amount between currencies. Map the amount from the previous module into it.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module and read the bundles it received, to check the converted figure before anything else uses it.

  5. 05

    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.

Modules

What the Currency modules do

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

Currency1

Convert an amount between currencies

Action

You get the same amount expressed in another currency, ready for the next module to store, compare or send. It is the reason to add Currency to a scenario at all.

When to use it
right after the module that brings in a price, an invoice total or a deal value, and before the module that records it.
Watch out
the source of the rate is not stated in the Make documentation; check the result during Run once before relying on it.
Currency2

Actions

ActionIn the docs only

This second module is listed by Make as an action named simply Actions, with no official description to explain it. Before building a scenario around it, open it in the editor and look at what it asks for.

When to use it
when Convert an amount between currencies does not match what you need and the editor shows this module covers it.
Watch out
without a description, test it with Run once and read its output before chaining anything to it.
Need help

Need help automating Currency with Make?

A person reads every message.

FAQ

Currency and Make: common questions

01Is the Currency Make integration free?
Yes. Currency is a standard app, available from the Free plan. On Free you keep 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Every module run on one bundle is an operation, and usage is counted in credits per month. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Currency itself needs no account of its own: you only set up the app that feeds it.
02What do you need to connect Currency to Make?
Nothing beyond a Make account. The Make documentation states that the Currency app needs no connection, so you will not see an authorization window or a key field. You add the module, fill its fields and map the amount coming from an earlier module. The only connection your scenario needs is the one for the app that supplies the data, such as your store or your CRM, since Currency cannot start a flow by itself and always sits after another module.
03Does Currency react in real time?
No, because it has no trigger at all. Currency only works once a scenario is already running. To start that scenario, use a trigger from another app: an instant trigger fires as soon as the app calls Make through a webhook, while a scheduled one is polled on the scenario's schedule, every 15 minutes by default. Either way, the schedule on that first module sets the pace, and the conversion happens when the bundle reaches the Currency module.
04What if a Currency module is missing or too limited?
It depends on what you need. Currency has only 2 modules and no Make an API Call module, so there is no generic way to reach further inside this app. If converting an amount is not enough, look at another app that handles the data you work with, or ask the team for help: the Make agency builds scenarios that go beyond one module. Testing with Run once first shows exactly what the existing modules return, which often answers the question before you switch.
05Make or n8n for currency conversion?
It depends on your criteria, not on a winner. On the Make side, Currency is a built-in app with 2 action modules, no connection to set up and availability from the Free plan, which keeps a first scenario simple. n8n often has a node for the same app, but this page does not cover what n8n offers here, so compare the two tools on your own needs: how you like to build, which other apps you already connect, and who maintains the flows. The n8n vs Make comparison on the site walks through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations