Flow Templates¶

Audience: Everyone · Tags: template, flow, catalog

Purpose. Templates are ready-made flow definitions — a trigger plus one or more pre-wired actions — so you can start from something that already works instead of a blank definition. SnapLink ships 7 starter templates today.

When to use. When your automation matches (or is close to) a common pattern below. You still fill in your own specifics — channel IDs, recipients, message text — before promoting it.

The 7 starter templates¶

id	Title	Category	Connectors
`webhook-to-slack`	Webhook → Slack Message	notifications	slack
`webhook-to-teams`	Webhook → Teams Message	notifications	teams
`webhook-to-hubspot`	Webhook → HubSpot Create Contact	crm	hubspot
`hubspot-lead-to-slack`	HubSpot Lead → Slack Alert	sales	hubspot, slack
`hubspot-to-teams`	HubSpot Contact → Teams Message	sales	hubspot, teams
`rest-to-slack`	REST → Slack Message	notifications	rest_sdk, slack
`rest-to-teams`	REST → Teams Message	notifications	rest_sdk, teams

Every template's trigger is a webhook. hubspot-lead-to-slack and hubspot-to-teams chain two actions (create a HubSpot contact, then notify a channel); the rest are a single action.

Browsing templates¶

curl https://api.snaplink.cloudsolutionaccelerators.com/api/v1/flow-designer/templates \
  -H "Authorization: Bearer $TOKEN"

{ "data": [
  { "id": "webhook-to-slack", "title": "Webhook → Slack Message", "description": "When a webhook fires, post a message to a Slack channel.", "category": "notifications", "requiredConnectors": ["slack"], "flowDefinition": { "...": "..." } }
] }

Note the response shape here — /flow-designer endpoints return { "data": ... } without an "ok" field, unlike most of the rest of the API.

Filter by category, or fetch one template by id:

curl "https://api.snaplink.cloudsolutionaccelerators.com/api/v1/flow-designer/templates?category=notifications" \
  -H "Authorization: Bearer $TOKEN"

curl https://api.snaplink.cloudsolutionaccelerators.com/api/v1/flow-designer/templates/hubspot-lead-to-slack \
  -H "Authorization: Bearer $TOKEN"

An unknown id returns a 404 with error.code: "TEMPLATE_NOT_FOUND".

Using a template¶

Each template response includes a complete, ready-to-use flowDefinition. There isn't a one-click "install" button yet (that workflow is Planned) — today, using a template means copying its flowDefinition into a new flow the same way you would any other definition:

POST /flows to create the flow shell.
POST /flows/:id/drafts with the template's flowDefinition as the definition — edit the placeholder values first (the sample channel id C0000000, the sample HubSpot email, etc.) to your real ones.
Make sure every connector the template needs (see its requiredConnectors) is installed and active in your workspace — see Connect Your First App.
Validate it — this is exactly what will catch a connector you forgot to connect.
POST /drafts/:id/promote to make it live.

See Creating Flows for the full curl walkthrough of steps 1–5.

How templates relate to Snap Studio¶

Templates and Snap Studio are two separate mechanisms today, and it's worth being precise about the difference:

The template catalog (this page) and the legacy POST /flow-designer/draft endpoint both draw from the same 7 templates above, matching your prompt's keywords ("Slack", "HubSpot", "Teams"…) to the closest one.
Snap Studio's guided plan builder (/snap in the app) does not read from this template catalog. It builds its own plan directly from your description, and today its plans are limited to a webhook trigger plus email or generic REST actions — it doesn't yet offer Slack, Teams, or HubSpot steps. For those connectors, use a template or the raw API directly.

See AI Flow Drafting for the full picture of both drafting paths, and Snap Studio for what Studio can build today.

Best practices¶

Treat a template as a starting point, not a finished flow — always replace the sample channel/recipient/URL values with your real ones.
Check requiredConnectors before you start; connecting the app first avoids a missing_credential validation error later.
If no template matches, Creating Flows walks through building one from scratch — it's the same amount of work as filling in a template's blanks.

FAQ¶

Can I save my own custom templates? Not yet — sharing custom templates is Planned. Will more templates be added as connectors mature? Yes — the catalog is expected to grow alongside the connector set.

If something goes wrong¶

If a flow built from a template validates but doesn't actually run when triggered, see Flow not running.