--- title: "Cloud Functions glossary" slug: "cloudfunctions-glossary" tags: ["Cloud Functions"] updated: 2026-09-17T09:18:13Z published: 2026-09-17T09:18:13Z canonical: "guide.ncloud-docs.com/cloudfunctions-glossary" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Cloud Functions glossary Available in Classic and VPC To use Cloud Functions, you must become familiar with a few terms. The glossary and its description are as follows: ### Namespace A unique area assigned per user, created as a random string All resources are created under a namespace, serving as the basis for measuring usage and calculating charges per user ### Resource Term referring to Cloud Functions packages, actions, sequences, and triggers ### Sequence An action that runs multiple actions sequentially ### Sequence action Term used with the same concept as sequence. See sequence description ### Action NAVER Cloud Platform's service that can be written in desired languages such as JavaScript, Swift, Java, Python, PHP, without specific predefined tasks. Can perform user image detection, respond to database changes, aggregate API call sets; actions can be called by users or run in response to events, and can be run as sequences taking other actions' results as input ### Action container Space where actions run Created when action runs, each action owns an independent container ### Activation Result of running an action or trigger Created when action runs as a unique value containing meta information, each activation owns a unique 32-character ID consisting of random letters and numbers ### Web action Cloud Functions action that can easily provide web services by creating web-based applications Can implement backend logic accessible to anyone by connecting with API Gateway ### Trigger Event forwarding object that can run actions through events from cloud services or external services that can integrate with Cloud Functions Can run actions depending on registered events when they occur, event data forwarded when running triggers is forwarded as execution parameters to each action ### Package Manage related actions together as one unit through packages Note For more information on terms, see [Glossary](https://www.ncloud.com/guideCenter/glossary) on NAVER Cloud Platform portal.