Template gallery
Templates are ready-made scenarios built by the Latenode team and community. They show working patterns (AI agents, webhooks, CRM sync, MCP servers, and more) so you do not start from a blank canvas.
A template gives you nodes, routes, and often sample settings. You still connect your own accounts, adjust fields for your data, and test before Production.
When to choose a template
- You need something working today and will customize later.
- You want to learn how a complex pattern is wired.
- A template already matches your use case (support bot, lead sync, scheduled report).
- You prefer editing a proven flow over describing it to AI or an MCP agent.
Open the gallery
In the app, go to the template gallery:
Browse by category or search by app name. Each card shows what the scenario does and which integrations it uses.
Documentation also links featured examples:
Copy a template
Open a template
Click a template to read the description and preview the flow.
Use template
Click Use template. The scenario opens in your workspace on the Development branch with nodes already placed and connected.
Connect authorizations
Open nodes that need apps and select or create authorizations. Templates rarely include your personal credentials.
Adjust settings
Replace placeholder emails, URLs, schedules, and prompts with your values. Read sticky notes or descriptions on the canvas if the author left setup hints.
Test, deploy, activate
Run Run Once or trigger the scenario as designed. When Development is correct, Save, Deploy, and turn Active on for Production.
After you copy
| Check | Why |
|---|---|
| Authorizations on every app node | Without them, runs fail immediately |
| Trigger settings (schedule, webhook URL) | Wrong timezone or URL means no runs or wrong data |
| Field mappings (DATA tab) | Template placeholders may not match your property names |
| Error handling routes | Confirm failures go where you expect (retry, notify, stop) |
Combine with other ways to build
Templates are a starting point, not a lock-in. You can open AI scenario helper to refactor a branch, or extend the flow manually with new nodes and routes.
Want to publish your own template, or looking for a specific use case that is not in the gallery? Contact support or post in the Latenode community.
Go deeper
- Template gallery
- Publishing scenarios - Deploy and Active
- Authorizations - connect apps once, reuse everywhere
Latenode MCP Server
Connect Cursor, Claude, or another MCP client to the Latenode MCP Server and build scenarios from your agent.
How Latenode works
The basics of the Latenode automation platform: scenarios, triggers, and actions.
Need Help? Ask the community
If something on this page is missing or unclear, post on the Latenode community forum. Our team and other users usually reply quickly.