Getting Started
Aurel lets you design backend workflows visually. You combine trigger nodes, action nodes, and branching logic, then execute and monitor each run from one place.
- Create a workflow from the home terminal or dashboard.
- Add a trigger node (for example webhook).
- Chain action nodes (HTTP request, email, set values).
- Use filter/branch nodes to route true vs false outcomes.
Core Concepts
Every workflow run is deterministic based on node inputs and previous outputs. Keep node configs small, explicit, and testable.
- Workflow: a graph of connected nodes.
- Execution: one run instance of that workflow.
- Node output: data produced by a node for downstream steps.
- Branching: conditional path selection from filter logic.
Node Types
Build most automations using a small set of composable nodes.
- Webhook: starts a run from external systems.
- HTTP Request: calls APIs with request configuration.
- Set: transforms and stores intermediate values.
- Filter: applies conditions to split execution paths.
- Send Email: sends notifications from run outcomes.
Executions & Monitoring
Use the executions view to debug failures and verify expected outcomes.
- Inspect run status and timestamps.
- Review per-node outputs and errors.
- Track branch decisions for auditability.
- Re-run workflows after config changes.
Webhooks & API
Webhook endpoints trigger workflows directly. You can also create workflows programmatically from API routes.
- Use workflow webhook URLs for inbound event triggers.
- Keep webhook secret values private.
- Validate incoming payloads before branching.
- Prefer idempotent downstream actions where possible.
Best Practices
These patterns improve reliability as workflows scale.
- Name workflows and nodes with domain language.
- Keep each node focused on one responsibility.
- Surface terminal errors with actionable messages.
- Add branch guards before expensive or external operations.
Troubleshooting
If a workflow fails, isolate where input, transform, or action diverged.
- No run triggered: verify webhook route and secret.
- Branch mismatch: inspect filter conditions and input shapes.
- Action failed: inspect HTTP response and auth headers.
- Missing data: confirm upstream node outputs and mapping keys.