In today's fast-paced digital landscape, businesses rely on a constellation of specialized SaaS applications. Your payment processing lives in Stripe, your team communication in Slack, your customer data in Salesforce, and your marketing in Hubspot. While each tool is powerful on its own, their true potential is only unlocked when they work together. The challenge? Connecting them is often a complex, brittle, and time-consuming process of writing custom glue code, managing webhooks, and juggling API keys.
What if you could orchestrate these multi-service interactions as a single, coherent, and version-controlled workflow? This is the promise of Business-as-Code, and it's precisely what you can achieve with the .do SDK. By leveraging agentic workflows, you can transform fragmented processes into powerful, automated Services-as-Software.
Before we dive into integrations, let's clarify the core concept. An agentic workflow, in the context of the .do platform, is a sequence of defined steps that an autonomous "agent" executes to complete a business process.
By defining your processes this way, you're practicing Business-as-Code. Your company's operations become as robust, testable, and scalable as your core application code.
Connecting disparate APIs is where the agentic workflow model truly shines. The .do Typescript SDK provides a radically simpler and more robust way to build and manage these connections.
Instead of a tangled mess of asynchronous calls and callback functions, a .do workflow is a simple, declarative list of steps. This makes the entire integration flow easy to read, understand, and maintain.
Your entire integration logic lives in your Git repository. It's version-controlled, peer-reviewed, and deployed as part of your standard CI/CD pipeline. This brings a professional software development lifecycle to what has traditionally been an ad-hoc process.
The SDK is designed for developers. If you know Typescript, you have everything you need to start building. Enjoy the benefits of static typing, autocompletion in your favorite IDE, and a rich ecosystem of tools you already use.
One of the biggest hurdles in API development is testing. The .do SDK includes a complete local testing environment and mocking utilities. You can simulate a Stripe webhook, mock the Slack API response, and debug your entire workflow on your machine before a single line is deployed.
Let's build a classic integration: posting a notification to a Slack channel every time a new customer subscribes via Stripe.
Traditionally, this involves:
With the .do agentic workflow SDK, the process is dramatically simplified.
import { Agent, Workflow } from '@do-sdk/core';
// Define a workflow to handle new Stripe subscriptions
const notifyOnNewSubscription = new Workflow({
name: 'stripe.subscription.created',
steps: [
// Step 1: Use the Stripe event data to get full customer details
{
do: 'stripe.customer.retrieve',
input: '{{ trigger.body.data.object.customer }}'
},
// Step 2: Use the retrieved data to post a formatted Slack message
{
do: 'slack.message.post',
channel: '#sales-feed',
text: '🎉 New Pro Subscription! Customer: {{ steps.0.output.name }} ({{ steps.0.output.email }}) just signed up!'
},
],
});
// Create an agent to handle Stripe events
const stripeAgent = new Agent({ workflows: [notifyOnNewSubscription] });
// To run locally for testing:
// await stripeAgent.execute('stripe.subscription.created', { body: mockStripeEvent });
This pattern is infinitely extensible. You can chain together any number of services to automate complex business processes:
With the .do SDK, you're not just connecting apps; you're composing new, powerful Services-as-Software from the building blocks you already use.
Ready to stop wrestling with glue code and start building robust, scalable integrations?
Get started with the .do SDK today. Install the package via npm install @do-sdk/core and check out the documentation to turn your most complex business processes into clean, powerful code.