Resources · Make integration

Colligso WalletIn Make integrationAutomate Colligso WalletIn with Make.

Can Make send Colligso WalletIn passes for you? The Colligso WalletIn Make integration gives you a single action module, Send Pass. This guide shows how to link your account, where that module fits in a flow, and how to build your first scenario around it.

Try the Colligso WalletIn integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Colligso WalletIn Make integration do?

The Colligso WalletIn Make integration lets a Make scenario (the automation you build, a chain of modules) send a pass from your WalletIn account without you opening WalletIn. It has one module, Send Pass, which is an action: it acts on one item each time it runs, so it always follows something else in the flow.

A pass after a form is submitted. A form app starts the scenario when someone fills it in, and Send Pass follows with the details from that entry. The person gets their pass without anyone on your team copying data by hand.

A pass for each row of a list. Put a spreadsheet module first, let Make read the rows, and Send Pass runs once per row. Each row is a bundle, one item that flows to the next module, and each run of Send Pass counts as one operation on your plan.

A pass on a schedule. Without any trigger, you can still start the scenario from its clock: by default a new scenario runs every 15 minutes, and the Free plan cannot go below that interval.

What the integration does not do: WalletIn has no trigger, so Make cannot react to something that happens inside WalletIn, and there is no Make an API Call module to reach other WalletIn features. The official doc also warns that its own text is AI-generated and asks you to confirm details with Colligso WalletIn. If you are still choosing a platform, read our Make review and the n8n vs Make comparison; the Make pricing page explains how operations are billed.

Connect

How do you connect Colligso WalletIn to Make?

  1. 01

    Check the prerequisites and create a key

    You need a Clover developer account with access to a test or production merchant account, plus a WalletIn account. In WalletIn, open Business, then API Keys, click New, name the key, give it a validity period in days and pick the scope post_activities.

  2. 02

    Save and copy the key

    Click Save and copy the API key shown on screen right away. Keep it somewhere safe until Make asks for it, because this key is what proves to WalletIn that the scenario is allowed to act on your account.

  3. 03

    Create the connection in Make

    In your scenario, add the Send Pass module and click Create a connection. A connection is your WalletIn account linked to Make once and reused later. Optionally fill Connection name, paste the key, then follow the on-screen instructions.

First scenario

Build your first scenario with Colligso WalletIn

GoalWhen new data arrives in another app, Make sends a pass through Colligso WalletIn.

  1. 01

    Start a new scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Since WalletIn has no trigger, pick the app that holds your source data, such as a form or a sheet.

  2. 02

    Set up the source module

    Create the connection for that app and fill its fields. Once connected, Make lists the forms, sheets or objects it can read, so you choose from a menu instead of typing names.

  3. 03

    Add Send Pass

    Click the + on the right of the first module, search for Colligso WalletIn and pick Send Pass. Select your connection, then map the values coming from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check that the pass went out as expected.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From there Make runs it for you at that interval.

Modules

What the Colligso WalletIn module does

Colligso WalletIn gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Colligso WalletIn1

Send Pass

ActionIn the docs only

Send Pass delivers a pass from your WalletIn account the moment the scenario reaches it, so the step your team did by hand now happens on its own after an upstream event.

When to use it
as the last module of a flow, after a form, a sheet or another app has produced the person and details the pass needs.
Watch out
the doc gives no description of its fields, so read the form Make shows once connected, and test with Run once before switching on.
Need help

Need help automating Colligso WalletIn with Make?

A person reads every message.

FAQ

Colligso WalletIn and Make: frequent questions

01Is the Colligso WalletIn Make integration free?
Yes, on the Make side. Colligso WalletIn is a standard app, so its module works on the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) bring a 1 minute interval and unlimited active scenarios, with usage counted in credits per month. Your WalletIn subscription is separate: check the Colligso WalletIn pricing page, since the Make doc points there and gives no price.
02What do you need to connect Colligso WalletIn to Make?
You need a Clover developer account with access to a test or production merchant account, and an account on Colligso WalletIn. Inside WalletIn you create an API key from Business, then API Keys, with a name, a validity period in days and the post_activities scope. In Make you click Create a connection on the Send Pass module, optionally name the connection, and paste that key. The same connection is then reused by any later scenario that sends passes.
03Does the Colligso WalletIn Make integration react in real time?
No, because the app has no trigger module at all. Something else has to start the scenario. You can open the flow with an instant trigger from another app, which that app fires through a webhook as soon as an event happens, and Send Pass follows it. Or you can rely on the scenario clock alone: a new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute.
04What if the Colligso WalletIn module you need is missing?
It depends on what you need. Send Pass is the only module, and the app has no Make an API Call module, so Make cannot reach other WalletIn features directly. If the gap is about reading data or reacting to events, handle that part with another app in the same scenario and keep Send Pass for the delivery step. The doc also warns its content is AI-generated, so confirm anything critical with Colligso WalletIn. For a custom build, the team can help.
05Should you use Make or n8n for Colligso WalletIn?
It depends on the tool your workflows already live in. On Make, Colligso WalletIn is a standard app with one action, Send Pass, available from the Free plan, connected with an API key from your WalletIn account. The same app often has an n8n node as well, so check what exists there before deciding. Pick the platform where your other apps and scenarios are already set up, since Send Pass always needs another module to start the flow.
Same platform

Other docs you might need on this stack.

Browse all integrations