vocabulary: name: Squillo Platform Vocabulary description: >- Key terms, concepts, and operational vocabulary for the Squillo SaaU (Software as a Utility) integration and automation platform. version: "1.0" created: "2026-05-02" modified: "2026-05-02" tags: - Squillo - Integration Platform - Workflow Automation terms: - term: SaaU label: Software as a Utility description: >- Squillo's core product philosophy — making enterprise software integrations as easy and on-demand as utility services. Contrasts with traditional SaaS by emphasizing process automation across entire IT systems rather than single-application functionality. category: Platform - term: Workflow label: Workflow description: >- A defined automation sequence consisting of a trigger and one or more steps that perform actions across connected systems. Workflows encode business processes that were previously manual or required custom development. category: Core Concepts - term: Trigger label: Trigger description: >- The event or schedule that initiates a workflow execution. Types include webhook (HTTP callback), schedule (cron-based), manual (API or UI invocation), and event (platform events from connected systems). category: Core Concepts - term: Step label: Workflow Step description: >- A single unit of work within a workflow. Step types include action (connector API call), condition (branching logic), loop (iteration), delay (time-based pause), and transform (data transformation). category: Core Concepts - term: Connector label: Integration Connector description: >- A pre-built integration module that provides authenticated access to a specific third-party system (e.g., Salesforce, ServiceNow, SAP). Connectors expose actions that workflow steps can invoke. category: Integrations - term: Connection label: Connector Connection description: >- An authenticated instance of a connector configured with credentials for a specific tenant account in the connected system. A single connector can have multiple connections (e.g., prod and staging). category: Integrations - term: Action label: Connector Action description: >- A specific operation exposed by a connector (e.g., "Create Record", "Send Email", "Update Ticket"). Actions correspond to API calls made to the connected system. category: Integrations - term: Execution label: Workflow Execution description: >- A single run of a workflow, triggered by its configured trigger or manually via API. Executions capture input data, step outputs, timing, and final status (running, success, failed, cancelled). category: Operations - term: Input Mapping label: Input Mapping description: >- Configuration that defines how data flows into a step from previous step outputs, trigger payload, or static values. Uses JSONPath or template expressions to reference data. category: Data - term: Output Mapping label: Output Mapping description: >- Configuration that defines which parts of a step's response are made available to subsequent steps as named variables. category: Data - term: Variable label: Workflow Variable description: >- A named value available across all workflows in an account. Variables can be plain (visible) or secret (encrypted, masked in logs). Used to store API keys, configuration values, and shared reference data. category: Configuration - term: Webhook label: Webhook Trigger description: >- An HTTP endpoint generated by Squillo that external systems can call to trigger a workflow. Each webhook trigger has a unique URL and supports authentication via HMAC signatures or API keys. category: Triggers - term: Schedule label: Schedule Trigger description: >- A cron-based trigger that fires a workflow at defined time intervals or specific times. Supports standard cron expressions with timezone configuration. category: Triggers