Communication

Connectix + StackGo

Connectix and the compliance workflow around it.

Connectix publishes 5 trigger events and 3 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Communication Across the workflow Not connected yet
What Connectix is

Connectix is a messaging platform allowing you to send SMS and Viber messages.

Description supplied by Connectix.

Where it fits

Across the workflow, not at a step

A chat or support tool does not sit at one step of a compliance workflow. It carries the workflow to the people who have to act on it — which is why it belongs here, and why pinning it to Intake or Monitor would be wrong.

What StackGo sends to Connectix

An outcome, never the client’s identity data. Connectix would be told what happened; the verification detail stays in your system of record.

  • What happened
  • Who it was for
  • When
  • Where the record is

Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.

Everything else Connectix publishes

Connectix’s public integration surface

The rest of what Connectix exposes on Zapier, beyond the workflow. This is the raw material a connector would use.

5 events
  • Message/Fallback Callbacks
  • Inbound Messages
  • Template
  • New Template
  • Delivery Tracking
3 actions
  • Send a Fallback
  • Send a Message
  • Submit a Tracking Number

Names are Connectix’s own, read from its public Zapier listing on 28 August 2026.

Where this sits

Connectix sits beside the work, not inside it.

The compliance work happens in the five workflows below. Connectix is where the result lands — nothing starts a check here.

Want Connectix connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.