Seamless Integration: How to Connect service.do With Your Existing Tech Stack

In today's fast-paced digital landscape, the promise of a new tool is often met with a healthy dose of skepticism. The biggest hurdle? Integration. A revolutionary platform is only as good as its ability to communicate with the systems you already rely on. Adding another silo is a step backward, not forward.

This is where service.do changes the conversation. We didn't build a platform you have to work around; we built a platform designed to plug into your work. Our core philosophy of Services as Software means that every automated business process, every agentic workflow, is treated like a first-class API.

This isn't about ripping and replacing your current stack. It's about enhancing it. It's about turning your complex business operations into simple, programmable endpoints that your existing applications can call on demand. Let's explore how you can seamlessly connect service.do with the tools you use every day.

The service.do Philosophy: API-First by Design

Before we dive into the code, it's crucial to understand why integration is so effortless. On the service.do platform, a "Service" isn't a vague concept—it's a complete business process encapsulated as a programmable API.

Whether it's lead qualification, financial report analysis, or customer onboarding, you define the steps, tools, and AI agents involved. The platform then instantly deploys it as a secure, scalable API endpoint. This Business as Code approach means that from day one, your operations are designed for interoperability.

There are no complex adapters to build or clunky UIs to navigate. If your system can make an HTTP request, it can leverage the power of service.do.

Your Integration Toolkit: The doClient SDK

While you can interact with any service via a standard REST API call, the easiest way to get started is with our lightweight SDKs. They handle authentication, error handling, and data serialization, letting you focus on the logic.

Here’s a simple example using our TypeScript SDK to invoke a data enrichment service.

import { createDo } from '@do-sdk/core';

// Initialize the .do client with your API key
const doClient = createDo({ apiKey: 'YOUR_API_KEY' });

// Get a handle to the service you want to use
const dataEnrichment = doClient.get('data-enrichment.service.do');

// Invoke the service with a specific payload
async function enrichCompanyData(domain: string) {
  try {
    const result = await dataEnrichment.run({
      companyDomain: domain,
      fields: ['logo', 'description', 'employeeCount']
    });

    console.log('Enriched Data:', result);
    return result;
  } catch (error) {
    console.error('Service execution failed:', error);
  }
}

// Run the service
enrichCompanyData('example.com');

Let's break this down:

1. Initialization: We import createDo and initialize a client with our unique API key.
2. Service Handle: We get a reference to the specific service we want to use—in this case, data-enrichment.service.do. This makes your code clean and readable.
3. Invocation: We call the .run() method, passing a payload with the inputs the service requires (here, a company domain and the fields we want).
4. Result: The async function waits for the agentic workflow to complete its tasks and returns a structured JSON object.

This simple pattern is the foundation for all integrations, making it incredibly easy to embed powerful business logic anywhere in your tech stack.

Real-World Integration Blueprints

So, what does this look like in practice? Here are a few common scenarios where service.do can act as the connective tissue for your operations.

1. Supercharge Your CRM (e.g., Salesforce, HubSpot)

Scenario: A new lead fills out a form on your website and is created in your CRM.

Integration:

• Set up a webhook in your CRM to trigger a call to lead-qualification.service.do every time a new lead is created.
• The service.do workflow can:
  • Enrich the lead's data using their email or company domain.
  • Analyze their company size, industry, and role to determine if they are a good fit.
  • Score the lead based on your custom criteria.
• The service then uses your CRM's API to update the lead record with the score and enriched data, and even assign it to the correct sales representative.

2. Power Your Web Application or CMS

Scenario: You want to display up-to-date, dynamic company information on your customer showcase page.

Integration:

• In your backend code (Node.js, Python, etc.), call the data-enrichment.service.do from our code example.
• Pass the domain of the customer whose logo you want to display.
• The service returns the latest company logo, description, and employee count.
• Your application renders this data on the frontend. No more manually updating logos or company details!

3. Automate Your Data & Analytics Pipelines

Scenario: You need to analyze unstructured customer feedback from surveys stored in your data warehouse (e.g., Snowflake, BigQuery).

Integration:

• Use a scheduler like Airflow or a cloud function (AWS Lambda, Google Cloud Functions) to run daily.
• The scheduled job queries your warehouse for new feedback entries.
• It then calls a sentiment-analysis.service.do, passing the unstructured text.
• The service's agentic workflow analyzes the text for sentiment, key topics, and urgency.
• Finally, the job writes the structured output back into a new table in your data warehouse, ready for BI tools like Tableau or Looker.

The Ultimate Flexibility: Chaining Services

The true power of the service.do platform lies in composition. Because every service is a modular API, you can chain them together to orchestrate complex, end-to-end automations.

Imagine a complete customer-onboarding.service.do. This single service might internally call other services:

1. It receives a new customer's email.
2. It calls data-enrichment.service.do to get their company name and role.
3. It calls welcome-email-generation.service.do with that data to create a personalized message.
4. It sends the email and logs the activity by calling your internal logging API.

This modularity keeps each service simple and maintainable while enabling you to build incredibly sophisticated automations that span your entire organization.

Frequently Asked Questions (FAQs)

Q: What is a 'Service' in the context of .do?
A: A Service on the .do platform is a complete business process encapsulated as a programmable API. It takes inputs, performs a series of automated tasks using AI agents, and returns a structured output, effectively turning your operations into software.

Q: How do I create my own service?
A: You define your service using a simple configuration file that outlines the steps, tools, and AI agents involved. Once defined, you deploy it to the .do platform, which instantly makes it available as an API endpoint, ready to be integrated into your applications.

Q: What kind of business processes can be turned into a service?
A: Virtually any repeatable business process can become a service. Common examples include customer onboarding, data enrichment, lead qualification, content generation, financial report analysis, and compliance checks. If you can define the steps, you can automate it with .do.

Q: Can I chain multiple services together?
A: Absolutely. The .do platform is designed for composition. The output of one service can be used as the input for another, allowing you to build complex, end-to-end workflows by chaining together modular, single-purpose services.

Your Business, As a Service.

Integrating new technology shouldn't be a project in itself. With service.do, integration is an inherent feature, not an afterthought. By transforming your business processes into programmable, on-demand services, you can scale your operations with the elegance and efficiency of software.

Ready to connect your stack? Explore our services marketplace or start building your first agentic workflow today.