Quickstart Guide
This guide helps you go from zero → deployed Lamatic project and test it end-to-end.
What you’ll learn
- How to create a project and build your first Flow
- How to test a Flow in Studio
- How to deploy so your Flow is accessible from integrations (API / widget / apps)
Prerequisites
- A Lamatic account: lamatic.ai (opens in a new tab)
- Basic understanding: a Flow is a set of connected Nodes that run in order
- Optional (recommended): pick a Template to move faster
If you’re brand new, start with a template first. You can always customize it later.
The quickest way to get started is using a pre-built template, then editing it to fit your use case.
Create (or pick) a Project
- Open Studio (you’ll land on your dashboard).
- Create a new Project (or open an existing one).
Tip: Each Project is isolated — it has its own settings, credentials, and deployments.
Select a Template
- Go to Templates.
- Pick a template that matches your goal (API, chatbot, RAG, automation).
- Add it to your Project.
If you prefer starting from scratch, you can create a new Flow directly from the Flows section.
Configure the Nodes (make it run)
- Open the Flow in the Editor.
- Click each Node and fill required fields (you’ll usually configure):
- Model/provider credentials (for AI Nodes)
- App connections (for Apps Nodes like Slack / Postgres)
- Inputs and payload fields (what your Flow consumes)
Test the Flow
- Click Test in the Editor.
- Provide sample inputs (if your trigger expects them).
- Verify outputs at the final node (Response) and check logs if anything fails.
Deploy the Project
Deployment makes your latest Flow changes available for integrations.
- Click Deploy.
- Wait for deployment to finish.
- Copy the integration details from Studio (endpoint / keys / ids) as needed.
Common beginner mistakes (and how to avoid them)
- Forgetting to deploy: If you updated keys, variables, or a Flow, deploy so changes take effect.
- Missing credentials: Many nodes require a model/API connection. Check the node config panel for required fields.
- Payload mismatch: Ensure your input payload matches what your trigger and nodes expect (field names + types).
What’s next?
- Learn the core building blocks:
- If you’re integrating into an app:
- Explore hands-on tutorials: