Creating Your First Workflow
Step-by-step guide to creating your first automation workflow in Spojit.
Overview
A workflow is a visual definition of an automation. You assemble it on a canvas by dragging nodes from the palette, connecting them with edges, and configuring each node's settings. Spojit stores both the visual layout and an executable definition; when you click Run, the executable definition is sent to the workflow runner.
Every workflow begins with a Trigger node and grows from there. For a first workflow, a Manual trigger plus a single Connector node is the fastest way to confirm the end-to-end loop works: design, save, run, inspect results.
Before You Start
- An active Spojit workspace.
- At least one Connection added on the Connections page (the workflow needs a real connector instance to call).
Steps
- Open Workflows from the left sidebar and click + New Workflow.
- Give the workflow a name (for example, "My First Workflow"), optionally add a description, and click Create. Spojit opens the designer with an empty canvas and a default Trigger node.
- Click the Trigger node, pick Manual as the trigger type, and close the properties panel. Manual triggers fire when you click Run, which is ideal for testing.
- Drag a Connector node from the palette onto the canvas. Connect the Trigger's output handle to the Connector's input handle.
- Click the Connector node. Choose a connection, choose a tool, and fill in any required inputs. Use
{{ trigger.field }}handlebars syntax to reference data from the Trigger node. - Click Save in the toolbar. The canvas state and executable definition are persisted to your workspace.
- Click Run. Nodes light up as they execute - blue while running, green on success, red on error. Click any completed node to inspect its output.
Tips
- Save frequently. The designer doesn't auto-save while you're editing.
- Use the AI chat sidebar in the designer - it can see your canvas and will add or wire nodes for you.
- Start with Manual triggers while you iterate, then swap to Schedule, Webhook, or Email once the logic is right.
- Give each node a short, descriptive label - it makes execution logs easier to scan later.
Common Pitfalls
- Forgetting to connect nodes. Unconnected nodes are skipped at runtime and won't show output.
- Referencing a variable that doesn't exist yet. Variables are only available from upstream steps - check the variable picker.
- Selecting a Connector tool before choosing the Connection. The tool list is populated from the chosen connection.
- Clicking Run before Save. Spojit runs the saved definition, not the unsaved canvas state.
Related Articles
- Running Your First Workflow
- Understanding Execution Logs
- Overview of the Workflow Designer
- Adding and Connecting Nodes
- Adding a New Connection