Auxot
Tutorials Docs Pricing Login

Use Auxot as glue between two SaaS tools

Stand up a **glue-pattern partner** — name **system A → event**, **system B → action**, and **Auxot middle** — workflows ([Run a workflow](/tutorials/run-a-workflow)), intakes ([Trigger a workflow with an intake webhook](/tutorials/trigger-a-workflow-with-an-intake-webhook)), and MCP tools ([Add an MCP server](/tutorials/add-an-mcp-server)) — plus explicit **human gates** when writes touch money or customer records — so integrations read like architecture, not folklore.

Plus: three Admin-Agent passes — draft **one-page glue map** — five sections — no fake vendors — encode **idempotency + replay** rules from intake payload alone, and decide **MCP vs webhook-only** when only one side exposes HTTP cleanly.

Audience Admins · Developers
Time ~15 min
Prerequisites Workflow basics ([Run a workflow](/tutorials/run-a-workflow)). Tool discipline ([Define a tool policy](/tutorials/define-a-tool-policy), [Manage your Credentials](/tutorials/manage-your-credentials)). HTTP intake comfort ([Trigger a workflow with an intake webhook](/tutorials/trigger-a-workflow-with-an-intake-webhook)) **or** willingness to paste events manually until wired. Helpful: MCP setup ([Add an MCP server](/tutorials/add-an-mcp-server)) when agents must reach the second tool live.
You'll end up with One **Glue map** markdown — **sources, transforms, side effects, owners, and rollback posture** — plus the smallest viable chain **you** actually run once — manual paste acceptable — automation earns trust later ([Harden your intake webhooks](/tutorials/harden-your-intake-webhooks)).

When a tutorial shows italic text in quotation marks, it usually mirrors a label or helper string inside Auxot. Product copy changes between releases — if something reads differently in your workspace, trust what you see on screen.

Callouts with a Worth knowing gold accent are meant as must-read context before you move on. Blockquotes that open with Tip are lighter, optional depth.

Why this matters

Most “integrations” are brittle scripts nobody owns: secret sprawl, silent duplicates, and two truths in two databases.

Auxot gives you human-visible glue: normalize messy payloads (Trigger a workflow with an intake webhook), let agents draft summaries or field maps (Create an agent from scratch), attach MCP-backed tools when the second SaaS expects structured actions (Add an MCP server), and pause for humans when stakes demand it (Require human approval before risky actions).

Nothing crawls both tenants unattended: you prompt agents or you wire POSTs because you configured them. Chat bridges (Connect Slack to your agents) still count as glue when humans paste payloads until HTTP lands.

Glue is explicit routing — not vibe sync.

Quick start

  1. Name systems honestly — CRM vs ticketing vs billing; pick one system of record per fact (Add your first context file glossary helps names stay stable).
  2. Pick trigger reality — webhook intake today (Trigger a workflow with an intake webhook) vs tomorrow vs paste-only pilot; write PASTE_OK path first when vendors stall.
  3. Mint Glue-map agent — charter outputs fixed headings; refuses invented OAuth scopes; demands UNKNOWN when docs missing.
  4. Sketch workflow spine — ingest → normalize JSON → agent draft → optional MCP → approval (Require human approval before risky actions) → archive receipt (View your audit logs).
  5. Dry-run once — paste synthetic payload; verify duplicate POST story (Harden your intake webhooks); fix before exposing URL.

Done? Glue map checked into wiki or repo beside Runbook link; teammates reproduce dry-run without DM roulette.

The agent can do that?

1. Five-section glue map

Chat → Admin Agent:

Systems named A=[…] B=[…]. Events we care about: [bullets]. Constraints: [paste]. Produce Glue map — sections Purpose / Trigger / Transform / Side effects / Failure — <=35 lines — markdown — UNKNOWN gaps explicit — no vendor APIs invented.

Why it’s non-obvious: Diagrams lie; forcing failure section early prevents demo-only integrations after you paste constraints.

2. Idempotency brief

Sample JSON keys from vendor docs paste: […]. Describe duplicate delivery scenario — how workflow recognizes same logical event twice — bullets — includes deactivate posture — <=12 lines.

Why it’s non-obvious: Intakes retry; naive inserts duplicate tickets (Harden your intake webhooks).

3. MCP vs webhook-only tradeoff

Tool surfaces available: MCP catalog yes/no — inbound HTTP only yes/no — recommend pattern — **MCP_AGENT_STEP** vs **OUTBOUND_WEBHOOK_STEP** — cite assumptions — plain bullets.

Why it’s non-obvious: MCP shines for agent-shaped actions; dumb pipes prefer plain HTTP; mixing metaphors confuses operators (Add an MCP server).

Go deeper

CI triggers

Ship GitHub-side runners posting intakes (Trigger a workflow from GitHub Actions); same glue contract; correlation ids baked in.

Keys

Automation keys belong to teams, not departing humans (Create a shared Team API Key, Pick personal or team API keys for real work).

Ops tracing

When Jobs fail mid-chain: trace jobs end to end (Trace a failing job end to end); glue maps speed triage.

Announce changes

Brain edits affect glue behavior: ship notes (Update your agents without breaking the team); ops deserves diff literacy.

Walkthrough

Step 1: Pick boring pilot first

Read-only digest before write API; prove normalization; graduate slowly.

Step 2: Paste worst real payload

Redact customer identifiers; keep structural warts; normalize fields honestly.

Step 3: Wire MCP minimally

One tool, one credential; expand later (Define a tool policy, Manage your Credentials).

Step 4: Human gate dry-run

Reject once; confirm loop returns cleaner draft; approve once; log Job ids (View your audit logs).

Step 5: Document rollback

Disable intake token; pause workflow; announce channel (Connect Slack to your agents); keep the tone neutral; link Run a post-mortem that leads to action when prod glue snaps.

What’s next

Reference

Browse all tutorials