Know what happened
Filter runs by status, workflow, date, and order. Inspect every step, attempt, input, and sanitized output from one timeline.
Webhooks · schedules · polling
Build workflows that keep moving.
Trigger work from an event, a schedule, or a changing API. Shape the data, connect your tools, and follow every step from first run to final result.
3 trigger types10 action blocksReplayable runs
API change alert
Published · Version 4
When the API changes
Polling
response
Shape the payload
Transform
result
Notify the team
Slack
248
runs
99.2%
success
1.4s
median
How it works
From signal to outcome, in one clear flow.
Start with a ready-made template or build from scratch. Dynamic fields carry data from one step into the next.
01
Choose a trigger
Receive a webhook, run on a schedule, or watch an API for changes.
02
Build the flow
Add integrations and logic, then map data with simple template fields.
03
Publish and observe
Run asynchronously, inspect each attempt, and replay when needed.
Start your way
More than webhook automation.
React instantly, run recurring work, or turn an API change into the beginning of a workflow.
Webhook
Start instantly from a secure JSON endpoint unique to each workflow.
Schedule
Run recurring jobs on the interval that fits your process.
Polling
Watch an HTTPS API and continue only when its response changes.
Integrations and actions
Connect the tools your workflow needs.
Reuse encrypted connections for SMTP and HTTP, or connect Slack and Google with OAuth.
Send dynamic messages through a reusable SMTP connection.
HTTP Request
Call external HTTPS APIs with mapped workflow data.
Slack
Post messages to channels through a connected workspace.
Google Sheets
Append structured workflow results to a spreadsheet.
Solana
Transfer devnet SOL from an encrypted per-account wallet.
Workflow logic
Shape what happens between apps.
Filter
Continue only when your condition is true.
Branch
Choose a path from workflow data.
Transform
Reshape values for the next action.
Delay
Pause execution before continuing.
Loop
Run an action for every item in a list.
Operations included
Built for the run after “publish.”
Building is only half the job. FlowForge gives you the history and recovery tools to operate every workflow.
Retry with confidence
Leased workers, exponential retries, transactional delivery, and a dead-letter queue keep failures visible and recoverable.
Replay the right version
Published definitions are snapshotted with every run, so a replay uses the exact workflow version that originally executed.
Encrypted
Stored connection secrets
Ordered
Stage-by-stage execution
Idempotent
Duplicate-safe webhooks
Redacted
Sensitive run data
Ready when you are
Turn the next signal into a workflow.
Start from a template, connect your apps, and publish a workflow you can actually observe.
Start building →