Licence
MIT
Version
1.0.4
Deps
0
Size
66 kB
Vulns
0
Weekly
0
n8n-nodes-daize-flow
n8n community node for Daize Flow. Talk to a workspace's REST API directly instead of wiring up HTTP Request nodes by hand.
Installation
Self-hosted n8n:
- UI: Settings → Community Nodes → Install →
n8n-nodes-daize-flow - Manual:
npm install n8n-nodes-daize-flowinside~/.n8n/(or yourN8N_CUSTOM_EXTENSIONSpath), then restart n8n.
Credentials — Daize Flow API
| Field | Example | Notes |
|---|---|---|
| Workspace URL | https://acme.daize.app |
Your workspace subdomain. /api/v1 is appended automatically. |
| API Key | dz_… |
A workspace API key, sent as Authorization: Bearer <key>. |
The credential test calls GET /api/v1/entities.
If n8n runs in Docker against a local Herd site (
*.daize-flow.test), the container must be able to resolve and reach that host.
Resources & operations
| Resource | Operations |
|---|---|
| Entity | Get, Get Many |
| Record | Create, Get, Get Many, Update, Delete |
| Workflow | Create, Advance, Complete, Get Many, Update |
| File | Upload |
- Record / Workflow data is passed as a JSON object of field keys to values (
{ "name": "Acme", "amount": 42 }). - Entity and Workflow Type are picked from dropdowns loaded from the API; the Workflow ID (for Advance/Complete/Update) is entered manually.
- File → Upload sends the selected input binary field as multipart
fileand returns{ id, name, mime_type, size, url }. Reference the returnedidin a record/workflow file or image field. - Get Many supports
Return All(auto-paginates) or aLimit, plus search/sort/filter options.
Development
npm install
npm run build # tsc + copy icons into dist/
npm run dev # tsc --watch
The n8n key in package.json points n8n at the compiled dist/ credential and node.