Answers to frequently asked questions.

What is Switchur?

Switchur was created to extend IFTTT, Microsoft Flow, and Zapier (collectively "consumer" iPaaS - Integration Platform as a Service - solutions). These iPaaS solutions connect to your smart devices and online services, allowing you to link an event with an action. But whilst these platforms are amazing, they also have some limitations. The communications across iPaaS connectors is unidirectional and stateless, also there is little in the way of transmission evaluation and processing options available. Switchur adds both a state layer, and a logic processing layer, which when combined produce much smarter automation outcomes. When we're explaining this in nontechnical terms we can make a correlation between iPaaS solutions and a musical orchestra where Switchur embraces the vacant role of orchestra conductor. Listening, studying, coordinating, unifying tempos, interpreting meaning, whilst being a conduit for the platform communications.

What is the Switchboard?

It's where you can view, add, and manage all of your switches, counters, and keywords/key phrases. It displays the current value of your Switchboard items and gives you access to each items log of changes.

What are Switchboard items?

The three Switchboard item types are Switch, Counter, and Keyword(s). Each stores a different type of value.

  • A "Switch" stores an ON/OFF state
  • A "Counter" stores a NUMBER (up to two decimal places)
  • A "Keyword" stores TEXT (up to one hundred characters)

When you first create a Switchboard item it has no value set, and special urls are produced that allow for it to be updated via IFTTT, Zapier, and/or Microsoft Flow.

What can I do with Switchboard items?

Once you've configured IFTTT, Zapier, Microsoft Flow (or any system capable of making generic outbound HTTP requests and receiving inbound webhooks) to update the Switchboard item you can use them in automation routines. When a Switchboard item value changes, any automation where that Switchboard item is referenced is checked, and if automation criteria is met then the appropriate actions are processed.

What is an Automation?

An Automation is a fusion of Switchboard item criteria and actions. By defining the required criteria of a selection of Switchboard items you define the circumstances for when that Automation will evaluate to true. Add positive (i.e. when true) and negative (i.e. when false) actions to the Automation to invoke the desired result. For example,

Why would I want to use Switchur?

With Switchur you get automation superpowers. Imagine a world where once you've created the automation, you never have to manually control that thing again. It is the solution for absolute automation where several required states have to align to for an automation to occur. Switchur embodies logical conjunctive and disjunctive assertions (AND, OR) to bind conditions, and the advanced expression builder can support even the most complicated requirements. For example, to turn on a device, but only when at least one family member is at home, and only between certain hours of the day, and only when the indoor temperature is above some level, and only on weekdays. And also in reverse, turn off a device when all family members have left the house, or it's not between certain hours, or the temperature drops below some level. Switchur can track the state of those required conditions, and switch said device on and off accordingly.

How does an Automation work?

Every automation you add references a selection of Switchboard items and the required criteria of each. When a switchboard item has it's status or value updated, each automation that references that switchboard item gets re-evaluated. All actions in an automation assigned to either a positive (the green thumbs up icon) or negative (the red thumbs down icon) result are then invoked based on whether all of the automation Switchboard item criteria was a match.

How does a Switch work?

A switch has only two possible states, ON or OFF. So it can represent anything that can only have two possible states whether true or false, yes or no, on or off, etc. Use cases for a switch could include "Dad at home", "It is night time", or "It is raining". A switch is updated via one of three methods; turn ON, turn OFF, toggle. You control the switch by configuring http requests to call the API endpoint. When a switch is added to an Automation you define the required state of ON or OFF in order for the Automation to evaluation to be positive.

Visit our blog

Platform comparison

A succinct outline of the offerings of IFTTT, Microsoft Flow, Zapier, plus a few notable others. Find out which option makes the most sense for what, whom, and when.

Read more