Describe a recurring task in chat, right inside your own application. That becomes a visible flow, which you approve step by step before it runs. After that, it runs on demand or on schedule, with a full history.
The Agentic Part
An agent reads the description from chat and builds the matching flow from it: which data it queries, how it filters, which document it builds and where it goes. For every step, it keeps the status on record, even when a step cannot run. Nothing is written or sent until you approve that step; after that, the flow keeps running on schedule by itself.
Main Features
- Data structure for tasks, steps, connections, runs and chat logs
- Step types that run in the correct order
- Per-step execution status, including failed steps
- Schedule for automatic background runs
- Chat that turns a description into a flow
- Planning view and run history
Use Cases
- Someone used to rebuild every recurring task by hand in a separate tool. Now you describe it in your own application's chat, the agent builds the flow, and you approve it step by step.
- A report needs filtering, building as a document and mailing out on the first of every month. From then on, the flow runs automatically on schedule, with a full history of every run.
- One step fails to run once because a data source is missing. Its status stays visible, and the rest of the flow keeps running regardless.
- A new recurring task comes up that should update a record. You describe it in chat, review the proposed flow and approve it before it runs for the first time.
What we build for you
- Description of your own data for the planner
- Which step types are available at all
- The layout for documents and exports
- Schedules and triggers
- Approval point before anything is written or sent
