Platform Glossary

Definitions of key terms used throughout the Spojit platform.

Overview

This glossary defines the terms you'll encounter across the Spojit app, help center, and developer docs. Terms are grouped into core concepts, workflow node types, and account or billing concepts. When in doubt, use the specific term from this list rather than a synonym - it makes searching and support requests easier.

Core Concepts

Workspace - your organisation's container in Spojit. Holds all workflows, connections, knowledge collections, members, and billing.
Workflow - an automation built on the canvas. Consists of a trigger plus one or more nodes wired together.
Node - a single building block on the canvas. Each node performs one action (start, call a service, branch, transform, etc.).
Trigger - the event that starts a workflow: Manual, Schedule, Webhook, or Email.
Connector - a global template defining how to integrate with an external service (Shopify, Slack, etc.).
Connection - a tenant's configured instance of a connector, holding credentials and settings.
Execution - one run of a workflow, from trigger fire through final node, recorded in the Executions log.
Variable - data passed between steps. Reference with handlebars syntax: {{ variableName }} or {{ step.field }}.

Workflow Node Types

Trigger - starts the workflow (Manual, Schedule, Webhook, Email).
Connector - calls a tool on a specific connection. Runs in Agent Mode (AI picks the tools) or Direct Mode (you pick the tool).
Transform - reshapes data between steps.
Condition - if/else branching.
Loop - ForEach, While, or Times iteration.
Parallel - fans out into concurrent branches.
Human - pauses for human approval.
Knowledge - queries an indexed knowledge collection.
Send Email - quick email step.
Subworkflow - invokes another workflow as a step.
Response - returns a value to a synchronous webhook caller.

Account and Billing

Credits - the consumption unit for workflow runs. Different node types consume different amounts.
Plan - subscription tier (Free, Starter, Pro, Business) that sets feature limits and credit allocation.
Team - a group of members within a workspace who share access to a set of workflows and connections.
Role - permission level assigned to a member: Owner, Admin, Member, or Viewer.
Audit Log - record of administrative actions (member changes, connection edits, plan changes) for the workspace.

Tips

Use "connector" when talking about the template and "connection" when talking about your configured instance - mixing them up makes support requests harder to answer.
When pasting workflow variable references in documentation or chat, keep the full handlebars including double braces.
Refer to roles by their exact name (Owner, Admin, Member, Viewer) so permission discussions are precise.

Common Pitfalls

Saying "I added a connector" when you mean "I added a connection". The catalog already contains all connectors; you add a connection to use one.
Confusing Execution (one run) with Workflow (the definition). The Executions page shows runs, not designs.
Using "workspace" and "team" interchangeably. A workspace contains teams; they're different layers.