YOUR OPERATIONS, CONNECTED
From event
to outcome.
In one place.
Connect your systems, automate the work, and give every record a history. Bring it all into live dashboards — and the AI tools you already use.
Built for the way your business runs.
- 1 Order receivedReceive a request 38 ms
- 2 Save orderMap to a data model 112 ms
- 3 Ready to fulfil?Choose a path 4 ms
- 4 Run fulfilmentRun another workflow 1.4 s
- 5 Send order to ERPCall an API operation 402 ms
- — Queue for reviewTaken when the order is not ready Not run
- Step
- Send order to ERP
- Type
- Call an API operation
- Status
- Succeeded
- Duration
- 402 ms
Orders per day · last 7 days
- 13
- 14
- 15
- 16
- 17
- 18
- 19
| Order | Customer | Value | State |
|---|---|---|---|
| SO-4821 | Northwind Foods | $1,284.50 | Fulfilled |
| SO-4820 | Arrow Components | $612.00 | Needs review |
| SO-4818 | Harbour Supply | $3,940.25 | Fulfilled |
| SO-4817 | Delta Workshops | $188.75 | Fulfilled |
01 WORKFLOWS
Move the data.
Make the call. Tell someone.
A workflow is your process, drawn out on a canvas and running on a schedule or a webhook. Pick a step to see what that part of it does.
-
Pull data in
Fetch new orders
Call an API, read a Snowflake table, or pick up a file from S3. Import an OpenAPI spec and its operations become steps you can point and click.
-
Reshape it
Save as orders
Map fields, filter lists, and iterate over records. Formulas and typed data models turn an awkward payload into records the rest of your work can rely on.
-
Branch and wait
Ready to fulfil?
Conditions choose the path, and nest when the logic gets real. Delays hold a run until it is time to carry on.
-
Build once, reuse
Run fulfilment
Package a sequence as a subflow with its own inputs and outputs, then call it from every workflow that needs the same thing done.
-
Send it on
Send orders to the warehouse
Write the result back where it belongs — another API, a Snowflake table, a file in S3 — so the systems your team already uses stay current.
-
Tell someone
Email the operations team
Send an email, or post into Slack, Teams, or Discord, when a run turns up something a person needs to look at.
An order that is not ready takes the other path, and the run holds it for review instead.
MONITORING & RECOVERY
A clear view of every run.
See what happened, find the step that needs attention, and keep work moving.
Read the run, step by step
Follow live runs, inspect each step's status and timing, and see where a failure started.
Retry on your terms
Set retries and delays per step, route failures down an error path, and retry the run once the other side is back.
Test before you activate
Try a step against sample values and pin its output while you work on what comes next. Going live stays a deliberate click.
02 THE WAREHOUSE
Every record has a story.
Keep the whole timeline.
A shared home for the data your workflows collect. Give it structure, follow its history, and turn it into answers your team can use.
Give your data a consistent shape
Define typed data models for orders, customers, or the records your business runs on. Map incoming fields into that shared structure so workflows, reports, and dashboards use the same data.
Follow the timeline, version by version
See a record as it stands now and follow its change history. Select an earlier version to inspect what changed and what the record looked like at that point in time.
Turn records into repeatable reports
Filter, group, and aggregate warehouse data into saved reports. Run the same question again as new records arrive, then download the results as CSV, JSON, Excel, or PDF.
Change history 5 versions
-
2 min ago
~ status
fulfilling→ fulfilled + shipped_at 14:02 -
41 min ago
~ status
pending→ fulfilling -
1 hr ago
~ items
11→ 12 ~ total$1,180.00→ $1,284.50 -
2 hr ago
~ status
received→ pending - 3 hr ago created
WarehouseOrdersSO-4821 EXAMPLE
As of Now
- order_id
- SO-4821
- customer
- Northwind Foods
- items
- 12
- total
- $1,284.50
- status
- fulfilled
- shipped_at
- 14:02
Explore the example: select a version to see the record at that moment.
03 DASHBOARDS
The whole picture.
Always moving with you.
Build a view around the way your team works. Reusable widgets turn live warehouse data into dashboards you can share or embed.
Dashboards made from reusable widgets
Arrange KPI tiles, charts, tables, and maps on a canvas. Save widgets to your library and reuse them across dashboards, with time ranges and filters to focus on the question at hand.
Live data, without the refresh routine
As workflows write records to the warehouse, connected widgets update. Your team can follow the same changing picture, from the headline number down to the underlying records.
Share a view. Embed it anywhere you work.
Publish a read-only link, or embed a whole dashboard — or a single widget — in your own app. Shared views stay live, and you can turn off public sharing when a view is no longer needed.
Order operations
Your data, together in one place.
Orders by customer · last 30 days · example data
| Order | Customer | Value | State |
|---|---|---|---|
| SO-4821 | Northwind Foods | $1,284.50 | Fulfilled |
| SO-4820 | Arrow Components | $612.00 | Needs review |
| SO-4818 | Harbour Supply | $3,940.25 | Fulfilled |
| SO-4817 | Delta Workshops | $188.75 | Fulfilled |
Explore the example: change the time range to update the view.
04 INTEGRATIONS
Your stack.
Working together.
Connect the services behind your business, from the first incoming event to the last update sent back.
Connect the systems you already use
Bring in events through webhooks, call HTTP APIs, read and write Snowflake tables, and work with files in S3. Send updates to Slack, Teams, Discord, or email as part of the same workflow.
Turn an API spec into usable operations
Import an OpenAPI or Swagger specification to discover endpoints and their inputs. Choose an operation in the workflow builder and map the values it needs, without reconstructing every request by hand.
Keep authentication with the connection
Configure credentials once and reference the connection from your workflows. API keys, bearer tokens, and OAuth 2.0 support different services, while encrypted secrets stay out of your workflow definitions.
BRING YOUR SYSTEMS TOGETHER
HodoflowConnect once. Build on it.
Credentials managed with each connection
05 MCP & YOUR AI
Your AI. Your context.
Connected to the work.
The Model Context Protocol connects your preferred AI assistant to Hodoflow's tools and data, with access you control.
Bring your own AI client
Connect an MCP-compatible assistant to Hodoflow. Keep using the AI environment you prefer and give it a structured way to discover your workspace and work with your operations.
Go from a question to useful tools
Discover workflows, inspect runs, query warehouse records, and work with dashboards. Authoring tools also let your assistant help build workflows and widgets using the platform's own operations.
Connect with your existing permissions
Use a personal access token to let your assistant act as you across the organizations you belong to. Your existing permissions apply, and you can rotate or expire the token from your profile.
BRING YOUR OWN AI
“Show me the workflow runs that need attention.”
Your Hodoflow workspace
Your client. Your credentials. Your permissions.
CONNECT. AUTOMATE. UNDERSTAND.
Make your next move
a connected one.
Look around a demo organization, or tell us what you are trying to join up.