Thunderbit

Provides a drag-and-drop interface for constructing multi-step automation workflows without code, using a node-based graph model where users connect triggers (webhooks, schedules, form submissions) to actions (API calls, data transformations, notifications). The builder abstracts HTTP requests, DOM interactions, and conditional branching into visual blocks that compile to executable automation sequences, with real-time preview and validation of workflow logic before deployment.

Supports multiple trigger types (webhooks, scheduled intervals, form submissions, API calls) that initiate automation workflows, with each trigger type implementing a distinct activation pattern. Webhook triggers expose unique URLs that accept POST requests; scheduled triggers use cron-like expressions for time-based execution; form triggers capture HTML form submissions; API triggers respond to incoming REST calls. The system queues triggered events and executes associated workflows asynchronously with configurable retry logic.

Provides pre-configured connectors for a limited set of third-party services (email, Slack, Google Sheets, Zapier, etc.) that abstract away API authentication, request formatting, and response parsing. Each connector exposes service-specific actions (send email, post message, append row) through the visual builder without requiring users to construct raw HTTP requests. Connectors handle OAuth 2.0 flows, API key management, and rate limiting transparently, storing credentials in encrypted vaults.

Enables users to transform and map data flowing between workflow steps using a visual data mapper that supports field selection, basic transformations (concatenation, case conversion, date formatting), and conditional value assignment. The mapper generates transformation logic that extracts fields from upstream step outputs, applies transformations, and passes results to downstream steps. Supports JSON path expressions for nested data extraction and simple templating for string interpolation.

Tracks workflow execution history with detailed logs showing trigger events, step-by-step execution flow, input/output data at each step, and error messages. Provides a dashboard displaying execution status (success, failure, pending), execution duration, and timestamp information. Logs are retained for a configurable period and searchable by workflow, date range, and execution status. Failed executions are flagged with error details to aid debugging.

Allows users to create web forms that automatically trigger workflows when submitted, with form fields automatically mapped to workflow variables. The system generates embeddable form HTML or provides a hosted form URL that captures user input and passes field values to the triggered workflow. Form submissions are validated client-side and server-side before workflow execution, with error messages returned to the user.

Implements automatic retry mechanisms for failed workflow steps with configurable retry counts and exponential backoff delays. When a step fails (API error, timeout, validation failure), the system automatically retries the step after a delay, with each retry increasing the delay interval. Users can configure retry behavior per step or globally for the workflow. Failed steps that exceed retry limits trigger error handlers that can log errors, send notifications, or skip subsequent steps.

Enables users to schedule workflows to execute at specific times or intervals using cron expressions or a visual schedule builder. Supports common scheduling patterns (daily, weekly, monthly) with a UI that abstracts cron syntax for non-technical users. Scheduled workflows execute asynchronously at the specified time, with execution logs recorded for audit and debugging. Timezone handling is supported for scheduling across different regions.

Tracks workflow versions as users make changes, allowing rollback to previous versions if needed. Each workflow modification creates a new version with timestamp and change metadata. Users can deploy specific versions to production or keep workflows in draft mode for testing. The system maintains a version history accessible through the UI, enabling users to compare versions and understand what changed between iterations.

Allows workflows to branch execution based on simple conditional logic (if/then/else) evaluated against step outputs or trigger data. Conditions support basic comparisons (equals, contains, greater than) on string and numeric values. When a condition is true, the workflow follows one branch; when false, it follows an alternative branch or continues to the next step. Conditions are configured visually without requiring code.