Resources · Zapier integration

mintBlue Zapier integrationAutomate mintBlue with Zapier.

The mintBlue Zapier integration gives you 8 triggers, 3 actions and 0 searches. Seven triggers are instant event listeners on transactions and payments, one watches new projects, and the actions write data or payment transactions.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the mintBlue Zapier integration actually does

The mintBlue Zapier integration connects mintBlue, a service that links organizations to the blockchain, with the rest of your tools. Events on the mintBlue side can start a Zap, and other apps can ask mintBlue to write a transaction, with data, with a micropayment, or with both.

Three outcomes sum up the catalog. A payment log that fills itself: New Payment to Event Listener reports payments sent to an address you choose, and a spreadsheet step writes each one down. A record written on the chain from another tool: Create a Data Transaction, the action Zapier highlights, writes a transaction carrying data each time something happens elsewhere. A project feed: New Project spots each new mintBlue project so the right people hear about it.

Here is what Zapier does not do for mintBlue. There is no search step, so a Zap cannot look up an existing transaction or project before acting. The three actions only create transactions; nothing edits or removes one. And seven of the eight triggers revolve around an event listener you define in the trigger itself, with a name and, depending on the trigger, a Protocol id, a BitQuery or an address: what each one returns is best read at test.

If you are still choosing a tool for this kind of flow, see our n8n vs Zapier comparison, or our Zapier training.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every Zapier screen. Here they are in plain terms, once each.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. mintBlue offers eight.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you. mintBlue has three.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps what it has not seen. New Project works this way.
Instant trigger
A trigger the app reports itself, the moment the event happens, so nothing waits for a check. Seven mintBlue triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search step makes one, and it needs a paid plan.
Cost

What a mintBlue Zap really costs

mintBlue is not a premium app, so it works on the free plan. Zapier bills the actions your Zap completes, nothing else.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, unlimited two-step Zaps
  • BilledEach successful action, one task
  • Not billedTriggers, checks for new data, failed actions

A mintBlue trigger costs nothing, instant or not. Each action that succeeds costs one task, and a failed one is not counted: logging every incoming payment in a sheet is one task per payment. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, so a filter or a second action needs a paid plan. The interval grid below only applies to New Project, the one polling trigger; it does not apply to the seven instant triggers, which fire straight away on any plan.

Connect

Connect mintBlue to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an account on mintBlue, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick mintBlue

    Type mintBlue in the search box of the dialog, select it, then click Add connection. A new tab opens so you can sign in to the mintBlue account the Zap will work with.

  3. 03

    Sign in and grant access

    Sign in to mintBlue in that tab and grant Zapier access to the account. Every mintBlue step in every Zap then reuses this connection, so you set it up once.

First Zap

Your first mintBlue Zap

GoalEvery payment sent to one of your addresses lands as a new row in your spreadsheet, without anyone copying it.

  1. 01

    Pick the trigger

    Create a Zap, choose mintBlue, then New Payment to Event Listener. Give the listener a name in Event Listener Name and enter the address to watch in To Address.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the next step on a real payment, not a guess.

  3. 03

    Add the spreadsheet step

    Add a step, pick your spreadsheet app and its new-row action. Map each column to a value from the mintBlue step, so every payment fills its own row.

  4. 04

    Test the action

    Run the action once and read what came back before going further. Check that the test row landed in the sheet with each column where you expected.

  5. 05

    Publish

    Click Publish to switch the Zap on. Payments made before this point are not picked up; only the ones that arrive afterwards reach the sheet.

Triggers

mintBlue triggers on Zapier

8 events start a Zap when something happens in mintBlue, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Bitcom Event Listener

Instant trigger

In Zapier“Triggers a new Bitcom event listener creation.”

This trigger is built around a Bitcom event listener that you define inside the trigger: you give it a name and a Protocol id, and your Zap starts on the events tied to it. Pick it when you already know the Protocol id you want to follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the events you care about are tied to that Protocol id and each one should reach another tool.
Watch out
Event Listener Name and Protocol id are both required, so have the Protocol id ready before you open the editor.
2

New Bitquery Event Listener

Instant trigger

In Zapier“Triggers a new Bitquery event listener creation.”

Instead of a protocol, this listener rests on a BitQuery that you write when you set the trigger. Your Zap then starts on the events tied to that listener; what each one carries is best read at test.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when what should start the Zap is described by a BitQuery rather than by an address or a Protocol id.
Watch out
BitQuery and Event Listener Name are required; check at test that the query brings back what you expect before you publish.
3

New Transaction Created in Mintblue - Event Listener

Instant trigger

In Zapier“Triggers a new transaction created in mintblue event listener creation.”

Here the listener watches transactions created in mintBlue. Apart from a name for the listener, it asks for nothing else, which makes it the simplest of the event listeners to set up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when every new transaction on your account should leave a trace in another tool, a log or a team channel.
Watch out
a Zap that writes where its own trigger watches can set itself off; keep the trigger and the target of your Zap apart.
4

New Transaction Inserted Into Project - Event Listener

Instant trigger

In Zapier“Triggers a new transaction inserted into project event listener creation.”

This listener follows transactions inserted into a project. Use it when your mintBlue work is split into projects and only what lands in them matters, rather than every transaction on the account.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to tell the people in charge of a project each time a transaction is added to it.
Watch out
the only required field is Event Listener Name; read at test which project the events come from before you route them anywhere.
5

New Payment From Event Listener

Instant trigger

In Zapier“Triggers a new Payment From event listener creation.”

A listener on payments, named in the editor, that asks for a To Address when you set it. Your Zap starts on the payments this listener reports; read at test what each one carries.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when each payment tied to an address you manage should be recorded somewhere your accounting can see it.
Watch out
To Address is required even though the trigger is about payments from; check at test what the field changes in the results.
6

New Payment to Event Listener

Instant trigger

In Zapier“Triggers a new Payment To event listener creation.”

This listener is about payments sent to an address. You give it a name and the To Address to watch, and each payment reported for that address starts your Zap once.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to log incoming payments in a sheet, or to warn a colleague the moment money reaches a given address.
Watch out
To Address and Event Listener Name are both required, so keep the address at hand before you set the trigger.
7

New Minimum Payment Event Listener

Instant trigger

In Zapier“Triggers a new minimum payment event listener creation.”

Its name points to minimum payments, and Zapier says nothing more about what it covers. Like the two other payment listeners, it asks for a name and a To Address before it can be tested.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
only once a test has shown that what it reports matches the event your process waits for.
Watch out
the trigger name is all Zapier says about a minimum payment; read at test what the listener returns before you rely on it.
8

New Project

Polling trigger

In Zapier“Trigger when a new project is created.”

New Project starts your Zap each time a project is created in mintBlue. It needs no listener and no address: once connected, the trigger is ready to test.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to announce a new project to the team, or to open a matching entry in the tool where you plan work.
Watch out
it is the only polling trigger of the app, so on the free plan a project can wait up to 15 minutes before Zapier sees it.
Actions

mintBlue actions on Zapier

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

1

Create an Advanced Transaction

Action

In Zapier“Creates a transaction with data and micropayments”

The fullest of the three: one transaction that carries both data and micropayments, written by mintBlue when your Zap reaches the step.

When to use it
when a record and a payment belong to the same event and should not be split into two transactions.
Watch out
with data and payment in one step, test with small values first and read what mintBlue returns.
2

Create a Data Transaction

Action

In Zapier“Creates a transaction with data”

Writes a transaction that carries data only, with no payment attached. Zapier highlights it as the main mintBlue action.

When to use it
to leave a lasting trace of something that happened in another tool, a signed form or a closed record.
Watch out
map only the values you actually want written, and check at test how they come out in the transaction.
3

Create a Payment Transaction

Action

In Zapier“Creates a transaction with micropayment”

Sends a transaction carrying a micropayment, without the data part of the advanced version.

When to use it
when an event elsewhere, a validated step for instance, should trigger a small payment and nothing more.
Watch out
each successful run is one task and one payment; a filter before it keeps the step from running on every event, on a paid plan.
When it breaks

When a mintBlue Zap breaks

Zapier attaches no help article to mintBlue, and no limit specific to the app is documented. What breaks comes from the way Zapier itself works.

These four cases apply to every mintBlue Zap. When a run fails and you cannot see why, see our Zapier troubleshooting guide.

  • The past is not picked up

    A Zap only reacts to what happens after you switch it on. Payments, transactions and projects that already existed are never picked up; moving them is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again and burn through your tasks. Keep the trigger and the target apart.

  • A big batch held back

    After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection instead of running through.

  • The same project, once

    On a polling trigger like New Project, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help

Need help automating mintBlue with Zapier?

A person reads every message.

FAQ

mintBlue Zapier integration: questions

01Is the mintBlue Zapier integration free?
Yes, as long as each Zap stays at two steps. mintBlue is not a premium app, so it runs on the free plan, which gives 100 tasks a month and an unlimited number of Zaps. The free plan builds one trigger and one action per Zap. A payment listener followed by a spreadsheet row fits. Put a filter in between, or chain a second action such as a data transaction, and the Zap becomes a multi-step Zap that needs a paid plan.
02How many tasks does a mintBlue Zap use?
One task per action that succeeds, and nothing for the trigger. The seven event listeners and New Project never cost a task, and neither do Zapier's checks for new projects. A Zap that logs each incoming payment costs one task per payment. If an action fails, that run is not counted. A Zap that writes a data transaction and then a payment transaction costs two tasks each time. A few apps and actions use more than one task, so check at test what your Zap consumes.
03Do mintBlue triggers fire in real time?
Seven of the eight do. The event listeners, Bitcom, Bitquery, the two transaction listeners and the three payment listeners, are instant triggers: mintBlue tells Zapier when the event happens, whatever your plan, and the editor shows a lightning bolt on such a Zap. New Project is the exception. It is a polling trigger, checked every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The type comes from the app and cannot be changed in the editor.
04What does connecting mintBlue to Zapier require?
An account on mintBlue, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once: open Apps, click + Add connection, search mintBlue, sign in in the tab that opens and grant Zapier access. After that, every mintBlue step reuses it. For the event listeners, have the values they ask for ready: a Protocol id for Bitcom, a BitQuery for Bitquery, a To Address for the payment ones.
05Which mintBlue triggers ask for values before they work?
Seven of them, all the event listeners. Each one requires an Event Listener Name, and several ask for more: a Protocol id for New Bitcom Event Listener, a BitQuery for New Bitquery Event Listener, and a To Address for the three payment listeners, New Payment From, New Payment to and New Minimum Payment. Without those values, the trigger cannot be set. Gather them from your mintBlue account before you open the editor. New Project is the only trigger that asks for none, and the two transaction listeners only need the name.
06What if the mintBlue operation you want is not available?
Then this integration cannot do it today. The catalog holds eight triggers and three actions that create transactions, with no search step and nothing that edits or deletes. The mintBlue page on Zapier shows the current list, so check it before you plan around a missing event. If what you need starts in another tool, build the Zap from that tool and use one of the three transaction actions as the last step.
07Zapier, Make or n8n for mintBlue?
Decide by criteria rather than by brand. On Zapier, mintBlue brings seven instant listeners, which fire straight away even on the free plan, plus one polling trigger and three transaction actions. The criteria that matter: whether your flow starts on a listener or on New Project, how many steps each run needs, and how many runs you expect each month, since every successful action is a task. Weigh those against how the other tools bill and set up the same flow.
Same platform

Other docs you might need on this stack.

Browse all integrations