Welcome to SnapLink¶
Audience: Everyone · Tags:
overview,product-tour,getting-started
SnapLink helps you connect the apps and services you use every day, without writing code. You tell SnapLink what should happen, and it does that thing for you, reliably, every time — and it shows you exactly what happened, every time.
The idea in one sentence¶
Trigger → Action. Something happens (the trigger), so SnapLink does something in response (the action). A saved trigger-plus-actions is called a flow.
Here's a plain example: "When my link gets a message, email it to me." The trigger is my link gets a message — a private web address (a webhook) that other systems can send information to. The action is email it to me — SnapLink sends the email through your mail settings. Once that flow is saved, it happens automatically, every single time your link receives a message. You don't have to be there, and you don't have to do it by hand.
Flows can have more than one action. A single trigger can, for example, email you and post a message somewhere else — SnapLink runs each action in order and keeps a record of what happened.
How you build a flow¶
You don't fill out a technical form to build a flow. You describe what you want in plain words inside Snap Studio — SnapLink's guided flow builder, found at /snap in the app. Studio turns your description into a plan you can read, edit, and approve before anything is saved. Nothing runs on your behalf until you say so.
That's the core trust model behind SnapLink:
- AI proposes, you approve. SnapLink's assistant can draft a flow for you, but it never turns anything on by itself.
- Every run is observable. Once a flow is active, every single time it runs you can see exactly what happened, step by step.
- Every failure is explainable. If a step doesn't work, SnapLink tells you what went wrong in plain language and, where it can, how to fix it.
What you can connect today¶
SnapLink is an early-access product with a deliberately small, honest initial connector set:
| Connector | What it does |
|---|---|
| Webhook | Starts a flow when another system sends a message to your private link |
| REST / HTTP | Sends a request to any public web address you choose |
| Email (SMTP) | Sends an email through mail settings your operator has configured |
| Slack | Posts a message to Slack (early access — see note below) |
| Microsoft Teams | Posts a message to Teams (early access — see note below) |
| HubSpot | Creates a contact in HubSpot (early access — see note below) |
Slack, Teams, and HubSpot are early access: their connector code makes real calls to each vendor's API and has been thoroughly tested using fake responses, but it hasn't yet been exercised against a real Slack, Teams, or HubSpot account — that needs real credentials that your operator connects for your workspace. More connectors are planned over time — SnapLink will only ever tell you what's actually available, not what's coming.
An early product, built on trust rather than hype¶
SnapLink is genuinely early. We'd rather tell you plainly what it does today than promise things it doesn't do yet. There are no invented customer counts, no manufactured savings numbers, and no compliance badges that haven't been earned. What you do get is a small set of things that work end to end, that you can watch run, and that never act without your say-so.
If a capability isn't ready yet, these docs will say so honestly — using words like "Planned" or "Early access" — rather than imply it exists.
Where to go next¶
Ready to see it work? The Quick Start walks you from creating an account to watching your first real flow succeed, in about 10 minutes.
Related: Quick Start · Your First Success · Glossary
Was this helpful? 👍 👎