Resources · Make integration

Overledger Make integrationAutomate Overledger with Make.

Want your blockchain events to start work in other tools on their own? The Overledger Make integration gives you 20 modules: 2 triggers and 18 actions for smart contracts, tokens and webhooks. This page shows how to link your account, build a first scenario and pick the right module.

Try the Overledger integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Overledger Make integration do for you?

The Overledger Make integration links your Overledger account to Make so blockchain activity can drive a scenario, the automation you build in Make as a chain of modules. You get 2 scheduled triggers that watch account and contract events, and 18 actions to read contracts, move tokens and manage webhooks, all without writing code.

Contract activity that reaches your team. Put Watch New Contract Event first, add Read from a Smart Contract to fetch the state you care about, then send the result to the app your team already reads. Nobody has to check a block explorer by hand.

Token transfers that follow the same path every time. The module names describe a sequence: Prepare a Transfer of Fungible Tokens, then Sign a Transaction, then Execute a Signed Token Transfer Transaction. Building it as a scenario keeps each step visible, and Run once lets you check what every module returned before anything goes live.

Webhooks you manage from one place. Create a Webhook Entity, Read Webhooks, Update a Webhook and Delete a Webhook cover the full life of a webhook, so an ops lead can audit or clean them up in a scenario.

One honest limit: the Make documentation for Overledger is short. Make says there is not enough public information about the app to describe it in full, so field names and behaviors are best confirmed with a test run. The Make troubleshooting guide helps when a run fails. If you are also weighing n8n, the n8n vs Make comparison sets the two side by side, and the Make training walks through scenario building step by step.

Connect

How do you connect Overledger to Make?

  1. 01

    Add an Overledger module

    In a scenario, click the +, search for Overledger and pick any module. Then click Create a connection. A connection is your Overledger account linked to Make once and reused by every Overledger module afterwards.

  2. 02

    Name the connection

    This step is optional but worth the few keystrokes. A clear name, such as the environment or the team that owns the account, helps you tell connections apart when several people share the same Make workspace.

  3. 03

    Authorize and save

    Follow the prompt Make shows: either approve access on the Overledger page, or paste the key Overledger gives you. Click Save. Make can now list what it can read from your account inside the module fields.

First scenario

Build your first scenario with Overledger

GoalWhen a new contract event shows up in Overledger, Make reads the contract and hands the result to the next step.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. This is where the first module, the one that starts everything, goes.

  2. 02

    Add the trigger

    Search for Overledger and choose Watch New Contract Event. Click Create a connection if you have not linked your account yet, then fill the fields Make shows.

  3. 03

    Read the contract

    Click the + to the right of the trigger and add Read from a Smart Contract. Map data from the trigger into its fields so each event points the read at the right contract.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. A bundle is one item passed from module to module, here one event.

  5. 05

    Schedule and switch on

    Set the schedule on the trigger. A new scenario checks every 15 minutes by default. Then switch the scenario on, and each check that finds a new event runs the chain.

Triggers

Which Overledger triggers can start a scenario?

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

Overledger1Watch New Account Event

Watch New Account Event

triggerIn the docs only

Start a scenario whenever something new happens on an account you follow in Overledger. Each new event arrives as one bundle, ready to be passed to the next module or to another app.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, with a shorter interval possible on paid plans.
When to use it
you want your team told about account activity, without anyone watching it.
Watch out
the documentation gives no detail on which events count, so run it once and read the bundles before building on it.
Overledger2Watch New Contract Event

Watch New Contract Event

triggerIn the docs only

Pick this one when the thing to follow is a smart contract rather than an account. The scenario starts from the events the contract emits, one bundle per event.

How it fires
scheduled. Make checks the app on the scenario's schedule, so an event waits until the next check before the scenario runs.
When to use it
a contract your product relies on emits an event and a follow-up step, such as reading its state or logging it, should happen every time.
Watch out
each event processed by each module counts as an operation on your Make plan, and a busy contract adds up quickly.
Modules

What can each Overledger module do?

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

Overledger1

Create a Webhook Entity

ActionIn the docs only

Registers a new webhook in Overledger straight from a scenario, so setting one up becomes a repeatable step instead of a manual task in the Overledger interface.

When to use it
each new project or client needs its own webhook, and you want it created the same way every time.
Watch out
keep what the module returns, since Update a Webhook and Delete a Webhook will need to know which webhook to act on.
Overledger2

Delete a Webhook

ActionIn the docs only

Removes a webhook you no longer need, which keeps your Overledger setup tidy and stops notifications that nobody reads anymore.

When to use it
a project closes and its webhook should go with it, as the last step of an offboarding scenario.
Watch out
treat a deletion as final. Put Read Webhooks and a filter before it so the scenario only removes the webhook you meant.
Overledger3

Execute a Signed Smart Contract Deployment Transaction

ActionIn the docs only

Sends a smart contract deployment that has already been signed, which is the moment the contract actually goes out. The word signed in the name tells you it expects a transaction prepared and signed earlier.

When to use it
at the end of a chain that starts with Prepare a Smart Contract Deployment Transaction and Sign a Transaction.
Watch out
test the whole chain with Run once and check every mapped value before switching it on for real.
Overledger4

Execute a Signed Smart Contract Invoke Transaction

ActionIn the docs only

Calls a function on a contract that already exists, once the call is signed. Where the deployment module puts a contract out, this one makes a live contract do something.

When to use it
after Prepare a Smart Contract Transaction and Sign a Transaction, when a business event should change something on chain.
Watch out
a call that writes to the chain is not something you take back, so check the mapped values in the Run once output first.
Overledger5

Execute a Signed Token Transfer Transaction

ActionIn the docs only

Sends a signed token transfer on its way. It is the last step of a transfer, the one that actually moves value from one address to another.

When to use it
a payout or a reward should go out automatically once an approval or an event upstream says so.
Watch out
add a filter before this module so only the bundles you expect reach it, since a wrong mapping here sends real tokens to the wrong place.
Overledger6

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Overledger API with the same connection as the other modules. It is the way out when none of the 20 listed modules does what you need.

When to use it
you know the Overledger API offers an operation that the named modules do not cover.
Watch out
you write the request yourself, so keep the Overledger API reference open, because the Make documentation for this app is limited.
Overledger7

Prepare a Basic NFT Token Deployment Transaction

ActionIn the docs only

Builds the transaction that deploys a basic NFT token, ready to be signed. Nothing is sent yet: you get the prepared transaction back as a bundle.

When to use it
you launch simple NFT collections often enough that doing each one by hand wastes time, and a standard template is enough.
Watch out
preparing is only the first move. Without Sign a Transaction and an execute module afterwards, nothing reaches the chain.
Overledger8

Prepare a Basic Token Deployment Transaction

ActionIn the docs only

Gives you a ready to sign transaction for deploying a basic fungible token, the kind used for points, credits or internal currencies.

When to use it
a new program or community needs its own token and the basic version fits, so there is no custom contract to write.
Watch out
the name says basic. If you need custom behavior, Prepare a Smart Contract Deployment Transaction is the closer match.
Overledger9

Prepare a Smart Contract Deployment Transaction

ActionIn the docs only

Prepares the deployment of your own smart contract rather than a basic template. The result is an unsigned transaction you then pass to Sign a Transaction.

When to use it
your developers wrote the contract, and the ops side wants to deploy new instances from a scenario when a request comes in.
Watch out
the documentation does not detail the fields, so read what Make shows in the module and confirm with a test deployment.
Overledger10

Prepare a Smart Contract Transaction

ActionIn the docs only

Sets up a call to a function on a deployed contract, filled from the fields Make displays. It is the usual starting point before Execute a Signed Smart Contract Invoke Transaction.

When to use it
an event elsewhere, like an order being approved, should trigger a contract function with values mapped from that event.
Watch out
if your call needs a structure the fields cannot express, look at the JSON body version instead.
Overledger11

Prepare a Smart Contract Transacton with JSON body

ActionIn the docs only

Does the same job as the previous module, but lets you describe the call as a JSON body. That suits developers who already have the payload written.

When to use it
the contract call carries nested or long parameters that are easier to paste as JSON than to map field by field.
Watch out
one missing quote or bracket in the JSON and the call fails. Test it with Run once before switching the scenario on.
Overledger12

Prepare a Transfer of Fungible Tokens

ActionIn the docs only

Builds a transfer of interchangeable tokens, where any unit is worth the same as another. You get a transaction to sign, not a completed transfer.

When to use it
rewards, refunds or payouts in tokens should follow an event in your CRM or billing tool.
Watch out
the transfer only happens after Sign a Transaction and Execute a Signed Token Transfer Transaction, so place all three in the same scenario.
Overledger13

Prepare a Transfer of a Non-Fungible Token

ActionIn the docs only

Prepares the move of one specific NFT to a new owner. Unlike the fungible version, it targets a single unique token rather than an amount.

When to use it
a ticket, certificate or collectible should reach the buyer once the sale is confirmed in another tool.
Watch out
map the token and the recipient from the right bundle. Run once shows exactly which values the module received.
Overledger14

Read Webhooks

ActionIn the docs only

Lists the webhooks set up on your Overledger account, so you can see at a glance what is sending notifications and where.

When to use it
before any update or deletion, or in an audit scenario that sends the current list to a sheet for review.
Watch out
treat it as the check step. Filtering its output before Delete a Webhook is what keeps a cleanup from removing the wrong entry.
Overledger15

Read from a Smart Contract

ActionIn the docs only

Fetches data from a contract without changing anything on chain, so it is the safe module to start with while you learn the integration.

When to use it
you want a balance, a status or a stored value from a contract and then send it to a report, a message or a database.
Watch out
every read still counts as an operation on your Make plan, even though nothing is written.
Overledger16

Read from a Smart Contract with JSON body

ActionIn the docs only

Reads contract data like the module above, with the request written as a JSON body. It helps when the query is complex or already exists in your codebase.

When to use it
a developer hands you the exact payload and you would rather paste it than rebuild it field by field.
Watch out
map values into the JSON carefully, since a missing quote or bracket makes the whole read fail.
Overledger17

Sign a Transaction

ActionIn the docs only

Signs a transaction that a Prepare module built, the step between preparing and executing. Without a signature, the execute modules have nothing valid to send.

When to use it
in every chain that writes to the blockchain, placed right after the Prepare module and right before the matching Execute module.
Watch out
this is the step that gives the go-ahead. Check in the Run once output what the Prepare module passed to it.
Overledger18

Update a Webhook

ActionIn the docs only

Changes an existing webhook rather than deleting it and creating a new one. Your setup stays in place, only the settings you edit change.

When to use it
the endpoint that receives notifications moves, and every webhook pointing at it should follow.
Watch out
you need to target the right webhook, so fetch it first with Read Webhooks and map its identifier from there.
Need help

Need help automating Overledger with Make?

A person reads every message.

FAQ

Overledger and Make: common questions

01Is the Overledger Make integration free?
Yes. Overledger is a standard app in Make, so its modules are available from the Free plan. The Free plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow a 1 minute interval and up to 40 minutes of execution. Make counts usage in operations: one module processing one bundle. This page says nothing about Overledger's own pricing, which is set by Overledger.
02What do you need to connect Overledger to Make?
An Overledger account and a Make account. The Make documentation lists no specific prerequisites for this app and gives no dedicated connection steps, so the generic flow applies. Add any Overledger module, click Create a connection, give it a name if you like, then either approve access on the Overledger page or paste the key Overledger provides. Click Save and the connection is ready for every Overledger module in your scenarios. If it fails, check the credentials on the Overledger side first, since the documentation offers no troubleshooting notes for this app.
03Does the Overledger trigger fire in real time?
No. Both Overledger triggers, Watch New Account Event and Watch New Contract Event, are scheduled. Make checks Overledger on the scenario's schedule instead of being told the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute. So an event waits until the next check before your scenario picks it up. If you need a shorter delay, move to a paid plan and tighten the schedule on the first module.
04What if the Overledger module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Overledger API with the same connection as the other modules, so you are not limited to the 20 listed ones. You write the request yourself, so keep the Overledger API reference at hand. Be aware that Make's own documentation for this app is limited: Make states there is not enough public information about Overledger to document it fully. In practice, test every new module with Run once and read the bundles it returns before you rely on it in a live scenario.
05Should you use Make or n8n for Overledger?
It depends on your setup. In Make, Overledger comes with 20 modules, 2 scheduled triggers and 18 actions, plus Make an API Call for anything else, and it is available from the Free plan. Many apps also have an n8n node, so check whether one exists for Overledger before deciding. There is no ranking to give here: the practical criterion is where your other automations already live and which tool your team knows. Keeping blockchain steps next to the scenarios that use their results is usually simpler to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations