Search the box above for a task, a setting, or the exact error message you are looking at. Everything below is the same content, organised by what you are trying to do.
Start here
Build your first workflow takes about 20 minutes, needs no credentials, and ends with a real run you can open. If you have not built anything in Hodoflow yet, start there — the rest of these pages assume the vocabulary it teaches.
Browse by what you are doing
| I want to… | Go to |
|---|---|
| Make something run on a schedule, a webhook, or a message | Workflows |
| Set up a key, a connector, or machine access | Credentials and connections |
| Keep what a workflow produced, and chart it | Data and dashboards |
| Ask one question of those records, and download the answer | Run a report |
| Find out why a run failed, and fix it | Run and troubleshoot |
| Add people, set roles, or split environments | Account and access |
Popular tasks
- Build your first workflow — the complete path, with nothing to set up first.
- What you need before you build — the matrix that stops a wizard blocking you halfway.
- Send data into Hodoflow with a webhook — service account, trigger, and one authenticated POST.
- Activation errors — every message activation can refuse with, searchable.
- Recover a failed run — retry from the failing step without repeating what succeeded.
- Connection and authentication errors — what a failing connector or rejected credential is telling you.
What Hodoflow is
A workflow-native data platform. Data arrives from the systems you already run — webhooks, message streams, scheduled API calls — visual workflows clean and reshape it, and the results land in a warehouse your dashboards read from in real time.
The whole product is one loop with three stages:
- Ingest. Something outside Hodoflow sends data in, or a workflow goes out and fetches it. Either way, what arrived is recorded exactly as it arrived.
- Map. A workflow you drew on a canvas pulls that payload apart, calculates the fields you actually want, and maps them onto the business entities you care about — orders, customers, tickets.
- Analyze. The mapped results become an append-only history, and dashboards recompute the moment new data shows up.
No glue code and no SQL anywhere in that loop.
Product map
The left sidebar of the app is the whole product.
| Section | What it is for |
|---|---|
| Home | Opens on Overview — workflow run states and data model activity for a time range you choose, plus recent throughput. |
| Dashboards | Your dashboards, and the widgets on them that update live as data lands. Widget Library holds standalone widgets you can reuse across dashboards or embed elsewhere. Reports are saved questions you run on demand and download. |
| Workflows | The visual builder and every workflow you have saved, with its versions. Monitor is the live run history. |
| Warehouse | Your data models and the records mapped into them. Every record keeps its full change history. |
| Connectors | Integrations between your organization and outside services. Inbound is for external services sending data to Hodoflow, Outbound for credentials Hodoflow uses when it calls out, and API Specs for OpenAPI descriptions you have imported. |
| Settings | Organization, Workspaces, Users, and Service Accounts. |
Press Cmd/Ctrl + K anywhere in the app — or click the search bar in the
top bar — to jump straight to a workflow, dashboard, data model, connector,
widget, or person.
Everything you create belongs to the workspace named beside your organization in the top bar. Switching workspaces switches the whole app to a different set of workflows, dashboards, and data.
Still stuck
- Check Settings → Organization first if something was refused. Most surprising refusals are a plan limit, and that page names which one.
- Email support@hodoflow.com with the exact message you saw, the workflow or dashboard name, and roughly when it happened. Run ids from Monitor are the fastest thing to give us.
- Trial ending, or want to move a demo organization to production? Same address — see Organizations and trials.
Building against the API
Every page here is also served as plain markdown, so an assistant can read the
same documentation you do. Append .md to any page URL.
If you are integrating rather than clicking, the developer portal covers the JSON API, the GraphQL endpoint, authentication, and webhook ingestion.