Hi y’all, Carolina from support here once again 
If you’re new to Analysis on TagoIO and want to process your device data or connect to external APIs, this post gives you a practical starting point.
First of all, a reminder about what is Analysis and when to use it: Analysis is TagoIO’s serverless compute layer that lets you transform data, automate workflows, and integrate with external services programmatically. You can process variables, move data across devices, and combine it with Actions to trigger on events or schedules.
- Create your first Analysis
Go to Analysis, click “+ Add Analysis”, choose a runtime (Node.js, Deno, or Python), and decide whether to run on TagoIO servers or externally. You can start from built-in code examples to learn the basics faster.
- Triggering your Analysis with Actions
Analyses typically run via Actions (e.g., when new data is inserted, on a schedule, or custom conditions) or Widgets. Pairing Actions with Analysis is the standard way to build event-driven automations.
- Data manipulation basics
-
The platform provides example scripts right inside the Analysis editor showing how to:
-
Read and insert device data
-
Execute calculations
-
Send notifications
-
- Integrating with external APIs
- Analyses can call external services (e.g., REST APIs) using Node.js, Deno, or Python. For larger projects or when you need extra npm packages (like axios), use the TagoIO Analysis Builder to bundle dependencies before uploading, or run the Analysis externally during development.
- Local development and deployment tips
Develop and debug locally using Node.js with your Analysis token, then bundle your project with @tago-io/builder to generate the .tago-io.js file and deploy it back to TagoIO when you’re ready. For teams integrating multiple libraries or complex API flows, use the TagoIO CLI (@tago-io/cli) to initialize the project, manage environments, and deploy/run your Analysis from the terminal.
There is already a post about CLI here. You can check it also 
- Helpful examples to explore
Inside the Analysis editor, pick from the provided examples to quickly see patterns for reading/writing device data and notifications.
That’s it for a quick start. The links above cover creation, triggers, examples, and how to integrate external services in a scalable way. If you’ve built an integration (e.g., calling a weather API to enrich device data), please share your approach and any pitfalls you found helpful to avoid.
Cheers,