Ready-made flows

Complete agents to download and import on the platform: the canvas, the JSON and the explanation of why each card is there.

Updated on Sep 02, 2026

Each flow below is a complete agent, exported from the platform and ready to import: download the file, import it, adjust what's yours, and publish. Each one's page shows the canvas, the JSON, and — the part that matters — why each card is there and what it solves.

They're real starting points, not fragments: you can import, run, and keep changing.

Company operations

Agents that talk to your system: query, record, and act, with your authenticated API on one side and your knowledge base on the other.

Support with schedulingReal case: 7 API routes + knowledge base. The agent that actually schedules.View the flow Support with ticketsRAG to answer + 5 authenticated routes to open and track tickets.View the flow Post-sale with approvalFree read, write under approval. The standard for an agent that touches orders.View the flow Passwordless identificationChannel link by single-use code + PII gatekeeper. Passwordless identity in conversation.View the flow Scene directorVideo with narrative: opening frame → closing frame → interpolated clip, all by conversation.View the flow ProspectorSearch for people and B2B leads (LinkedIn, Maps, websites) with async jobs and progress alerts.View the flow

Builder patterns

Short flows, each isolating one piece: routing, approval, sequence, tool pipeline, loop. They help you understand the mechanism and paste into a larger flow.

Support triageRouter → support or sales. The starting point of any support center.View the flow Human approvalThe flow pauses, waits for a person's "go ahead" and only then executes.View the flow Assembly lineDraft → review → title, in sequence, inside a single Sequential card.View the flow Page extractorTool pipeline: fetch the page, structure the result, save context.View the flow Loop refinementWhile loop: iterate N times over the result itself before delivering.View the flow

How to import

1
Download the flow file
Each page has the .hinow-agent.json download button.
2
On the platform, open Agents → Import
Choose the file. The agent enters as new draft — nothing you already have is changed.
3
Fill in what belongs to your environment
Webhook credentials (come masked), your API URLs and knowledge bases (the link comes empty: bases don't cross environments).
4
Test in sandbox
Run in the editor itself and track tool calls before publishing.
5
Publish
Only the published version responds on /run.

What the file contains

It's the same envelope that the platform's Export button generates:

estrutura do .hinow-agent.jsonjson

{
  "format": "hinow.agent",
  "version": 1,
  "exported_at": "2026-09-01T00:00:00Z",
  "credentials_included": false,
  "agent": {
    "name": "...",
    "description": "...",
    "model": "...",
    "system_prompt": "...",
    "config": { },
    "workflow": { "nodes": [ ], "edges": [ ] }
  }
}

Import details	Behavior
Always creates draft	The imported agent is born as `draft`, private, in the current project — never overwrites an existing one.
Duplicate name	Becomes `Name (imported)`, `Name (imported 2)`…
Credentials	Sensitive keys come out of the file masked. Fill in after importing.
Knowledge bases	`rag_ids` comes empty: a base from the source environment doesn't exist in yours.
Observability IDs	Renewed on import — your agent's metrics don't mix with anyone else's.
Limits	Up to 200 nodes and 500 connections per file.

Test before the API is ready

In flows with Webhook, swap the baseUrl for https://httpbin.org/anything and publish: the agent runs for real and each route returns the echo of the request itself — method, URL, query string, body and headers. It's the fastest way to check if the {{parameters}} are arriving as you expect before pointing to your system.

Example credentials

The files bring PASTE_YOUR_TOKEN_HERE in place of the secret, on purpose. Before publishing, fill in the Webhook card authentication — and read Credentials and identity to choose the right standard for your case.

Prefer to build from scratch?

Start with My first agent and use the Builder cards as reference for each piece.

Create and manage by API

The same flows can be created by REST: `POST /v1/agents` with the workflow JSON.

Agents by API Builder cards

Was this page helpful?