Set Up the woasi Integration

Set Up the woasi Integration

The woasi integration connects octoja to woasi — the connected platform you use to centralise data across your customers. Once connected, octoja sends a baseline inventory snapshot to woasi and then continues to push hourly batches of every customer, site, and device that changed since the last push.

What gets sent?

octoja delivers inventory updates to a woasi API URL via signed outbound deliveries. The first push after Set up is a full snapshot — every customer, site, and device — so woasi has a complete baseline. After that, octoja sends an hourly batch that contains:

• Customer, site, and device records that have been created, renamed, or otherwise mutated since the previous push
• Deletions that were queued during that window (so woasi can keep its view in sync)

The hourly batch is incremental — if nothing changed in a customer or device, that record is not re-sent. Deliveries are signed with the bearer token woasi issued you, and the delivery history is preserved on octoja as an audit trail — you can review it on the woasi integration page.

Inventory is not the only payload type: the same outbound pipeline delivers monitoring events to woasi. The setup dialog asks for the URL octoja should POST monitoring events to, and the test delivery described below includes a monitoring sample.

Prerequisites

• An active woasi account with API access
• From woasi: the API URL octoja should POST inventory to, and the bearer token woasi issued for outbound deliveries
• The Integration Management permission in octoja, granted via groups under Administration → Groups

How it works

When you click Set up (the dialog titled Set up woasi opens), octoja:

1. Stores the API URL and bearer token on a singleton woasi integration record.
2. Queues an initial baseline push so woasi receives every customer, site, and device you currently manage.
3. Starts the hourly delta scheduler.

Steps — Connect

1. Go to Administration → Integrations. Under Ticketing systems, find the woasi card.
2. On the woasi card, click Set up. The dialog titled Set up woasi opens.
3. Fill in:

4. Click Save. octoja:

• Stores the URL and token on the woasi integration record
• Queues a baseline inventory push

The card status flips to Enabled, and the next time the hourly delta scheduler ticks it ships any changes since the baseline.

Send a test delivery

From the woasi integration page, click Send test. octoja queues two test events — an inventory-style event and a monitoring sample — for delivery to the configured URL with the configured bearer token; a toast confirms Test events queued for delivery. Use this to confirm woasi accepts the connection before relying on the live inventory feed.

Integration is enabled, but the snapshot fails with 405

A 405 — Method Not Allowed in the delivery history means woasi's server was reached, but the exact address you entered does not accept POST requests. Because octoja posts to the URL exactly as stored, this is almost always an incomplete API URL — typically the domain or API root (e.g. https://api.woasi.com/) instead of the full receiver endpoint woasi issued (e.g. https://api.woasi.com/incoming/octoja/…).

To fix it:

1. On the woasi integration page, open the Configuration tab, paste the complete endpoint into woasi API URL, and click Save.
2. Switch to the History tab and click Replay on the failed snapshot delivery. The full snapshot is re-sent to the corrected URL.

Deliveries rejected with a 4xx status are not retried automatically, and the baseline snapshot is not re-attempted by the hourly scheduler — until the snapshot goes through (or you disconnect and reconnect, which queues a fresh baseline), Last inventory push stays on Pending and no hourly batches are sent. If deliveries keep failing, octoja pauses the integration automatically after 20 consecutive failures.

Pause vs disconnect

Update the bearer token

If woasi rotates the bearer token, open the woasi integration page and paste the new token into Bearer token (woasi → octoja). Leaving the field empty keeps the current token. The status pill shows whether a token is currently stored.

Tips

• Use HTTPS only. The setup form will refuse anything that is not an absolute https:// URL.
• The baseline push runs once at connect time. If you disconnect and later re-connect, octoja queues a fresh baseline to make sure woasi is in sync. Resuming from a pause does not re-run the baseline — the next hourly tick catches up on its own.
• The hourly batch is coalesced — if a device is changed multiple times within the hour, octoja sends one record with the latest state, not one per change.
• The woasi feed covers inventory and monitoring events. octoja does not send case activity or remote-control events to woasi.
• To deliver check alerts to other external systems, see Set up Webhooks and Send Alerts to a Microsoft Teams Channel.