Dagy / Developer documentation
From your first flow
to a working integration.
Dagy lets you define data workflows in Python or on a visual canvas, deploy them to an environment, and start and inspect runs through a CLI or REST API.
Run your first flow
Install the Python SDK and run a small pipeline locally.
Start with PythonConnect your application
Get credentials, deploy a flow, and trigger a hosted run.
Integrate the APIBuild on the canvas
Compose a graph with configured nodes and typed connections.
Explore the builderChoose your starting point
| Your goal | Start here | What you will have |
|---|---|---|
| Understand Dagy | Flows, tasks, and runs | A vocabulary for building and operating a workflow |
| Try it on your machine | Python quickstart | A working flow and a local run you can inspect |
| Integrate an application | Connect to Dagy | Credentials, a deployed flow, and an API-triggered run |
| Compose configured nodes | Visual flow builder | A validated graph and an environment deployment |
| Find a request or response | API reference | Endpoint guides and a downloadable OpenAPI contract |
What you can build
Use tasks to call your application's services, transform records, check data quality, write to a destination, or run an AI model. Pass task results to other tasks to declare dependencies. Start runs on demand, on a schedule, or through an inbound webhook. Inspect task states and logs, then retry or backfill when necessary.
The node catalog describes the provided ingestion, transformation, AI, vector database, and notification nodes. You can also use your own Python libraries. A catalog entry describes a capability and its configuration; credentials, installed packages, network access, and documented runtime limitations still determine whether it will execute successfully.
Understand availability before deploying
These docs describe the implementation in SDK version 0.1.0. Individual hosted capabilities depend on the deployment you use. Cloud-account setup currently supports registration and verification; it does not yet supply credentials to workflow tasks. Saved connector records also do not automatically resolve credentials for node executions. Integration guides explain the working alternatives.
Review limits and constraints and the production guide before moving beyond a development environment. The release information records compatibility notes without implying features have shipped to every hosted deployment.