Skip to content

Quick Send

Audience: Everyone · Tags: studio, quick-send, beginner

Quick Send is the fastest thing you can do in Snap Studio: type a message, tell it where to go, and send it — right now, for real, with no flow built or saved.

When to use it

Reach for Quick Send when you want to send one thing, one time — testing that a destination works, firing off a one-off notification, or demonstrating SnapLink without building anything permanent. Reach for the full three-stage builder instead (Describe it → Review & edit → Save & test) when you want the same thing to happen automatically every time a trigger fires, from now on.

Where to find it

Quick Send lives as a collapsible section on the Describe it stage — open it, and you'll see a message textarea, a destination field, and an optional title field. It doesn't touch the plan or step cards you use for a full flow at all; it's a separate, simpler path.

The two destination types

You put exactly one thing in the destination field, and SnapLink figures out how to deliver it from what you typed:

  • An email address (like ops@example.com) — SnapLink sends your message as a real email, over SMTP.
  • A web address starting with http:// or https:// — SnapLink sends your message as a real HTTP request straight to that URL.

Whichever one you type, SnapLink recognizes the shape of it — an address with an "@" versus a URL — and picks the matching delivery channel automatically. There's no separate switch to flip.

Sending

Submitting Quick Send calls:

POST /api/v1/flow-designer/snap
Authorization: Bearer $TOKEN
Content-Type: application/json

{
  "text": "Reminder: standup at 9am.",
  "destination": "ops@example.com",
  "title": "Standup reminder"
}

The title field is optional. SnapLink sends the message immediately and returns a 201:

{
  "runId": "run_4b19aa",
  "status": "succeeded",
  "flowId": "flow_3ea701",
  "workspaceId": "ws_8f2a1c",
  "destination": "ops@example.com",
  "channel": "email"
}

Point it at a URL instead, and the response has the same shape but with "channel": "rest":

{
  "runId": "run_4b1c02",
  "status": "succeeded",
  "flowId": "flow_3ea701",
  "workspaceId": "ws_8f2a1c",
  "destination": "https://hooks.example.com/incoming",
  "channel": "rest"
}

Because this is a real send through SnapLink's execution engine — not a preview — you get back a genuine runId, so the send is fully logged, the same as any other run. What you don't get is a saved, reusable flow: there's no plan, no step cards, and no Stage 2 review to come back to. If you want the same message to go out automatically every time something happens, build it as a proper flow instead.

Worked example

You want to check that your team's webhook receiver is actually listening before you wire a whole flow to it. Open Quick Send, type a throwaway message like "Testing 1 2 3", paste https://hooks.example.com/incoming into the destination field, leave the title blank, and click send. Within moments you get back status: "succeeded" and channel: "rest" — confirmation the endpoint is live, with zero flows created.

If something goes wrong

See Snap Studio problems if your Quick Send doesn't arrive — it covers the most common causes for both email and URL destinations.

Related: Describe it · Save & test · Email connector