Integrations
No makerspace is the only system on campus. MakerOps treats integration as a first-class part of the platform: standard ways to connect — live REST calls, event-driven webhooks, scheduled file exchange, an outbound-only channel for on-prem hardware, and campus single sign-on — and first-class integrations for the systems that need more.
Five patterns
A card office wants a nightly file. A tool-control box in the basement cannot accept an inbound connection at all. A dashboard wants live reads. MakerOps has a path for each, so an integration can match what the other system is actually capable of. And where a system needs more than a standard pattern, MakerOps supports a first-class integration built for it, rather than a workaround.
For anything that needs the current answer right now.
A dashboard that shows machine downtime. A campus portal that lists which trainings a student has completed. A script that reconciles inventory against the purchasing system. Token-authenticated, permission-scoped, and shaped for incremental sync so a nightly job pulls only what changed.
Typically used for
For when something on your side must happen the moment something happens here.
Subscribe an HTTPS endpoint to normalized events and MakerOps posts to it as they occur. A member earns a credential and your tool-control system grants the machine within seconds. A card number changes and your door system updates. An item hits its reorder point and your procurement system opens a requisition. No polling, no lag, no cron job guessing at an interval.
Typically used for
For the systems that will only ever accept a file on a share.
A configurable roster CSV, generated on your schedule and delivered to your SFTP endpoint. You pick the columns and their order, the cadence, and the remote path. Plenty of campus systems — card offices, legacy tool control, some student information systems — have no API and never will. A file at 2am is not a workaround for them; it is the integration.
Typically used for
For boxes in the basement that cannot accept an inbound connection.
A small program runs inside your network and long-polls MakerOps for work, then reports results back. Everything is outbound from your side — no inbound firewall rule, no port forward, no VPN, no public endpoint on a machine that runs a laser. Failed jobs retry with backoff, and polling doubles as the liveness signal so an offline connector raises an alert on its own.
Typically used for
For letting the campus stay the source of truth about people.
SAML single sign-on with per-tenant identity sync, so accounts, person identifiers, card numbers, and status follow the institution rather than being maintained twice. Configured from an administrator screen by importing your identity provider’s metadata — no code, and no ticket to us.
Typically used for
Start free, or book a demo and see MakerOps running with real equipment, training flows, and reports.
