Skip to content

Tutorial: Build your first flow#3

Open
ekline[bot] wants to merge 1 commit into
mainfrom
ekline/8372113e-826e-434f-8afd-0405c0c54dda
Open

Tutorial: Build your first flow#3
ekline[bot] wants to merge 1 commit into
mainfrom
ekline/8372113e-826e-434f-8afd-0405c0c54dda

Conversation

@ekline

@ekline ekline Bot commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

Lets research and build this quckstart

Quickstart: Build your first flow
Tutorial
A simple 10-min

Changes

Status File
🆕 Created flows/build-your-first-flow.md
✏️ Modified SUMMARY.md

📝 Created with EkLine · View session

@usmanaslam712

Copy link
Copy Markdown
Collaborator

Step 1 - Wrong button label with lack of detail

Tutorial says "Click Create Flow." Actual button says + Create Flows leading to an option to create from template or from scratch.

Step 1 - "On Webhook Event" trigger ambiguity

Tutorial says "Select On Webhook Event as the trigger type." The proper term should be starting point.

Step 1 - Incorrect naming conventions

Flow name webhook-to-slack uses dashes. Platform rejects dashes with error: "Only letters, numbers, and underscores are allowed, no spaces or special characters." Should be webhook_to_slack.

Step 5 — {{input.message}} mapping ambiguity

The input.message value does not exist and using it with Slack sendMessage and New webhook received: {{input.message}} results in the message arriving in Slack but showing only "New webhook received:" however the {{input.message}} portion was empty.

Fastn's data mapping autocomplete shows available variables: {{input}}, {{headers}}, {{appConfig}}, {{var}}, {{state}}, {{secrets}}, {{headers['x-fastn-space-tenantid']}}, {{steps}}. The tutorial never tells the user to define a request schema on the trigger step using + Build Schema (for API triggers) or Payload Schema (for webhook triggers). Without defining the schema first, {{input.message}} has nothing to resolve to. The tutorial needs an additional step between Steps 1 and 2 that walks the user through defining the input schema with a message field.

Step 6 - "Debugger" should be "Testing"

Tutorial references "the Debugger" five times. The actual UI has a Test panel with Header, Input, and Output tabs.

Step 7 - DRAFT/LIVE terminology is wrong throughout

Actual statuses are "Live" and "Changes Pending". There is no "DRAFT" status. The claim "DRAFT and LIVE have separate webhook URLs" is unverified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant