Support Hub
Report a bug or request a feature from inside Dave with the screen context attached, or email the team if you cannot reach your workspace at all.
Open the Support HubStart a 30-day free trial for up to five seats, no infrastructure to stand up first. Add your AI provider keys to the encrypted vault, invite your team, then drag nodes onto the canvas to build your first workflow; most people are live the same afternoon.
Report a bug or request a feature from inside Dave with the screen context attached, or email the team if you cannot reach your workspace at all.
Open the Support HubEverything HelloDave.ai publishes about Dave, gathered in one place: the guides, the blog and three worked examples, plus the discussion boards when they open.
Visit the communityNew to Dave? Start with the How It Works guide to understand the core concepts, then build your first workflow.
Read How It WorksNeed help? Reach us at support@hellodave.ai.
Email supportWhat a workspace looks like when you sign in, and the help centre that ships inside it.
Nine steps from an empty workspace to a completed run. Each one is a real click path in the product.
Go to Admin, then API Management, then Providers, and click Add Provider. Name it, pick the provider type, add the base URI and the credential to authenticate with. Your key goes into the encrypted vault and is never returned through the API once saved.
Guide: Add an AI providerGo to Agents and click Create Agent. Name it and describe what it does, then open it and add a version carrying its system prompt, the model to run on, and a temperature. The version is the unit you roll back to later.
Guide: Create an agentGo to Workflows and click Create Workflow. Give it a name that describes the process rather than the mechanism, then open the workflow editor.
Guide: Create a workflow and make it activeDrag nodes from the palette onto the canvas and connect them in the order the work happens. A first workflow is usually Start, then User Interaction to collect input, then Agent Interaction, then Human Review, then End. Save a version when the shape is right.
Guide: Build your first workflowGo to Instances and click Create Instance. Pick your workflow and the version to run, then start it. An instance is one live execution, tracking its own data and progress.
Guide: Launch an instanceGo to Tasks. The User Interaction node has created a task waiting in the inbox. Open it, read the payload to see what the workflow is asking for, enter your input and submit.
Guide: Work a task from your inboxThe engine calls your agent automatically, on the provider and model that agent is pinned to. Nothing to do here. When it finishes, the review task appears.
Guide: Watch a run and read its timelineOpen the review task, read what the agent produced, and approve, reject or request changes. Add a comment saying why: it is optional, but a rejection nobody explained is one the next person has to guess at.
Guide: Work a task from your inboxBack in Instances, the run shows as completed, and the dashboard counts update. Every agent call, field change and human decision along the way is in the audit log.
Guide: Watch a run and read its timelineShort, task-level walkthroughs of the things people do most often, drawn from the in-product help centre.
Create the provider record every agent calls, store the API key once, and pull in the model catalogue. About five minutes.
Read the guideCreate an agent, give it a version carrying its prompt and model, and see why versions are retired rather than edited. About five minutes.
Read the guideCreate the record, learn what draft actually stops you doing, and activate it so it can be run and scheduled. About four minutes.
Read the guideOpen the editor, drag nodes from the palette onto the canvas, connect them, and save a version. About five minutes.
Read the guideCreate a run from an active workflow version, start it, and read the list to see what it is waiting on. About four minutes.
Read the guideFilter the inbox, read the payload a workflow sent you, and approve, reject or request changes. About four minutes.
Read the guideTell which step a run is on, how long it has taken, and what it is waiting for. About four minutes.
Read the guidePut a workflow on a daily, weekly or monthly schedule so nobody has to start it. About four minutes.
Read the guideCreate a field, pick its type and scope, and decide whether a workflow must fill it in. About four minutes.
Read the guideRegister a connection, pick the narrowest preset, and wire it into Claude Code, Claude Desktop, VS Code or JetBrains. About six minutes.
Read the guideRecurring runs sit on a calendar, so an operator can see what is due and what just ran.
No formal training is required. The builder is visual and drag-and-drop; the How It Works guide covers the core concepts before you build your first workflow.
Add them in the credential vault, where they're encrypted with AES-256 and never returned through the API. You then select a stored credential when configuring an agent or an API Call node.
Six built-in, tenant-scoped roles: Admin (full administration), Create (build and manage AI agents), Curate (design workflows in the visual editor), Use (run instances and complete tasks), Reporting (analytics only, no edit access), and Financial (billing and subscription management).
Yes. An instance can be scheduled from the calendar, triggered via the API, or kicked off manually, and running instances always use the current workflow version.
Visit support.hellodave.ai for documentation and tutorials, or email support@hellodave.ai directly.