- Home
- Resources
- Integrations
- Colligso TextIn
Colligso TextIn Zapier integrationAutomate Colligso TextIn with Zapier.
The Colligso TextIn Zapier integration gives you 3 actions, 0 triggers and 0 searches. Another app starts the work, then Zapier records an SMS opt-in, imports a customer or sends a text in Colligso TextIn. It runs on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Colligso TextIn Zapier integration actually does
Connecting Colligso TextIn to Zapier lets your other tools feed your SMS list without anyone retyping a phone number. Zapier (a service that links apps together) waits for something to happen elsewhere, then writes into Colligso TextIn for you. It can only write here: the app offers actions, nothing that watches it.
Three outcomes come up again and again. A logged opt-in: a checkout or signup elsewhere passes a mobile number to Get Permission, and the person lands on your text-marketing list with their consent recorded. A customer ready for a campaign: Create Customer copies a contact from your shop, CRM or spreadsheet into the right Colligso site, so your first permission campaign has someone to reach. A text that goes out on its own: Send Message fires one SMS the moment the upstream event happens (a booking, a paid invoice, a ticket closed).
Now the part the app page skips. Zapier cannot read anything out of Colligso TextIn. No reply, no new opt-out, no campaign result will ever start a Zap from this side, and there is no step to look up a customer who already exists. If your plan depends on reacting to an incoming text, this integration will not get you there.
Before building, the Zapier review gives you the wider picture of the tool, and the Colligso TextIn Make integration covers the same app on Make.
Zapier vocabulary in one minute
Seven words you will meet in the editor. Each one comes back later on this page without a second explanation.
- Zap
- Your automation: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event that starts a Zap. Colligso TextIn has none, so the trigger always comes from another app you use.
- Action
- What the Zap does once it is running, such as logging an opt-in or sending a text in Colligso TextIn.
- Task
- What Zapier bills you for: one action that went through. Your plan's monthly allowance counts these.
- Polling vs instant
- A polling trigger is checked on a timer, the plan sets the gap. An instant one is pushed by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming data matches a rule you set, and stops it otherwise.
- Connection
- Your Colligso TextIn account linked to Zapier once, then reused by every step that writes into it.
What it really costs to run
Short answer: nothing extra to start, because Colligso TextIn is not a premium app.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps
- CountedEach successful action
- Not countedThe trigger, failed actions
The trigger on the other app never costs a task, and neither do the checks Zapier runs to spot new data. Each Colligso action that succeeds counts as one task; one that fails counts for nothing. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter or a second action and you need a paid plan. On a polling trigger, the plan sets how often Zapier looks.
Connect Colligso TextIn to Zapier in 3 steps
- 01
Open your Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. Have your Colligso TextIn login at hand before you go further.
- 02
Pick Colligso TextIn
Type the app name in the dialog, select Colligso TextIn, then click Add connection. Zapier hands you over to Colligso TextIn so you can sign in with the account that owns your sites.
- 03
Grant access
Sign in and allow Zapier to act on the account. From then on, every Colligso step in every Zap reuses this connection. If a colleague owns the sites, you need write access on them too.
Your first Zap: opt-ins from Shopify orders
GoalA store selling coffee subscriptions wants buyers who ticked the SMS box at checkout added to its text list, and nobody else.
- 01
Build the trigger
Create a Zap and choose Shopify with New Order as the trigger. Connect the store, then test: Zapier pulls the three most recent orders so you map on real data.
- 02
Add the filter
From the plus icon, add Filter. In the test order, find the value that says the buyer agreed to texts, pick it, choose a text rule, and set what it must equal.
- 03
Add Get Permission
Add Colligso TextIn with Get Permission. Choose the Site, then drop the order's phone number into Mobile Number. Both fields are required.
- 04
Test, then publish
Run each step once and read what came back. When the opt-in shows up in Colligso, click Publish. With a filter this is a multi-step Zap, so it needs a paid plan.
The 3 Colligso TextIn actions
Colligso TextIn gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Get Permission
ActionIn Zapier“Opt-in for text marketing.”
Records that a mobile number has agreed to receive your marketing texts, on the Colligso site you pick. Only two things to fill: the site and the number.
Create Customer
ActionIn Zapier“Import Customer from other app to your Colligso account. Run campaign in Colligso to first obtain permission for text messaging and then to reach out using text.”
Copies a contact from another app into Colligso as a customer, with a first name and a mobile number attached to one site. The official description is clear: a permission campaign in Colligso comes next, before any marketing text.
Send Message
ActionIn Zapier“Sends a message (SMS)”
Fires a single SMS to one mobile number through the chosen site. You write the text in the step and can insert data from earlier steps, like a booking time.
When it breaks
Zapier links no help article to Colligso TextIn, so the failures below come from how Zapier itself behaves.
Since every Zap here starts in another app, most surprises happen on that side. Read these four cases before you switch anything on.
Your existing contacts never arrive
A Zap only reacts to what happens after it is published. Customers already in your shop or CRM stay where they are; moving that backlog is a separate job.A bulk import gets held back
If the trigger app suddenly returns a huge batch, after a migration for instance, Zapier's flood protection can hold those items back instead of firing hundreds of texts.The same record does not fire twice
On a polling trigger, Zapier remembers what it has already seen. An order or row it has already handled will not log a second opt-in or send a second text.Long texts run past the limit
Each message is limited to 160 characters and Colligso appends a required footer. A long template mapped from another app will not fit as written.
Need help automating Colligso TextIn with Zapier?
A person reads every message.



