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. 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.
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.
- Start simple — build and test one node at a time before adding complexity. Verify each step works before connecting the next.
- Use descriptive names for your workflows and nodes. When you have multiple workflows, clear naming makes management easier.
- Add error handling with conditional nodes after critical steps. Check for error responses before proceeding to avoid cascading failures.
- 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.