Skip to content

Release Notes

Audience: Everyone · Tags: releases, release-notes

This page describes what's in SnapLink today — a snapshot, not a change-by-change history. As the product evolves we'll add dated entries above this one; for now, read this as "what you get if you sign up right now."

2026-07-03 — Current release

SnapLink is pilot-ready / early access: the core Trigger → Action model works end to end, every run is real and observable, and AI only ever drafts — a person always reviews before anything is saved or activated.

Accounts & workspaces

  • Email/password sign-up and sign-in.
  • Every flow, connection, installed connector, and run lives inside a workspace. Workspace roles are owner (assigned automatically to whoever creates the workspace), admin, and member — no other roles exist yet.

Snap Studio

  • The guided flow builder at /snap, in three stages: Describe → Review & edit → Save & test.
  • Describe your automation in plain English and get back a plan — an editable, ordered list of step cards (one "WHEN" trigger card, one or more "THEN" action cards).
  • Plans are drafted by a real LLM (Claude, via the configured AI provider) when one is configured; otherwise a deterministic, keyword-based rules planner drafts them automatically. Either way, the plan reports which engine produced it, and nothing is ever activated without you reviewing and saving it yourself.
  • Check runs design-time validation on your plan before you save, surfacing plain-language problems tied to specific steps or fields.
  • Saving a flow runs one real test run immediately, so you see it work before you trust it.
  • Quick Send lets you send a single message to an email address or a URL right now, with no flow saved at all.

Connectors

SnapLink ships the Webhook trigger connector plus five action connectors — REST, Email, Slack, Teams, and HubSpot — installable from the in-app Marketplace. Installed connectors move through a lifecycle: installed → configured → certified → active (with disabled and deprecated reachable from any of those states).

  • Webhook — the only trigger type today: a private, secret-bearing URL (/api/v1/webhooks/<flowId>/<secret>) that starts a flow when something POSTs to it. The secret can be rotated with a grace window for the old value.
  • REST — call any HTTP endpoint as an action, with SSRF protection blocking requests to private/internal network addresses.
  • Email — send email as an action.
  • Slack, Teams, HubSpot — send a Slack message, send a Teams message, and create a HubSpot contact, respectively. Early access: live sending for these three requires OAuth credentials to be configured; until then, flows using them install and validate correctly but return an auth error on live calls.

Templates

Seven ready-made starter flows are available in the Template Catalog: Webhook → Slack Message, Webhook → Teams Message, Webhook → HubSpot Create Contact, HubSpot Lead → Slack Alert, HubSpot Contact → Teams Message, REST → Slack Message, and REST → Teams Message. Install one, swap in your own values, and activate.

Monitoring & debugging

  • Every run — whether started by a live webhook, a manual "run now," or a Snap Studio test-run — is recorded with a status: queued, running, succeeded, failed, cancelled, retry_pending, retry_running, or retry_exhausted.
  • The flow debugger gives you a read-only view of any run: its timeline, each step's status, the connector calls it made, and — for failures — an error code from a fixed taxonomy (auth, rate_limit, timeout, upstream_5xx, bad_request, blocked, unknown) plus a suggested fix.

API

The full flow lifecycle — auth, workspaces, connectors, connections, flow drafts and versions, webhooks, runs, and monitoring — is available over a REST API. Every authenticated call takes a bearer token (Authorization: Bearer <token>); every response is wrapped in a consistent success/error envelope. See the API Reference.

What's next (planned)

Not in the product yet — planned, in roughly the order we're tackling them:

  • Payload mapping / templating — passing data from a trigger into an action's fields.
  • Scheduled (cron) triggers — starting a flow on a timer, not just via webhook.
  • Branching, conditions, and loops — logic beyond a straight-line list of actions.
  • SSO / SAML — enterprise identity provider login.
  • Billing / paid plans — today every account is early access; no paid tiers exist yet.

We don't have uptime SLAs, compliance certifications, customer counts, or savings metrics to report — those aren't part of the product today, and we'd rather say nothing than say something untrue.

Related: Glossary · Template Catalog · Connectors · API Reference