The promise of agentic workflows is the ability to automate and streamline complex processes. At the heart of building these sophisticated systems lies the fundamental concept of the "atomic function." On the .do platform, functions aren't just abstract code blocks; they are the concrete, reusable, and composable building blocks that power your "services-as-software" vision.
Think of a function on .do as a single, perfect piece of a puzzle. It has one specific job, it does it efficiently, and it's clearly defined by what it needs (inputs) and what it produces (outputs). This atomicity is key:
Unlike monolithic applications where functionality is often intertwined, .do emphasizes discovering and utilizing these small, potent units of work.
The real magic happens when you start composing these atomic functions. Because each function adheres to a clear input/output structure, they can be seamlessly chained together. The output of one function can become the input for the next, creating a fluid flow of data and execution.
Imagine building a complex sales automation workflow. You might have separate functions for:
Each of these is a single, atomic function. By composing them in sequence, you create a complete, automated sales process – a tangible "service-as-software." This composability allows you to:
A core tenet of the .do platform is the emphasis on reusable components. Once you've defined and deployed a function, it becomes a discoverable resource on the platform, available for use in any agentic workflow. This drastically accelerates the development of new services and applications.
Consider the example JSON definition of a simple "sum" function:
{
"name": "sum",
"description": "Adds two numbers",
"inputs": {
"a": "number",
"b": "number"
},
"outputs": {
"sum": "number"
}
}
This function, once defined, can be used anywhere you need to add two numbers – whether it's within a complex financial calculation workflow or a simple utility service. This "business as code" approach means your functional logic becomes a shareable, valuable asset within your organization or community.
On the .do platform, every function inherently acts as an API endpoint. Each function has a unique identifier and a clear definition of its interface (inputs and outputs). This means your functions are immediately accessible programmatically, allowing them to be integrated into other applications, systems, or even consumed via generated SDKs. This seamless integration capability further solidifies the "services-as-software" paradigm.
Getting started with composing agentic workflows on .do begins with identifying the fundamental, atomic steps in your process. Break down the larger task into its smallest logical units. Then, define each of these units as individual functions with clear inputs and outputs.
The platform provides the tools to then graphically or programmatically chain these functions together, defining the flow of data and execution and building your first composable, agentic workflow.
Q: What does it mean for a function to be 'atomic' on .do? A: Functions on .do are atomic, meaning they perform a single, well-defined task. They are the smallest, most fundamental units of work within an agentic workflow.
Q: Can I reuse functions across different workflows? A: Yes, functions on .do are designed to be highly reusable. Once defined, a function can be incorporated into multiple different agentic workflows, reducing redundancy and promoting efficiency.
Q: How does the composability of functions benefit me? A: Composability means that functions can be combined and sequenced together to create more complex workflows and services. By linking atomic functions, you can build sophisticated business processes.
Q: Can you give me an analogy for how functions work in a workflow? A: Think of functions as the steps in a recipe. By combining these individual steps (functions), you can create a complete meal (a bundled service or application). Each function does one specific thing simply and elegantly.
Q: How do functions handle data and information exchange? A: Functions have clearly defined inputs they accept and outputs they produce. This structure makes them predictable and easy to integrate into larger workflows, ensuring compatibility and smooth execution.
Start exploring the power of atomic, composable functions on .do today and begin building your own agentic workflows and services-as-software. They are the essential building blocks for the future of automation and business as code.