Resources · Zapier integration

Layer4 Zapier integrationAutomate Layer4 with Zapier.

Layer4 Zapier integration: 0 triggers, 4 actions and 7 searches. Layer4 never starts a Zap by itself, so another app fires first. Then Layer4 writes a record, creates or updates a token, or reads a balance on the blockchain for you.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Layer4 Zapier integration actually does

The Layer4 Zapier integration lets an event in one of your other apps write to the blockchain through Layer4, without opening Layer4 at all. Layer4 is a platform that makes blockchain work less painful; Zapier is the glue. Since Layer4 has no trigger, it always sits after another app in the chain, as an action or as a lookup.

Three outcomes come up again and again. First, a stored proof: Create Record saves a piece of data in one of your buckets (a bucket is the container you set up inside Layer4), and it can even store the fingerprint of a file instead of the file. Second, a token you control from elsewhere: Create Token, Increase Token Supply and Update a Token cover the life of a token without a manual step. Third, a value the next step can use: the seven searches read balances, supply, metadata and records so a later action works with fresh numbers.

Now the part the app listing keeps quiet. Zapier cannot react to anything that happens inside Layer4: there is no trigger, so a new record or a moved balance will never start a Zap. Nothing deletes a record or a token either; the list stops at create, increase, update and find. And the searches only look inside one bucket at a time, because every one of them asks for a Bucket ID.

If you are still weighing the tool itself, our Zapier review and the n8n vs Zapier comparison are the next reads.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the rest of the page. Each one is explained here once, then used as is.

Zap
The automation you build: one trigger, then one or more actions that run every single time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it. Layer4 offers none.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like creating a Layer4 record.
Task
The unit Zapier bills. One task equals one action your Zap completes successfully; your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and quietly stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can use what it found, like a token's supply.
Connection
Your Layer4 account linked to Zapier once, then reused by every step of every Zap that touches Layer4.
Cost

What a Layer4 Zap really costs

Layer4 is not a premium app, so it works from the free plan. The bill is counted in tasks, and only finished actions count.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Searches and filtersMake the Zap multi-step: paid plan

The trigger never costs a task, and neither does Zapier checking for new data, however often it looks. Each Layer4 action that succeeds counts once; an action that fails is not billed. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps: one trigger, one action. Add a Layer4 search before your action, or a filter, and the Zap becomes multi-step (more than one trigger and one action), which needs a paid plan. A few apps and actions take more than one task, so keep an eye on the counter. How fast the Zap starts depends on the other app's trigger, not on Layer4.

Connect

Connect Layer4 to Zapier in three steps

  1. 01

    Open the Apps page

    From your Zapier account, go to Apps and click + Add connection. You need a Layer4 account first, and access to any bucket you did not create yourself but want the Zap to write into.

  2. 02

    Pick Layer4

    Type Layer4 in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Layer4 side, where the actual sign-in happens.

  3. 03

    Sign in and allow access

    Log in to Layer4 in that tab and grant Zapier access to the account. The connection then shows up in your list, and every Layer4 step of every Zap can reuse it without asking again.

First Zap

Your first Layer4 Zap, step by step

GoalRaise a token's supply when something happens in another app, after reading how much of it exists.

  1. 01

    Create the Zap and pick its start

    Create a new Zap and choose the app and the event that should start it. Layer4 has no trigger, so the first step always belongs to another tool you already use.

  2. 02

    Test the trigger

    Run the trigger test. Zapier pulls the three most recent items from that connected account, so you map fields on a real one instead of a made-up example.

  3. 03

    Add Find Token Supply

    Add a step, open the Action event list and pick Find Token Supply under SEARCH. Fill in the Bucket ID and the Token ID you want to watch.

  4. 04

    Add Increase Token Supply

    Add Layer4 again with Increase Token Supply. Reuse the same Bucket ID and Token ID, then set the Amount, which has to be at least 1.

  5. 05

    Test, then publish

    Test each step and read what came back before moving on. When the numbers look right, click Publish to switch the Zap on. With a search inside, this Zap needs a paid plan.

Actions

Layer4 actions in Zapier

Layer4 gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Record

Action

In Zapier“Creates a new record to store data on the blockchain.”

Writes a new record into one of your buckets, so the data ends up stored on the blockchain. You can also store a file's fingerprint with {{fileHash}} rather than the file.

When to use it
a document arrives in another app and you want a lasting proof that it existed in that exact form.
Watch out
when Content Type announces structured data, the Data field must follow that structure exactly, or the step fails.
2

Create Token

Action

In Zapier“Creates a new token for a bucket.”

Mints a fresh token inside a bucket, with the quantity you set in Supply. For a one-of-a-kind token, Supply is 1 and metadata goes with it.

When to use it
each new item in another tool should become its own token without anyone opening Layer4.
Watch out
very large quantities belong in Supply as text rather than as a number.
3

Increase Token Supply

Action

In Zapier“Increase the supply of a token.”

Adds units to a token that already exists, identified by its Bucket ID and Token ID. The Amount you give is added on top of the current supply.

When to use it
an event elsewhere means more of the same token should exist, and the count must follow on its own.
Watch out
Amount must be at least 1, and both IDs have to point to a token that already exists.
4

Update a Token

Action

In Zapier“Update a token for a bucket.”

Changes an existing token in a bucket, picked by its Token ID, without creating a new one. The token keeps its identity, only what you send gets modified.

When to use it
details kept in another app change and the token on Layer4 should stay in step.
Watch out
the Token ID is mandatory, so a search step often has to find it first.
Searches

Layer4 searches in Zapier

7 search steps look for data that already exists in Layer4, so a later step can use it.

Layer4 searches sit at the bottom of the Action event list, under SEARCH. Each one reads inside a single bucket and passes what it found to the next steps. Some action fields also show + Add search step, which inserts the lookup for you. Whether a search wants an exact value or a close one is up to Layer4, not Zapier. Three settings decide what happens when the result is not the one you expected.

1

Find Token Balance for Address

Search

In Zapier“Find the balance of a token for a given address.”

Tells you how many units of a given token one wallet holds, using the wallet's public address on the chain.

When to use it
a later step should only run, or should change its numbers, depending on what that wallet already owns.
Watch out
it needs three things at once: the Bucket ID, the Token ID and the Address.
2

Find Records

Search

In Zapier“Find all records for a given bucket.”

Brings back every record stored in one bucket in a single pass, rather than one specific entry.

When to use it
the next step needs the whole set of what a bucket holds, for instance to pass it all along together.
Watch out
pair it with the multiple-results setting, otherwise only the first record travels down the Zap.
3

Find Tokens

Search

In Zapier“Find all tokens associated with a given bucket.”

Lists all the tokens linked to a bucket, with only the Bucket ID to fill in.

When to use it
you do not know which Token ID to work on yet and want the full list of what the bucket contains before acting.
Watch out
like Find Records, it hands over only the first match unless you change the multiple-results setting.
4

Find Record

SearchFind or create

In Zapier“Find a single record for a bucket”

Fetches one precise record from a bucket by its Record ID. The editor also shows Find or Create a Record: that is this same search with the create box ticked, not a separate operation.

When to use it
a step needs the content of a record you already wrote.
Watch out
with find-or-create on, a missing record gets written in your bucket instead of the Zap stopping.
5

Find Token

SearchFind or create

In Zapier“Find a single token for a bucket.”

Reads one token from a bucket, given its Token ID. Find or Create a Token in the list is the same lookup with the create option ticked, so it is not one more operation.

When to use it
before Update a Token, to check the token is there.
Watch out
the create variant then asks for what Create Token needs, Supply included.
6

Find Token Metadata

Search

In Zapier“Find the metadata for token.”

Returns the descriptive details attached to a token, the metadata, rather than its quantity or its owners.

When to use it
a message or a document in another app should quote the token's own description, pulled live.
Watch out
a token created without metadata has little to give back, so test on a token that really has some.
7

Find Token Supply

Search

In Zapier“Find the supply of a token.”

Gives the quantity of a token that currently exists on the blockchain, read from its bucket and Token ID.

When to use it
just before Increase Token Supply, or before a filter, so the Zap decides with the current figure.
Watch out
it needs both the Bucket ID and the Token ID, so carry them from an earlier step or type them in.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips the steps that relied on it. Turned on, the Zap carries on with nothing in hand.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into find-or-create: the setting above disappears and Zapier asks for the fields it needs to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on together.
When it breaks

When a Layer4 Zap breaks

Zapier links no help article to Layer4 and no limit specific to the app is documented. What breaks is what breaks on any Zap.

Four situations account for most surprises. None of them shows up as a red error on day one, which is exactly why they are worth knowing before you publish. For anything deeper, our Zapier troubleshooting page is the place to start.

  • The past is never picked up

    A Zap only reacts to what happens after you switch it on. Items that existed before are ignored, so moving older data into Layer4 is a separate job.

  • A Zap that sets itself off

    If a Zap writes into the very place its own trigger watches, it fires again and again and burns through your task count fast.

  • A big batch gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can pause it instead of running everything.

  • The same item never runs twice

    On a polling trigger, Zapier remembers what it has already seen. The same item never starts the Zap twice.
Need help

Need help automating Layer4 with Zapier?

A person reads every message.

FAQ

Layer4 Zapier integration: common questions

01Is the Layer4 Zapier integration free?
Yes, as long as the Zap stays simple. Layer4 is not a premium app, so it runs on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the size of each Zap: the free plan allows two steps, one trigger and one action. A Zap that reads a token with a Layer4 search before writing, or that uses a filter, becomes multi-step and needs a paid plan. Since Layer4 has no trigger, the first step always comes from another app, which leaves room for exactly one Layer4 action on the free plan.
02How many tasks does a Layer4 Zap use?
One task per Layer4 action that succeeds. The trigger from the other app costs nothing, and Zapier checking for new data costs nothing either, however often it runs. In a Zap with several actions, each successful one is counted on its own, so a Zap that creates a record and then updates a token uses two tasks per run. An action that fails is not billed. A few apps and actions take more than one task when they complete, so the task counter in your account is the figure to watch.
03Is Layer4 on Zapier real time?
It depends entirely on the app that starts the Zap, because Layer4 has no trigger of its own. If that app offers an instant trigger, it alerts Zapier as soon as the event happens and the Layer4 step follows straight away, whatever the plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. A lightning bolt in the editor marks an instant trigger.
04What is needed to connect Layer4 to Zapier?
A Layer4 account, then a few clicks. In Zapier, open Apps, click + Add connection, search for Layer4, click Add connection, sign in on the tab that opens and grant access. If the Zap must write into a bucket someone else created, you also need access to that bucket. In practice, the real prerequisite is a bucket: every Layer4 action and search asks for its Bucket ID, which you copy from the bucket dashboard inside the Layer4 app.
05Why does a Layer4 step keep asking for a Token ID?
Because every token operation targets one exact token, and only the Token ID tells Layer4 which one. Increase Token Supply, Update a Token, Find Token, Find Token Metadata, Find Token Supply and Find Token Balance for Address all require it, along with the Bucket ID. When the other app does not carry that ID, put Find Tokens or Find Token before the action so the value arrives on its own. Bear in mind that this search turns the Zap into a multi-step one, which needs a paid plan.
06What if the Layer4 operation you need is not listed?
Then Zapier cannot do it with Layer4 today. The integration stops at four actions (Create Record, Create Token, Increase Token Supply, Update a Token) and seven searches. There is no trigger, so nothing inside Layer4 can start a Zap, and no operation deletes a record or a token. Those steps stay manual in Layer4. Before building around a gap, check the action list in the editor, since an app can add operations over time.
07Zapier, Make or n8n for Layer4?
Decide on three criteria rather than on a ranking. First, coverage: on Zapier, Layer4 offers four actions and seven searches but no trigger, so check what the other tool lists for Layer4 before switching. Second, cost model: Zapier bills each successful action as a task, and searches push you to a paid plan. Third, the shape of the Zap: on Zapier's free plan, a Layer4 Zap stays at one trigger from another app and one Layer4 action.
Same platform

Other docs you might need on this stack.

Browse all integrations