Resources · Make integration

1Shot API Make integrationAutomate 1Shot API with Make.

Can a blockchain transaction start from a spreadsheet row, with no code at all? The 1Shot API Make integration gives you 18 modules: one instant trigger, 12 actions and 5 searches. This guide connects your account and walks you through a first working scenario.

Try the 1Shot API integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the 1Shot API Make integration let you automate?

The 1Shot API Make integration links your 1Shot API account to Make, a visual tool where you chain apps into a scenario (the automation you build). Each 1Shot API step is a module: it can run or read a Contract Method, manage a Wallet, look up Transactions, or start the scenario when a Transaction ends.

Transactions launched from business data. A row lands in a sheet or a form is submitted in another app, and Execute a Contract Method turns it into a Transaction on 1Shot API. Put Simulate a Contract Method in front when you want to see the returned value or the error before anything is sent for real.

A clear signal when a Transaction ends. Watch Transaction Webhook fires as soon as a Transaction is completed or failed, so a support or finance team hears about a failure without refreshing a dashboard.

Wallet balances where people look. List Wallets returns each Wallet with its balance, which you can copy into a sheet or a chat message and use to spot the ones that need funds.

The directory lists no documented limits for this app, and there is no dedicated doc page yet. When a listed module does not cover an endpoint, Make an API Call reaches it with the same connection. 1Shot API also has an n8n node, covered on the 1Shot API n8n integration page, and n8n vs Make sets the two tools side by side. New to the editor? The Make training starts from zero.

Connect

How do you connect 1Shot API to Make?

  1. 01

    Add a 1Shot API module

    In your scenario, click the +, search for 1Shot API and pick any of its modules. The module opens with an empty connection field and a Create a connection button next to it.

  2. 02

    Name the connection

    Click Create a connection. Giving it a name is optional, yet a clear label such as the account or the environment helps later, because every 1Shot API module in Make reuses this same connection.

  3. 03

    Authorize and save

    Follow the prompt: either approve Make on the 1Shot API page that opens, or paste the key your 1Shot API account gives you. Then click Save. The module can now list the Wallets and Contract Methods it is allowed to read.

First scenario

Your first scenario with 1Shot API

GoalWhen a new request lands in another app, Make runs a 1Shot API Contract Method and creates the matching Transaction.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your requests arrive, such as a sheet or a form tool, and its trigger module.

  2. 02

    Add Execute a Contract Method

    Click the + on the right of that first module, search for 1Shot API and choose Execute a Contract Method. Create the connection when Make asks for it.

  3. 03

    Pick the method and map the data

    Once connected, Make lists the Contract Methods it can read. Choose yours, then map each value from the bundle (one item passed from the previous module) instead of typing it by hand.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can confirm that a Transaction was created with the right values.

  5. 05

    Schedule and switch on

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

Triggers

What starts a 1Shot API scenario

1 module starts a scenario when something happens in 1Shot API. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by 1Shot API as soon as it happens.

1Shot API1Watch Transaction Webhook

Watch Transaction Webhook

Instant trigger

In Make“Triggers when a Transaction is completed or failed.”

Your scenario starts the moment a 1Shot API Transaction reaches its end, whether it completed or failed, so the next steps work on a known outcome instead of a pending one.

How it fires
instant: the app calls Make through a webhook as soon as it happens. That is why the module carries the lightning badge rather than the clock.
When to use it
after a scenario that executes Contract Methods, to post the result to the team, update the record that asked for the Transaction, or open a ticket when something failed.
Watch out
both outcomes arrive through the same trigger, so read the status in the bundle before sending a success message.
Modules

Everything 1Shot API can do in Make

1Shot API gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

1Shot API1

Assure Contract Methods from Prompt

Action

In Make“Assures that Contract Methods are available based on a chosen 1Shot Prompt.”

Makes sure the Contract Methods described by a chosen 1Shot Prompt are available to your account, so the modules that follow have methods to call.

When to use it
right after Search for Prompts has found the Prompt that fits your need, before any Read or Execute step.
Watch out
this step prepares methods; the Transaction itself only comes from Execute a Contract Method.
1Shot API2

Create a Wallet

Action

In Make“Creates a new Wallet. You still need to deposit funds though!”

Gives you a brand new Wallet in 1Shot API straight from a scenario, handy when each new client or project should get its own.

When to use it
when a customer record is created in your CRM and needs a dedicated Wallet.
Watch out
the new Wallet starts empty. You still have to deposit funds before it can pay for anything.
1Shot API3

Delete a Wallet

Action

In Make“Deletes a Wallet. May only be done if the Wallet is empty!”

Removes a Wallet you no longer need, which keeps your account list short and your balance reports readable.

When to use it
when a project is closed and its Wallet has been drained.
Watch out
the deletion only goes through if the Wallet is empty, and it cannot be undone once it succeeds. Run Get a Wallet first to check the balance.
1Shot API4

Estimate Gas for a Contract Method

Action

In Make“Get a gas cost estimate for executing a Contract Method.”

Tells you what executing a Contract Method should cost in gas before you commit, so a scenario can decide with a number in hand.

When to use it
ahead of Execute a Contract Method, when you want to log the expected cost or compare it with the balance returned by Get a Wallet.
Watch out
it is an estimate, not a charge, so treat it as a guide.
1Shot API5

Execute a Contract Method

Action

In Make“Execute a Contract Method and create a Transaction.”

Runs a Contract Method for real and creates a Transaction in 1Shot API, which is the step that actually changes something on chain.

When to use it
when an approved request, a paid order or a signed agreement in another app should lead to an on-chain action.
Watch out
the Transaction is not finished when this module returns; pair it with Watch Transaction Webhook or Get a Transaction to learn the outcome.
1Shot API6

Get a Contract Method

Action

In Make“Gets a specific Contract Method.”

Brings back the details of one specific Contract Method, useful to show or store exactly what a scenario is about to call.

When to use it
when List Contract Methods has pointed you to a method and you need its full record for a log or an approval message.
Watch out
it reads the method only and never runs it.
1Shot API7

Get a Transaction

Action

In Make“Get a specific Transaction. Useful for polling to see if a Transaction has completed or failed.”

Returns one specific Transaction, so you can see whether it has completed or failed and pass that status along.

When to use it
when you prefer to check on a Transaction yourself, for example in a scenario that looks up pending ones, rather than wait for the webhook.
Watch out
each check costs an operation, so the instant trigger is usually the lighter route.
1Shot API8

Get a Wallet

Action

In Make“Gets an individual Wallet and its balance.”

Fetches a single Wallet together with its balance, the quickest way to know whether it can cover what comes next.

When to use it
before Execute a Contract Method or Delete a Wallet, to stop the flow if the balance is not what you expect.
Watch out
you need the Wallet reference; map it from List Wallets rather than retyping it.
1Shot API9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the 1Shot API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
when none of the other ready-made modules matches the request you need to send.
Watch out
you build the request yourself, so keep the 1Shot API reference open while you fill it in.
1Shot API10

Read a Contract Method

Action

In Make“Execute a Contract Method to read from the blockchain and get the value back.”

Runs a Contract Method in read mode and hands you the value it finds on the blockchain, without creating a Transaction.

When to use it
to pull a current value into a report, a sheet or a condition later in the scenario.
Watch out
pick a method meant for reading; methods that change state belong in Execute a Contract Method.
1Shot API11

Simulate a Contract Method

Action

In Make“Simulates the execution of a Contract Method, returning the value or an error.”

Shows you what a Contract Method would return, or the error it would raise, without sending anything for real.

When to use it
while building a scenario, or right before Execute a Contract Method when a failed Transaction would be costly to clean up.
Watch out
a clean simulation is a strong hint, not a promise that the real run will succeed.
1Shot API12

Update a Wallet

Action

In Make“Updates an existing Wallet.”

Changes an existing Wallet without leaving the scenario, so it stays in step with the client or project it serves.

When to use it
a record is renamed or reassigned in your CRM, and the Wallet should follow.
Watch out
target the Wallet by the reference returned by List Wallets or Get a Wallet so you never edit the wrong one.
1Shot API13

List Chains

Search

In Make“Lists chains supported by 1Shot API.”

Returns the chains that 1Shot API supports, one bundle per chain, so you can pick from a real list instead of guessing.

When to use it
when setting up a scenario that must pick the right chain, or to feed a dropdown in a form.
Watch out
as a search, it can hand back several bundles, and each following module then runs once per chain.
1Shot API14

List Contract Methods

Search

In Make“Lists available Contract Methods from 1Shot API.”

Gives you the Contract Methods available in your 1Shot API account, handy to see what a scenario can call.

When to use it
when you need to find a method before Get, Read, Simulate or Execute, or to keep a catalog of methods in a sheet.
Watch out
each method comes out as its own bundle, so later modules run once per method unless you narrow the search.
1Shot API15

List Transactions

Search

In Make“Get a list of executed Transactions from 1Shot API”

Pulls the Transactions already executed through 1Shot API, a solid base for a ledger or an activity report.

When to use it
when accounting or operations wants every executed Transaction copied into a sheet or a database.
Watch out
every Transaction becomes a bundle and every following module spends an operation on each one, so narrow the results before adding heavy steps.
1Shot API16

List Wallets

Search

In Make“Lists Wallets with their balances.”

Returns your Wallets with their balances in one pass, the simplest way to watch funds across projects.

When to use it
when a finance lead wants the balances posted to a chat channel or written to a sheet.
Watch out
one bundle per Wallet means one operation per Wallet in every module that follows.
1Shot API17

Search for Prompts

Search

In Make“Perform a semantic search for 1Shot Prompts.”

Finds 1Shot Prompts by meaning rather than exact words, so a plain description of your need is enough to surface the right one.

When to use it
as the first step before Assure Contract Methods from Prompt, when you know what you want to do but not which Prompt covers it.
Watch out
a semantic search can return several close matches; check which one you map.
Need help

Need help automating 1Shot API with Make?

A person reads every message.

FAQ

Questions about the 1Shot API Make integration

01Is the 1Shot API Make integration free?
Yes, 1Shot API is a standard app in Make, so you can use it on the Free plan. That plan comes with limits worth knowing: 2 active scenarios, at least 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month.
02What do you need to connect 1Shot API to Make?
You need a 1Shot API account and a Make account. The directory lists no extra prerequisite. Add any 1Shot API module, click Create a connection, give it a name if you like, then either authorize Make on the 1Shot API page or paste the key your account provides, and click Save. That single connection is reused by every 1Shot API module in all your scenarios, so you only set it up once per account.
03Does the 1Shot API trigger fire in real time?
Yes. Watch Transaction Webhook is an instant trigger: 1Shot API calls Make through a webhook as soon as a Transaction is completed or failed, and the scenario starts right away. You can spot it in the editor by the lightning badge on the module. It is the only trigger of the app, so if you need to react to anything else, such as a new Wallet, a scheduled scenario that runs List Wallets or List Transactions is the way to go.
04What if a 1Shot API module is missing in Make?
Use Make an API Call. It calls any endpoint of the 1Shot API with the connection you already have, so you are not limited to the ready-made modules. You write the request yourself, which is why it helps to have the 1Shot API reference open while you fill it in. The Make directory lists no documented limits for this app, so there is no published cap to plan around from the Make side.
05Make or n8n: which one fits 1Shot API?
It depends on where your other automations already live. In Make, 1Shot API offers 18 modules, including an instant trigger for finished Transactions and Make an API Call for anything not covered. 1Shot API also has an n8n node, described on its own page on this site. Neither choice is better by default: pick the tool your team already builds in, and compare the modules each one offers for the exact steps you need.
Same platform

Other docs you might need on this stack.

Browse all integrations