How to integrate Netsuite MCP with LlamaIndex

This guide walks you through connecting Netsuite to LlamaIndex using the Composio tool router. By the end, you'll have a working Netsuite agent that can generate monthly profit and loss report, list overdue invoices for all customers, create new sales order for a client through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Netsuite account through Composio's Netsuite MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Netsuite logoNetsuite
Oauth2

NetSuite by Oracle is a cloud-based ERP suite combining accounting, CRM, e-commerce, and inventory management. It streamlines business operations with real-time insights and unified data.

85 Tools

Introduction

This guide walks you through connecting Netsuite to LlamaIndex using the Composio tool router. By the end, you'll have a working Netsuite agent that can generate monthly profit and loss report, list overdue invoices for all customers, create new sales order for a client through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Netsuite account through Composio's Netsuite MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Netsuite with

ChatGPTOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAI

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Netsuite
  • Connect LlamaIndex to the Netsuite MCP server
  • Build a Netsuite-powered agent using LlamaIndex
  • Interact with Netsuite through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

What is the Netsuite MCP server, and what's possible with it?

The Netsuite MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Netsuite account. It provides structured and secure access to your business data, so your agent can perform actions like creating invoices, managing inventory, tracking customer records, and automating financial workflows on your behalf.

  • Automated invoice creation and management: Let your agent generate, send, and update invoices for customers, streamlining your accounts receivable process.
  • Real-time inventory control: Ask your agent to check stock levels, update inventory records, and manage supply chain transactions seamlessly.
  • Customer and vendor record management: Have the agent create, update, or retrieve customer and vendor profiles, keeping your CRM data fresh and accurate.
  • Financial reporting and analytics: Direct your agent to pull balance sheets, profit & loss statements, or transaction histories for up-to-date business insights.
  • Order processing automation: Enable your agent to create sales orders, manage purchase orders, and track fulfillment status across your operations.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Netsuite account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Netsuite

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Netsuite access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called netsuite_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["netsuite"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Netsuite actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, netsuite)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Netsuite tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Netsuite
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Netsuite tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Netsuite
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Netsuite, then start asking questions.

Complete Code

Here's the complete code to get you started with Netsuite and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["netsuite"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Netsuite actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Netsuite to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Netsuite tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Netsuite action and event your agent gets out of the box.

Get Async Job Status

Retrieves the current status of an asynchronous NetSuite REST job.

Get Async Job Task

Retrieves the task reference (task ID and URL) for an asynchronous job in NetSuite.

Async Get Job Task Result

Tool to retrieve the payload result of a completed async task.

Create Customer

Creates a new customer record in NetSuite.

Create Customer Payment

Creates a customer payment record in NetSuite.

Create Employee

Creates a new employee record in NetSuite.

Create Invoice

Tool to create a new invoice record.

Create Item

Creates a new item record in NetSuite via REST API.

Create Journal Entry

Tool to create a new journal entry record.

Create JWT Client Assertion

Tool to build a JWT client assertion for NetSuite OAuth2 client credentials.

Create Purchase Order

Tool to create a new purchase order record.

Create Record

Creates a new NetSuite record of any type (customer, vendor, invoice, sales order, etc.

Create Sales Order

Tool to create a new sales order record in NetSuite.

Create Vendor

Creates a new vendor record in NetSuite.

Create Vendor Bill

Tool to create a new vendor bill record.

Delete Customer

Tool to delete a customer record by ID.

Delete Customer Payment

Delete a customer payment record from NetSuite by its ID.

Delete Employee

Deletes an employee record from NetSuite by its internal ID.

Delete Invoice

Tool to delete an invoice record by ID.

Delete Item

Tool to delete an item record by its type and ID.

Delete Item Fulfillment

Tool to delete an Item Fulfillment record.

Delete Item Receipt

Tool to delete an item receipt record by ID.

Delete Journal Entry

Tool to delete a journal entry record by ID.

Delete Purchase Order

Tool to delete a purchase order record by ID.

Delete Sales Order

Tool to delete a sales order by internal ID.

Delete Vendor Payment

Tool to delete a vendor payment record by ID.

Execute Dataset

Tool to execute a SuiteAnalytics dataset and return paged results.

Get Customer

Tool to retrieve a customer record by internal ID.

Get Customer Payment

Tool to retrieve a customer payment record by ID.

Get Data Center URLs

Tool to discover account-specific service domains.

Get Employee

Tool to retrieve an employee record by ID.

Get Governance Limits

Retrieve NetSuite account and integration concurrency governance limits.

Get Invoice

Tool to retrieve an invoice record by internal ID.

Get Item

Tool to retrieve an item record by internal ID.

Get Item Fulfillment

Tool to retrieve an item fulfillment record by internal ID.

Get Item Receipt

Tool to retrieve an item receipt record by internal ID.

Get Journal Entry

Tool to retrieve a journal entry by internal ID.

Get Purchase Order

Retrieves complete details of a purchase order by its internal ID using the NetSuite REST API.

Get Record Metadata

Retrieves the complete metadata schema for a NetSuite record type, including all field definitions, data types, constraints, and descriptions.

Get Reference Select Field

Retrieves the complete record referenced by a select-type field on a parent record.

Get Sales Order

Tool to retrieve a sales order record by internal ID.

Get Server Time

Tool to retrieve NetSuite server time in UTC.

Get Sublist Collection

Tool to retrieve a sublist collection from a parent record.

Get Sublist Line

Tool to retrieve a specific line from a sublist of a record.

Get Subrecord

Retrieves a specific subrecord from a parent NetSuite record.

Get Vendor

Tool to get a single vendor record by internal ID.

Get Vendor Bill

Retrieve a vendor bill record by its internal ID.

Get Vendor Payment

Retrieves a single vendor payment record by its internal ID from NetSuite.

List Customer Payments

Tool to list customer payment records.

List Datasets

Tool to list SuiteAnalytics Workbook datasets.

List Employees

Tool to list employee records.

List Integrations

Tool to list integration applications.

List Invoices

Tool to list invoice records.

List Item Fulfillments

Tool to list item fulfillment records.

List Item Receipts

Tool to list item receipt records.

List Journal Entries

Tool to list journal entry records.

List Metadata Catalog

Tool to list all record types and their metadata.

List Purchase Orders

Tool to list purchase order records.

List Records

Tool to list record instances.

List Sales Orders

Tool to list sales order records.

List Vendor Payments

Tool to list vendor payment records.

OAuth2 Authorize Account Domain

Tool to construct an OAuth2 authorization URL for a NetSuite account-specific domain.

OAuth2 Authorize System Domain

Initiates the OAuth2 authorization code flow using NetSuite's system domain endpoint.

Get OAuth2 JWKS Keys

Tool to retrieve OAuth2 JWKS public keys.

OAuth2 Logout

Tool to revoke an ID token and its associated access and refresh tokens.

Revoke OAuth2 Refresh Token

Revokes a NetSuite OAuth2 refresh token and all associated access tokens, immediately invalidating them.

Exchange OAuth2 Authorization Code for Tokens

Exchange an OAuth2 authorization code for access and refresh tokens using the NetSuite token endpoint.

OAuth2 Token Client Credentials

Tool to obtain an OAuth2 access token via client credentials grant.

OAuth2 Token Refresh

Tool to refresh an OAuth2 access token.

Run SuiteQL Query

Tool to execute a SuiteQL query.

Transform Record

Transform an existing NetSuite record into another record type (e.

Update Customer

Updates an existing NetSuite customer record using PATCH semantics - only fields included in the 'data' parameter are modified.

Update Customer Payment

Tool to update an existing customer payment by ID.

Update Employee

Tool to update an employee record by ID.

Update Invoice

Updates an existing NetSuite invoice record by ID using the PATCH method.

Update Item

Tool to update an item record by ID.

Update Item Fulfillment

Tool to update an Item Fulfillment record by ID.

Update Item Receipt

Tool to update an item receipt record by ID.

Update Journal Entry

Tool to update a journal entry record by ID.

Update Purchase Order

Tool to update a purchase order record by ID.

Update Sales Order

Updates an existing NetSuite sales order record by ID using PATCH semantics.

Update Vendor

Tool to update a vendor record by ID.

Update Vendor Bill

Tool to update a vendor bill record by ID.

Update Vendor Payment

Tool to update a vendor payment record by ID.

Upsert Record by External ID

Tool to create or update a record by external ID.

FRAMEWORKS

How to build Netsuite MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Netsuite MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Netsuite MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Netsuite MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Netsuite MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Netsuite MCP with Claude Cowork

Codex logo

Codex

Use Netsuite MCP with Codex

Cursor logo

Cursor

Use Netsuite MCP with Cursor

OpenClaw logo

OpenClaw

Use Netsuite MCP with OpenClaw

Hermes logo

Hermes

Use Netsuite MCP with Hermes

CLI logo

CLI

Use Netsuite MCP with CLI

Google ADK logo

Google ADK

Use Netsuite MCP with Google ADK

LangChain logo

LangChain

Use Netsuite MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Netsuite MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Netsuite MCP with Mastra AI

CrewAI logo

CrewAI

Use Netsuite MCP with CrewAI

OpenCode logo

OpenCode

Use Netsuite MCP with OpenCode

VS Code logo

VS Code

Use Netsuite MCP with VS Code

FAQ

Frequently asked questions

With a standalone Netsuite MCP server, the agents and LLMs can only access a fixed set of Netsuite tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Netsuite and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Netsuite tools.

Yes, absolutely. You can configure which Netsuite scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Netsuite data and credentials are handled as safely as possible.

Start with Netsuite.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Netsuite tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies