Hi y’all, Carolina from support here once again!
A few weeks ago, I created a post about scope. Now, I will talk about context and our other environment variables.
Here we go with this quick tip: In TagoIO, every analysis run receives a context object that describes the execution environment. It provides:
-
Analysis token: used by the SDK/Resources to authenticate calls.
-
Analysis metadata: such as the analysis ID running the code.
-
Environment variables: configuration you set in the Analysis to avoid hardcoding secrets and URLs.
-
ID’s: identification of the resource used to start the Analysis like action_id or widget_id.
-
Secrets: protected confidential information
Why it matters:
-
Security: use the token from context instead of embedding credentials.
-
Portability: switch configs by editing environment variables, not code.
-
Observability: metadata helps with logging and debugging during runs.
You create your Analysis, write the code, and run it on TagoIO or externally; the platform provides the needed token and runtime setup for execution, which are exposed through the context at runtime.
What do you think about this tip? I hope it can be useful to our users here in the community!
Happy Week,