Connect the systems you already run.

Everything in AssetWRX can be read and written through its API, and everything that happens in it can be sent to another system. A wizard connects the systems you already run, without a developer.

Start free Request a demo

Four ways in and out

Every system on this page uses one or more of these. Nothing is hidden behind a connector you cannot see.

The technical detail

  • API

    REST and GraphQL for assets, contacts, inspections, jobs, templates and files. Scoped keys, request IDs on every response, an explorer inside the app.

  • Events

    Signed webhooks for changes across assets, inspections, work, contacts and connected sources, with a test delivery, retries and idempotency.

  • Files and imports

    Spreadsheet import with mapping and duplicate review, a file exchange endpoint, and reports that go to SharePoint as Word.

  • Automations and AI

    Triggers and actions inside the account, an inbound webhook you publish into, and an MCP server where an AI agent's writes need a person's confirmation.

The wizard, not the manual

Eight outcomes on the Integration home, one guided path each: choose, configure, map, authorise, preview, test, activate. Only the access it needs is the default, and the key is shown once.

  • Connect another business system
  • Exchange files
  • Import records from a spreadsheet
  • React when something happens
  • Automate a process
  • Connect sensors or IoT
  • Connect an AI agent
  • Build a custom application

See the task

Systems you can connect

The ones people ask about. Each line says how it connects, because that is the honest answer to "do you integrate with X".

  • ERP and operations

    • Microsoft Dynamics 365
    • SAP S/4HANA
    • Oracle Fusion
    • Odoo
    • Sage Intacct
    • Any other system

    API both ways for assets and jobs, events for changes. The app carries a "Connect an ERP" guide.

  • Property and facilities

    • Yardi
    • MRI
    • Planon
    • Archibus
    • Any other system

    API for the register, file exchange and spreadsheet import for the bulk moves.

  • Service and CRM

    • Dynamics 365 Field Service
    • Salesforce
    • ServiceNow
    • HubSpot
    • Jira Service Management
    • Any other system

    Events out to open a ticket or case, API back to close the loop with status.

  • Automation platforms

    • Power Automate
    • Zapier
    • Make
    • n8n
    • Any other system

    An HTTP action against the API in your flow, an event connection for the trigger. Guide in the app.

  • Microsoft 365

    • Microsoft Entra ID
    • SharePoint
    • Microsoft Teams
    • Any other system

    Sign in with Microsoft. Send job reports to SharePoint as Word. Teams through Power Automate.

  • Finance

    • Xero
    • QuickBooks
    • Sage 50
    • Any other system

    Close-out costs and invoices by API or file, against the job that earned them.

  • Sensors and BMS

    • Any BMS
    • Any sensor gateway
    • Any device that can POST

    Token-authenticated ingest that matches a reading to an asset by external ID or QR label.

  • AI agents

    • Claude
    • ChatGPT
    • Any MCP client

    A first-party MCP server. The agent reads and drafts; material writes wait for a person to confirm.

Names are trademarks of their owners. AssetWRX is not affiliated with or endorsed by them. Every system here connects through the API, events, files and automations above; there are no vendor-specific connectors.

Do it yourself, or with us

Yourself

Guided wizards, keys shown once with an expiry, twenty-six guides with curl examples, and an API explorer inside the app. Most teams connect their first system in an afternoon.

Start free

With us

Architecture, design, delivery, adoption and training from the people who built it, when you would rather not do it alone.

Professional services
Who owns the data, and can we get it out?
You do. Everything is readable through the API and exportable as files, and account deletion removes it on a schedule rather than flagging it.
How are keys kept safe?
Every connection has its own service account and a single key with the narrowest preset that works, an expiry you choose, and a history. Rotate it in place; nothing else has to change.
What happens when the other system is down?
Event deliveries retry with backoff and carry an idempotency key, so a late delivery is not a duplicate. Every response has a request ID you can quote to support.

Connect one system this week.

Your first asset is free, with no card. The wizard takes an afternoon; the API is there when you outgrow it.

Start free Request a demo