Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.superglue.cloud/llms.txt

Use this file to discover all available pages before exploring further.

superglue isn’t just where you build tools, it’s where they run. When you execute a tool, superglue handles the infrastructure: making API calls, resolving credentials server-side, managing retries and rate limiting, and logging every step. You don’t need servers, queues, or cron jobs on your side. Trigger tool runs on-demand, automate them on a schedule, or react to external events via webhooks. All through the same managed runtime.

REST API & SDK

Execute tools programmatically from your codebase using the TypeScript or Python SDK, or call the REST API directly.

MCP

Give AI agents direct access to execute tools via Model Context Protocol in Cursor, Claude, and other MCP clients.

Schedules & Webhooks

Automate execution with cron schedules or trigger runs from external services like Stripe, GitHub, or Shopify.
Execute tools directly from the tool details page:Step input
1

Navigate to your tool

Go to Tools in your dashboard and select the tool you want to run
2

Provide input data

Enter any required input parameters in JSON format. If your tool doesn’t require input, use {}
3

Execute

Click “Run All Steps” to execute immediately. You’ll see real-time logs and step-by-step progress
4

Review results

Check the output data and individual step results. All executions are logged for debugging.

Enterprise deployment options

superglue Enterprise offers additional deployment capabilities for automated and event-driven execution:

Scheduled Execution

Automate tool runs with cron-based scheduling. Run tools at specific times or intervals.

Incoming Webhooks

Trigger tools from external services like Stripe, GitHub, or Shopify via HTTP webhooks.

Tool Chaining

Chain tools together so one tool’s output automatically triggers another tool.

Tool chaining

Chain multiple tools together to build multi-step workflows. When one tool completes, it can automatically trigger another tool with its output as input.
// Run a tool that chains to another tool when complete
const { data: run } = await runTool("fetch-orders", {
  inputs: { since: "2025-01-01" },
  options: {
    async: true,
    webhookUrl: "tool:process-orders", // Triggers process-orders with fetch-orders output
  },
});
The chained tool run will have requestSource: "tool-chain". See the webhooks documentation for more details.