Resources · Make integration

oqdo.bos Make integrationAutomate oqdo.bos with Make.

Want every oqdo.bos alarm to reach the right person without anyone refreshing a dashboard? The oqdo.bos Make integration gives you 4 modules: 2 scheduled triggers and 2 actions. This guide links your account, builds a first scenario and explains each module.

Try the oqdo.bos integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the oqdo.bos Make integration do for you?

The oqdo.bos Make integration lets Make read what happens in your oqdo.bos account and pass it to your other tools, with no code. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger or an action.

Alarms that land where people work. Watch alarms picks up new alarms from oqdo.bos, and the next module in the scenario can post them to a chat tool, open a ticket or send an email. Facility teams stop checking the platform by hand.

A log of twin changes. Watch twin changes spots twins that were modified, so a spreadsheet or a database can keep a running history that the rest of the company can read.

Details on demand. Get twin reads one twin, which is handy when another app sends you a reference and you need the full record before acting. For anything the listed modules do not cover, Make an API Call reaches the oqdo.bos API with the same connection.

What Make does not do here: both triggers are scheduled, so Make checks oqdo.bos on the scenario's schedule rather than being told at once. Make's help page for oqdo.bos says it was written by AI from the vendor's documentation and may contain mistakes, so confirm important details with oqdo.bos. If you weigh other tools, read n8n vs Make, and if you want the build done for you, see our Make agency. To learn the editor properly, Make training starts from zero.

Connect

How do you connect oqdo.bos to Make?

  1. 01

    Add an oqdo.bos module

    In a scenario, click the +, search for oqdo.bos and pick any of its modules. Then click Create a connection. A connection is your oqdo.bos account linked to Make once and reused by every oqdo.bos module.

  2. 02

    Name the connection and authorize

    Give the connection a name if you run several oqdo.bos accounts, for example one per site. Then follow what Make shows: either an authorization page from oqdo.bos or a field where you paste the key oqdo.bos gives you.

  3. 03

    Save and check

    Click Save. Once the connection works, Make can list the objects it is allowed to read, so the module fields stop being empty. If the list stays blank, the account behind the connection is the first thing to check.

First scenario

Your first scenario with oqdo.bos

GoalWhen a new alarm shows up in oqdo.bos, Make reads the twin behind it so your team gets the context with the alert.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Everything you build next hangs off this first brick.

  2. 02

    Add Watch alarms

    Search for oqdo.bos, choose Watch alarms and click Create a connection to link your account. Fill its fields; Make lists what it can read once the connection exists.

  3. 03

    Add Get twin

    Click the + on the right of Watch alarms and add Get twin. If the alarm carries a twin reference, map it from the previous module instead of typing a value.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one alarm. Check that the twin data looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Set it, then switch the scenario on.

Triggers

What starts an oqdo.bos scenario

2 modules start a scenario when something happens in oqdo.bos. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by oqdo.bos as soon as it happens.

oqdo.bos1Watch alarms

Watch alarms

triggerIn the docs only

Watch alarms turns new oqdo.bos alarms into bundles your scenario can route anywhere, so an alert no longer depends on someone having the platform open. Each alarm found becomes one item for the next modules.

How it fires
scheduled. Make checks oqdo.bos on the scenario's schedule, which is every 15 minutes by default, rather than being called by the app.
When to use it
a maintenance team wants alarms posted in its chat channel or turned into tickets as soon as Make picks them up.
Watch out
the delay between an alarm and your message depends on the schedule you set, and the Free plan cannot go below 15 minutes.
oqdo.bos2Watch twin changes

Watch twin changes

triggerIn the docs only

With Watch twin changes, every modified twin in oqdo.bos can feed a history, a report or a notification without anyone exporting data. The module hands each changed twin to the rest of the scenario as its own bundle.

How it fires
scheduled. Make asks oqdo.bos for changes at each run of the scenario, on the schedule set on this first module.
When to use it
an operations lead keeps a spreadsheet of twin updates that managers read without an oqdo.bos login.
Watch out
a new scenario checks every 15 minutes by default; if the log must stay fresher, a paid plan allows an interval down to 1 minute.
Modules

What the oqdo.bos modules do

oqdo.bos gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

oqdo.bos1

Get twin

ActionIn the docs only

Get twin fetches one twin from oqdo.bos so the rest of the scenario can use its data. It works on a single item, which makes it the natural step after a module that only gives you a reference.

When to use it
after an alarm or a request from another tool, to add the twin's details to the message you send.
Watch out
Make's help page for oqdo.bos is AI-generated, so run the module once and read its output before relying on a given value.
oqdo.bos2

Make an API Call

ActionIn the docs only

Make an API Call is your way out when the three other modules stop short: it calls any endpoint of the oqdo.bos API, reusing the connection you already created, so no second login is needed.

When to use it
you need an oqdo.bos action that has no dedicated module, and the API documentation from oqdo.bos describes it.
Watch out
Make does not fill the fields for you here, so you work from the vendor's API reference and test with Run once before activating.
Need help

Need help automating oqdo.bos with Make?

A person reads every message.

FAQ

oqdo.bos and Make: common questions

01Is the oqdo.bos Make integration free?
Yes, on the Make side. oqdo.bos is a standard app, available from the Free plan, which allows 2 active scenarios, runs spaced at least 15 minutes apart, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your oqdo.bos subscription is a separate matter: check the oqdo.bos pricing page for that.
02What do you need to connect oqdo.bos to Make?
An active oqdo.bos account is the only prerequisite the documentation lists. In Make, you add any oqdo.bos module, click Create a connection, optionally name it, authorize Make on the oqdo.bos page or paste the key oqdo.bos provides, then save. The same connection then serves all 4 oqdo.bos modules, so you only do this once per account. If the list of objects stays empty after saving, check that the account you used is active.
03Do the oqdo.bos triggers fire instantly?
No. Watch alarms and Watch twin changes are both scheduled triggers: Make checks oqdo.bos at each scheduled run instead of receiving a call from the app. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans go down to 1 minute. If you need a faster reaction, the only lever is a paid plan with a shorter interval.
04What if the oqdo.bos module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the oqdo.bos API with the connection you already set up, so it covers what Watch alarms, Watch twin changes and Get twin do not. Keep in mind that the oqdo.bos documentation in Make is flagged as AI-generated and may contain mistakes, so check the vendor's own API reference and contact oqdo.bos if something does not match. Test each call with Run once before switching the scenario on.
05Should you use Make or n8n for oqdo.bos?
It depends on what each tool offers for oqdo.bos at the time you build. In Make, you get 4 ready modules, a visual editor and Make an API Call for the rest. Many apps also have an n8n node, so check whether oqdo.bos has one before choosing, and compare the building blocks available on each side for your use case rather than general reputation. The n8n vs Make comparison linked earlier on this page lays out the main differences.
Same platform

Other docs you might need on this stack.

Browse all integrations