Resources · Zapier integration

Colligso WalletIn Zapier integrationAutomate Colligso WalletIn with Zapier.

The Colligso WalletIn Zapier integration gives you 0 triggers, 1 action and 0 searches. That single action, Send Pass, sends a customer a pass to save in their Apple Pay or Google Pay wallet, each time an event in another app starts it.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Colligso WalletIn Zapier integration actually does

Colligso WalletIn lets a merchant reach customers again through a pass stored in their Apple Pay or Google Pay wallet. Connected to Zapier, it does one thing: when something happens in another app, it sends that pass to a person, by email address and first name, under one of your Colligso sites.

Three results you can get from that one action, Send Pass.

A pass for every new sign-up. Someone fills in a form, and the Zap sends them a pass to save to their phone. No export, no copy and paste.

A pass after a purchase. A store or checkout tool starts the Zap, Send Pass follows, and the buyer leaves with something to remarket to later.

A pass per site. If you run several Colligso sites, each Zap points at the right one through the required Site field, so each customer is tied to the shop they actually dealt with.

Now the part the app page skips. Colligso WalletIn has no trigger on Zapier, so it can never start a Zap by itself. It cannot tell Zapier that a pass was saved or opened. It has no search either, so a Zap cannot look up a customer already in Colligso. Everything starts somewhere else and ends with a pass going out.

The same app also has a Make page: Colligso WalletIn Make integration. If you are still choosing a tool, Zapier review is the place to start.

Vocabulary

Zapier vocabulary in one minute

Eight words, used across the page without a second explanation.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it. Colligso WalletIn has none.
Action
What the Zap does once started: the step that writes, sends or moves something for you. Here, Send Pass.
Task
The unit Zapier bills. One task is one action that completed successfully; your plan's allowance counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment it happens.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
Connection
Your Colligso WalletIn account, linked to Zapier once and then reused by every step that talks to that app.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search turns it into one, and it needs a paid plan.
Cost

What a pass costs you in tasks

Short version: one pass sent is one task.

  • Send Pass1 task per successful send
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo

The trigger in the other app never costs anything, however often Zapier checks it. Send Pass counts one task each time it succeeds, and a send that fails is not billed. Colligso WalletIn is not a premium app, so it works on the free plan: 100 tasks a month, unlimited Zaps, and polling triggers checked every 15 minutes. The catch is that the free plan stops at two steps. Add a filter to send passes only to some people and the Zap becomes multi-step, which means a paid plan.

Connect

Connect Colligso WalletIn to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. Type Colligso WalletIn and pick it from the results.

  2. 02

    Sign in to Colligso

    Click Add connection. A new tab asks you to sign in to your Colligso account. You need an account on the app first, plus access to the sites you want the Zap to send passes for.

  3. 03

    Grant access

    Let Zapier use the account. The connection is saved once and offered again in every Zap that uses Colligso WalletIn, so you will not repeat this step for each new automation.

First Zap

Your first Zap: a wallet pass for each paid booking

GoalA yoga studio sends a pass to every client who books a paid class through a form.

  1. 01

    Build the trigger

    Create a Zap and pick Typeform with its new-entry event as the starting point. Colligso WalletIn cannot start a Zap, so the first step always belongs to another app.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent entries from the connected account, so you can map from a real booking and spot the answer that marks a paid class.

  3. 03

    Add a filter

    Add a Filter step and set the three boxes: the answer you spotted in the test, a text rule, and the value for a paid class. A text rule only works on text.

  4. 04

    Add Send Pass

    Add the Colligso WalletIn action Send Pass. Pick the studio's Site, then map the email and first name from the form answers. All three fields are required.

  5. 05

    Test and publish

    Test the action once and check that the pass reached the test address. Then click Publish. The filter makes this a multi-step Zap, so it runs on a paid plan.

Actions

The Colligso WalletIn action on Zapier

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

1

Send Pass

Action

In Zapier“Send pass to customer to download in his/her mobile wallet”

Sends a customer a pass they can download straight into the wallet on their phone, tied to one of your Colligso sites.

When to use it
right after a sign-up, a purchase or a booking lands in another app, so the customer leaves with a pass you can remarket to.
Watch out
Site, Email and First Name are all required, so a form that lets people skip their first name will make this step fail.
When it breaks

When the Zap breaks

Zapier links no help article to Colligso WalletIn, so the limits below are the ones every Zap shares.

None of them is exotic. They show up in the first week, mostly when a list is imported in one go or when a required value is missing. For deeper cases, Zapier troubleshooting covers the general method.

  • Old customers get nothing

    A Zap only reacts to what happens after you publish it. Contacts that were already in your form tool or store never receive a pass; moving that backlog is a separate job.

  • A bulk import gets held back

    If the trigger app suddenly returns a huge batch after an import or a migration, Zapier's flood protection can hold those items back instead of sending a pass for each one.

  • A missing first name stops the step

    Send Pass requires Site, Email and First Name. When the trigger app sends an empty value for one of them, the action cannot complete, and a failed action is not billed.

  • No duplicate passes from polling

    On a polling trigger, Zapier remembers what it already saw, so the same entry does not start the Zap twice. Two separate entries from one person still mean two passes.
Need help

Need help automating Colligso WalletIn with Zapier?

A person reads every message.

FAQ

Colligso WalletIn Zapier integration: questions

01Is the Colligso WalletIn Zapier integration free?
Yes, it works on the free Zapier plan, because Colligso WalletIn is not a premium app. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. A Zap made of a form trigger plus Send Pass fits. As soon as you add a filter, a second action or a search, the Zap turns multi-step and needs a paid plan. Your Colligso subscription is a separate matter that this page does not cover.
02How many Zapier tasks does sending a pass use?
One task for each pass that goes out successfully. The trigger step in the other app costs nothing, and neither does Zapier checking that app for new data, however often it looks. A Send Pass step that fails is not counted against your plan. If you add more actions after Send Pass, each one that succeeds is billed on its own, so a Zap with three actions uses three times the tasks of a Zap with one. On the free plan, that means up to 100 passes a month.
03Does Colligso WalletIn send passes in real time?
It depends on the app that starts the Zap, since Colligso WalletIn has no trigger of its own. If that app has an instant trigger, it reports the event to Zapier straight away and the pass follows without waiting, whatever your plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. The editor shows a lightning bolt on Zaps built on an instant trigger, which is the quickest way to check.
04What is required to connect Colligso WalletIn to Zapier?
A Colligso account, and access to the sites the Zap should send passes for. In Zapier, open Apps, click + Add connection, find Colligso WalletIn, click Add connection, sign in to Colligso in the new tab and grant access. That connection is then reused by every Zap. Before building, check that your sites appear under Business, then Sites, in Colligso: the Site field of Send Pass is required and lists those sites.
05Why does Send Pass fail on some entries and not others?
Usually because one of the three required fields arrived empty. Send Pass needs a Site, the customer's email address and their first name, every time. If the form or store starting the Zap lets someone leave the first name blank, that run stops at the action. The fix sits upstream: make the field mandatory in the source app, or add a filter that lets the Zap continue only when the value is present. That filter makes the Zap multi-step, so it needs a paid plan.
06What if the Colligso WalletIn action required is not on Zapier?
Then Zapier cannot do it with this app today. The integration offers exactly one action, Send Pass, with no trigger and no search: no reacting to a pass being saved, no looking up an existing customer, no updates. Anything beyond sending a pass stays outside this integration. If the gap blocks a real process, comparing tools is the next step, and a team that builds automations every day can tell you quickly whether a workaround exists elsewhere.
07Zapier, Make or n8n for Colligso WalletIn?
Judge on the operations each tool exposes, not on a ranking. On Zapier, Colligso WalletIn gives one action, Send Pass, and no trigger, so the question is whether that one move covers your need. Check what each other tool offers for this app before deciding. Then weigh cost: on Zapier, every pass sent is a task, and the free plan allows 100 a month with two-step Zaps only. Finally, look at what starts the flow, because the app that triggers the Zap decides how fast the pass goes out.
Same platform

Other docs you might need on this stack.

Browse all integrations