DocsAutomation Workflows

Pro

Automation Workflows

Build visual automation workflows that connect triggers, actions, and AI processing — no backend code required.

Automation Workflows require a Pro plan or higher.

Creating a Workflow

Building a workflow in GenMB is a visual, step-by-step process. Connect nodes on a canvas to create automated backend logic without writing code.

Open the Workflow Builder

Navigate to the Workflows section from your app editor sidebar. Click "Create Workflow" to open the visual canvas.

Choose a trigger

Every workflow starts with a trigger. Select a webhook trigger for real-time events, a schedule trigger for recurring automation, or manual trigger for testing.

Add and connect nodes

Drag nodes onto the canvas and connect them in sequence. Each node type (HTTP Request, Email, Conditional, Delay, AI Processing, Data Transform) handles a specific task.

Configure each node

Click a node to set its parameters — API endpoints, email templates, conditions, prompts, or data mappings. Use variable interpolation to pass data between nodes.

Test and activate

Use the test button to simulate a real execution with sample data. Once verified, activate the workflow to begin processing real events or running on schedule.

Node Types Reference

GenMB workflows support six node types, each designed for a specific automation task. Combine them to build powerful backend logic without writing code.

HTTP Request — Make API calls to any external service. Configure method (GET, POST, PUT, DELETE), headers, body, and authentication. Use data from previous nodes with variable interpolation.

Email — Send email notifications with customizable templates. Include dynamic data from your workflow using variables. Perfect for alerts, confirmations, and reports.

Conditional — Route workflow execution based on conditions. Define if/else logic to branch your workflow. Check values, compare data, or evaluate expressions.

Delay — Pause workflow execution for a specified duration. Useful for rate limiting, scheduling follow-ups, or waiting for external processes to complete.

AI Processing — Send data through a language model for classification, summarization, extraction, or generation. Configure the prompt and use the AI output in subsequent nodes.

Data Transform — Reshape, filter, or combine data between nodes. Map fields, extract values, merge arrays, or format data for the next step in your workflow.

Triggers and Scheduling

Every workflow starts with a trigger. Choose between webhook triggers for real-time events or schedule triggers for recurring automation.

Webhook triggers generate a unique URL for your workflow. Send HTTP requests to this URL from any external service, form, or API to start execution.

Schedule triggers run your workflow at fixed intervals — every minute, hour, day, or week. Configure the schedule using a simple frequency selector. Manual triggers let you run workflows on-demand from the GenMB interface, which is great for testing or one-off automations.

Each trigger passes data to the first node. Webhook triggers pass the request body; schedule triggers pass the current timestamp and run metadata.

Node Configuration

Each node type has its own configuration panel. Understanding the key settings helps you build reliable workflows.

Variable interpolation

Use double curly braces to reference data from previous nodes. For example, {{trigger.body.email}} accesses the email field from the webhook payload. {{node_1.output.status}} accesses the output of node 1.

Error handling with conditionals

Add a conditional node after HTTP Request nodes to check for error responses before proceeding. This prevents cascading failures when an external API returns an error.

Execution time limits

Each workflow execution has a maximum duration of 300 seconds (5 minutes). Workflows that exceed this limit are terminated. Design your workflows to complete within this window — avoid chaining too many delay nodes or calling slow external APIs sequentially. The maximum number of nodes per workflow is 50.

Execution History

Every workflow execution is logged with detailed information about each node. Use the history to debug issues, monitor performance, and verify your automations are working correctly.

View the status of every execution — success, failure, or in-progress. Click any execution to see the full trace. Inspect individual node results including input data, output data, execution time, and any errors that occurred.

Filter executions by status, date range, or trigger type to find specific runs quickly. Failed executions show detailed error messages and the exact node where the failure occurred, making debugging straightforward.

Best Practices

Follow these tips to build reliable, maintainable automation workflows.

Build incrementally

Start simple — build and test one node at a time before adding complexity. Verify each step works before connecting the next. This makes debugging much easier.

Use descriptive names for your workflows and nodes. When you have multiple workflows, clear naming makes management easier. Test with sample data before activating — use the test button to simulate real executions without affecting production data.

Monitor execution history regularly. Set up email notifications for failed executions so you can respond quickly to issues.

FAQs

What are automation workflows?▾

Automation workflows are visual backend logic builders in GenMB. You connect nodes on a canvas to create automated processes — HTTP requests, email notifications, conditional logic, AI processing, and more — without writing backend code.

How do I trigger a workflow?▾

Workflows can be triggered three ways: webhook URLs (send HTTP requests from any service), schedules (run at fixed intervals), or manually from the GenMB interface.

Can workflows call external APIs?▾

Yes. The HTTP Request node can call any external API with configurable methods, headers, body, and authentication. Use data from previous nodes with variable interpolation.

Can I use AI in my workflows?▾

Yes. The AI Processing node sends data through a language model for tasks like classification, summarization, content generation, or data extraction. Configure the prompt and use the output in subsequent nodes.

How do I debug a failed workflow?▾

Open the Execution History tab, find the failed run, and click to inspect it. You'll see the exact node that failed, the input it received, and the error message. Fix the node configuration and re-test.

Ready to build?

Create your first app for free — no credit card required.

Backend Agents Deployment