Academy

Want to learn how to add business logic to your WeWeb app? Check out our Build a proof of concept course for a comprehensive look at creating interactive experiences with workflows in WeWeb.

Intro to workflows

Workflows are sequences of actions that automate tasks in your WeWeb application. They allow you to create dynamic, interactive experiences by defining what happens when specific events occur - such as a user clicking a button, submitting a form, or when a page loads.

Understanding workflows

Every workflow consists of two main components:

1. Trigger — The event that starts the workflow (e.g., a button click, page load, or form submission)
2. Actions — The sequence of steps that WeWeb performs when the trigger occurs

For example, when a user submits a sign in form (On submit) trigger, you might want to:

• Sign the user in
• Check their role
• Navigate them to the appropriate page

Creating your first workflow

To create a local workflow:

In this example:

1. We select an element (in this case, a button)
2. Create a new workflow on the element
3. Select the trigger to use (On click)
4. Define the actions (increment the value of our Counter Value variable)
5. Test the workflow in Preview mode (with the live value of the variable open in the Debug panel)

Types of workflows in WeWeb

WeWeb offers four different types of workflows, each with its own scope and purpose:

Local workflows

Local workflows are attached to specific elements and are triggered by interactions with those elements. They're perfect for handling element-specific actions, like validating input fields or toggling visibility.

Functions

Functions are defined once in the Workflows tab (in the Interface section) and can be reused throughout your application. They help you maintain consistency and reduce duplication by centralizing common workflow logic.

Functions are ideal for:

• Complex logic that needs to be reused in multiple places
• Standardized processes like user authentication or data validation
• Workflows that might need to be updated across your application

TIP

When you find yourself creating similar workflows in multiple places, consider converting them to reusable workflows. This makes maintenance easier and ensures consistent behavior throughout your application.

Learn more about how to create and reuse reusable workflows

Page Trigger workflows

Page Trigger workflows apply to an entire page and can be triggered by page-level events such as page load or page scroll. They're useful for page-specific initialization or cleanup tasks.

To access Page Trigger workflows:

1. Click on the Workflows tab in the Interface section
2. Select the Page Triggers tab
3. Choose which page you want to add workflows to from the dropdown
4. Click + Add Workflow to create a new page workflow

Page Trigger workflows are especially useful for:

• Loading data when a page initializes
• Setting up page-specific variables
• Tracking page views

App Trigger workflows

App Trigger workflows operate at the application level and run across your entire website. They're ideal for site-wide functionality like authentication checks or analytics tracking.

To access App Trigger workflows:

1. Click on the Workflows tab in the Interface section
2. Select the App Triggers tab
3. Click + Add Workflow to create a new app workflow

App Trigger workflows are perfect for:

• Site-wide analytics
• User preference management
• Feature flags and site-wide settings

Managing workflows

As your application grows, managing workflows becomes increasingly important:

Finding reusable workflows

To see if a reusable workflow is used on a specific page:

1. Click on the Workflows tab in the Interface section
2. Select the Reusable tab
3. Toggle the "All pages" switch to filter by the current page

This helps you track where workflows are being used and ensures you don't accidentally break functionality when making changes.

Naming conventions

Always use clear, descriptive names for your workflows:

✅ Good: "ValidateUserInput", "SendWelcomeEmail", "UpdateCartTotal"
❌ Bad: "NewWorkflow", "Workflow1", "MyWorkflow"

Consistent naming makes debugging easier and improves team collaboration.

Best practices for workflows

1. Keep workflows focused — Each workflow should handle a specific task
2. Use reusable workflows for reusable logic — If you find yourself duplicating workflows, create a reusable version
3. Error handling — Set up error workflows to gracefully handle failures
4. Testing — Use the Debug panel to verify your workflows behave as expected
5. Documentation — Add comments to complex workflows to explain their purpose

Interface Workflows vs APIs

Workflows in the Interface section run in the user's browser and are great for UI logic. For secure operations (like creating records in tables, validating input, or using secrets), create an API in the Data & API tab and call it from your workflow.

Learn about APIs in the Data & API tab →

CONTINUE LEARNING

Ready to dive deeper into workflows? Learn about the different types of triggers available:

Learn about triggers →