Quick Start Guide
This guide takes you from a blank canvas to a running workflow in about 5 minutes. You will build a workflow that receives a webhook, makes an HTTP request, and returns a response — then test it locally using the CLI.
Make sure you have:
- A Tensorify account at app.tensorify.io
- Python 3.9+ installed
- The CLI installed:
curl -fsSL https://cli.tensorify.io/install | sh(Windows:irm https://cli.tensorify.io/install.ps1 | iex)
See Installation for detailed setup.
Sign in to app.tensorify.io and complete the onboarding to create your workspace. Then from the dashboard:
- Click New Workflow
- Give it a name — for example,
my-first-workflow - Click Create
The canvas will open with an empty graph.
Every workflow needs a trigger — the event that starts execution. Add a Webhook node:
- In the node palette on the left, find Webhook under Triggers
- Drag it onto the canvas
- Click the node to open its settings panel
- Leave the defaults as-is for now (method: POST, verification: none)
Next, add an action. This node will call an external API when the webhook fires:
- Drag an HTTP Request node onto the canvas
- In its settings, set:
- Method: GET
- URL:
https://httpbin.org/get
- Connect the payload output of the Webhook node to the body input of the HTTP Request node
tensorify init
tensorify login
tensorify init creates the runner config. tensorify login opens your browser to sign in and links the CLI to your workspace.
On a VPS or headless server, use tensorify init --api-key tfk_your_key instead. Get the key from Settings → API Keys in the app. See Installation for details.
tensorify runner start
Expected output:
✓ Connected to Tensorify
✓ Runner registered
Waiting for workflows from the app...
Leave this terminal running.
Canvas tests use test signals from the editor only. For production webhooks, deploy from the Deploy dialog — see Running Workflows and Deploying Workflows.
Back in the browser:
- Click the Test button in the top toolbar
- Select the HTTP Request node as the target
- Click Run to Selected
The workflow executes on your local machine up to the selected node.
Your terminal will show the execution log. In the editor, click the HTTP Request node to see its output — the JSON response from httpbin.
Webhook Trigger → HTTP Request
When this workflow receives a POST request, it calls httpbin.org/get and records the response. You can now extend it by adding Transform, If, Code, or any other nodes.
- Core Concepts — understand how nodes, edges, and data flow work
- Deploying Workflows — put this workflow in production
- Plugins — browse all available nodes
- Guides — follow a complete real-world automation from start to finish
