How to create your first workflow on n8n

If self-hosting, install n8n via npm or Docker. Run npm install -g n8n globally, then start the service with n8n start. This launches n8n on the default port 5678 at http://localhost:5678. For Docker users, run docker run -it --rm --name n8n -p 5678:5678 n8nio/n8n. The default database is SQLite (stored in ~/.n8n/database.sqlite) with no authentication enabled initially. Open your browser to http://localhost:5678 and complete the setup wizard by creating an owner account if prompted.

From the Overview page (your default landing page after login), locate the + (create) button in the upper-right corner. Click it and select Workflow from the dropdown menu. Alternatively, use the left side menu by selecting the + button in the upper-left corner, then choose Workflow. If using projects (available in cloud or enterprise editions), select Personal space or a specific project; community self-hosted instances default to personal space.

In the new empty canvas, click the workflow name field at the top-left (which defaults to "My workflow" or untitled). Enter a descriptive name such as "First Test Workflow" and press Enter. The workflow saves automatically to your Workflows list under personal space, so you can return to it anytime.

On the empty canvas, select the prominent Add first step... button in the center. This opens the node selector. Search for "Manual" to find the simplest trigger for testing. Select the Manual Trigger node to add it to the canvas. The node appears immediately; click it to open its settings panel. Manual Trigger requires no configuration—it exists purely for testing workflows by allowing you to execute them on demand.

With the Manual Trigger node selected, click the + icon on its right edge to connect a new node. Search for "Edit Fields" (or "Set" in older versions) and select it. The Edit Fields node allows you to transform or create data. Double-click the node to open its configuration panel. Select Keep Only Set mode, then click Add Field. Set the field name to testMessage and the value to "Hello from my first n8n workflow!" (as static text). Close the panel by selecting Back to canvas or clicking outside.

To extend your workflow, click the + icon on the Edit Fields node's right edge and add more action nodes. Common examples include Email (to send results), OpenAI (for AI processing), or HTTP Request (to call external APIs). Each node connects sequentially, forming a data pipeline. Configure each node by double-clicking it and filling in required fields. For external services like OpenAI or Gmail, you'll need to add credentials first (see Prerequisites).

If your workflow includes nodes that interact with external services (OpenAI, Gmail, Slack, etc.), you must add credentials. In the node's configuration panel, look for a Credentials or Authentication field. Click Create New or Add Credentials. Enter your API key or authentication details (e.g., OpenAI API key from your account dashboard). Save the credentials with a descriptive name. n8n encrypts and stores these securely, so you only enter them once per service.

Click the Save button (usually top-right or in the menu) to persist your workflow. After saving, toggle the Active switch (top-right of the canvas) to enable the workflow. For Manual Trigger workflows, activation is optional since you'll execute them on demand. For scheduled or event-triggered workflows, activation is required to run automatically. A green indicator confirms the workflow is active.

Click the Execute Workflow button (top-right, typically a play icon) to run your workflow once. The system executes from the trigger node through all connected action nodes. Watch for green checkmarks on nodes, indicating successful execution. Click any node to view its input and output data in the execution panel. This panel shows exactly what data flowed through each step, making it easy to debug issues. If a node shows a red error icon, click it to see the specific error message.

After execution, examine the output of your final node. If the results match your expectations, your workflow is complete. If not, adjust node configurations, add missing credentials, or restructure the node connections. Common adjustments include changing field names, updating API parameters, or adding conditional logic with If nodes. Save changes and re-execute to test. Repeat this cycle until your workflow produces the desired output.