Building Better Bots: Composing Agentic Workflows with function.do

Developing intelligent, automated agents requires breaking down complex tasks into manageable, reusable pieces. On the .do platform, this fundamental building block is known as a function.do. This concept is key to creating robust and scalable agentic workflows.

What is a function.do?

At its core, a function.do is an atomic, composable unit of business logic. Think of it as a single, well-defined action or piece of processing that your agent can perform. Instead of monolithic blocks of code, you create focused functions that do one thing well.

This atomic nature provides several key benefits:

• Reusability: Once defined, a function.do can be used across multiple agents and workflows. This promotes efficiency and reduces code duplication.
• Maintainability: Small, focused functions are easier to understand, debug, and update.
• Composability: Just like building with LEGO bricks, you can chain and combine multiple function.do to create more complex logic and workflows.
• Testability: Each function can be tested in isolation, ensuring its reliability before integrating it into larger systems.

Encapsulating Business Logic

The power of function.do lies in its ability to encapsulate specific business logic. Whether it's fetching data from an external API, processing a customer request, or performing a calculation, each task can be defined as a distinct function.

This approach aligns perfectly with the principles of "business as code," where your operational logic is directly represented and executed within the platform.

Defining a function.do

Defining a function.do on the .do platform is straightforward. You leverage familiar programming languages like TypeScript or JavaScript and utilize the .do SDK to wrap your logic. Here's a simple example:

export const createService = agent(async (input: { name: string, description?: string }) => {
  // Logic to create a new service
  const newService = {
    id: generateId(), // Assuming generateId is a helper function
    name: input.name,
    description: input.description || '',
    createdAt: new Date()
  };
  console.log(`Created service: ${newService.name}`);
  return newService;
});

In this example, createService is a function.do that encapsulates the logic for creating a new service entry. It takes specific input (the service name and optional description) and returns the newly created service object.

Powering Agentic Workflows

function.do serves as the foundation for building sophisticated Agentic Workflows. By composing these atomic functions, you can define the step-by-step processes that your agents execute. For instance, a customer support agent might chain functions for:

1. Receiving and parsing a customer inquiry.
2. Looking up customer history (using a function.do for data retrieval).
3. Identifying the issue (potentially using a function.do for natural language processing).
4. Troubleshooting the problem (composing multiple function.do for different potential solutions).
5. Responding to the customer (using a function.do for sending communications).

The .do platform provides the orchestration layer to manage these compositions, ensuring seamless execution and allowing you to visualize and refine your workflows.

Where are function.do Executed?

Once defined, function.do are deployed and managed directly within the .do platform. This provides a centralized environment for your business logic, making them:

• Easily Discoverable: Functions can be categorized and searched for within the platform.
• Scalable: The platform handles the execution environment, allowing your functions to scale based on demand.
• Secure: The .do platform provides a secure environment for running your business logic.

Get Started with function.do

Ready to start building with atomic, reusable logic? Explore the .do platform and begin defining your own function.do to power your next-generation agentic workflows.

FAQs

What is a function.do?

A function.do represents a single, atomic unit of business logic within the .do platform. It's a core building block for creating more complex agents and services.

How do I define a function.do?

You define function.do using standard programming languages like TypeScript or Javascript, leveraging the .do SDK to encapsulate specific business logic.

Can function.do be combined?

Yes, multiple function.do can be composed and chained together using the .do platform's orchestration capabilities to create comprehensive Agentic Workflows.

Where are function.do executed?

function.do are deployed and managed within the .do platform, making them easily discoverable, executable, and scalable.