gluer.io
Integrations

No connector catalogue. Just one protocol.

Integration platforms make you wait for someone to build a connector. Gluer is transport-level: HTTP in, WebSocket out, and your own code in the middle — so anything you can call, you can integrate today.

Inbound webhook → worker

Give any vendor a URL on the REST bridge. Gluer routes the payload to a worker and returns its JSON response synchronously, so the vendor sees a normal 200 with a body.

curl -X POST https://ws.gluer.io/api/4f2c9ab7e1d05c83/billing/payment_success \
  -H "Content-Type: application/json" \
  -d '{ "amount": 5000, "customer": "cus_123" }'

Automation platform step

Zapier, n8n, Make or a GitHub Action can call an action the same way. The frontend project key goes in the URL; no SDK required.

# n8n HTTP Request node
Method: POST
URL:    https://ws.gluer.io/api/4f2c9ab7e1d05c83/crm/sync_contact
Body:   { "email": "{{$json.email}}", "plan": "pro" }

Agent runtime as a client

Hermes flows, OpenClaw automations and custom agents connect as clients and call your registered actions — one audited door into your systems instead of credentials per service.

import gluer from "gluer-js";

gluer.setup({ project: "4f2c9ab7e1d05c83" });
gluer.connect();

// The agent only sees the tools you registered.
const tools = {
  lookup_customer: (args) => gluer.sendMsgSync("crm:lookup", args),
  create_ticket: (args) => gluer.sendMsgSync("support:create", args),
};

On-prem system, no VPN

Run a worker inside the private network. It dials out to the mesh, so a legacy ERP or a customer's database becomes callable from your SaaS with no inbound firewall rule.

import * as gluer from "gluer-nodejs";

gluer.register_plugin("erp", "invoice", async ({ id }) => {
  return await oracle.query("select * from invoices where id = :id", [id]);
});

// Outbound only. Nothing to open on the customer's firewall.
gluer.connect(process.env.GLUER_BACKEND_KEY);
Ecosystem

Things teams already wire through Gluer

These are patterns, not proprietary connectors: each one is a worker you own, using the vendor's own SDK.

Payments & billing

  • Stripe
  • Paddle
  • Mercado Pago
  • PayPal

Developer tools

  • GitHub
  • GitLab
  • Sentry
  • Linear

Automation

  • Zapier
  • n8n
  • Make
  • Cron / CI jobs

Agents & tooling

  • Hermes
  • OpenClaw
  • MCP-style tool servers
  • Custom agents

Models

  • Ollama
  • llama.cpp
  • vLLM
  • LM Studio
  • OpenAI-compatible APIs

Data & queues

  • Postgres workers
  • Redis / BullMQ
  • Kafka consumers
  • S3 pipelines

Connect your first two systems today

Create a project, drop the SDK into your app, and point a worker at it. Free while you build, no credit card, no infrastructure to provision.

Start for free Read the docs