Can Lyro turn a device on or change a variable in Apilio?

No. Every action this toolkit exposes is a read, covering variables, conditions, logicblocks, and time or Tuya conditions. Lyro can report exactly why an automation did or did not fire, but triggering it and changing a value still happen in Apilio.

How can Lyro tell whether an automation actually ran?

Get Logicblocks returns each logicblock's active status, last evaluation result, and update timestamp together. A rule that is inactive, one that evaluated false, and one that has not been evaluated for days are three different problems, and those fields separate them.

Which smart home brands show up in the conditions?

Tuya is the only brand with its own condition type here: List Tuya Conditions covers conditions based on Tuya and Smart Life device states. Devices from other brands surface through the variables and conditions Apilio maintains for them rather than a brand-specific action.

How is this different from wiring Apilio into Zapier or n8n?

Those run a fixed sequence when a trigger matches. Lyro decides which Apilio read to call while a question is still open, so it can check a boolean, then the condition watching it, then the logicblock combining them, and explain the result in one reply.

Apilio MCP integration

Reads current variable values, lists the conditions and logicblocks behind an automation, and shows which triggers fire on time or device state.

Connect Apilio See all integrations

8actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get logicblocks
Lyro retrieves all automation logicblocks configured in Apilio for the account. Your team audits which automations are active without leaving the conversation.
Get conditions
Lyro pulls all conditions defined in your Apilio account during a troubleshooting session. You quickly identify which logic blocks are triggering unwanted behavior.
List time conditions
Lyro fetches all time-based conditions from Apilio to review scheduling logic. Your team can verify or fix time-triggered automations on the fly.

See all 8 actions

How businesses use Apilio + Lyro

Each card is one request a support team gets, and the Apilio actions Lyro runs to close it.

Check whether a flag is set and what watches it
Lyro fetches every boolean variable with its current state, then lists the variable conditions that evaluate against those values, so a yes or no answer arrives with the rule that depends on it.
Get Boolean VariablesList Variable Conditions
Read the measured values an automation runs on
Lyro pulls the numeric variables with their current values and the string variables alongside them, each carrying a UUID and a last-updated timestamp for spotting a reading that has gone stale.
Get Numeric VariablesGet String Variables
Inspect the logic behind an automation
Lyro lists the logicblocks in the account with their names, active status, and last evaluation result, plus the conditions they combine, which is how you tell a disabled rule from a failing one.
Get LogicblocksGet Conditions
See which triggers depend on time or a device
Lyro retrieves the time conditions built on sunrise, sunset, fixed hours, or cron expressions, and the Tuya conditions that track Smart Life device states.
List Time ConditionsList Tuya Conditions

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Apilio actions it has and picks the ones a request needs.

01
Connect Apilio
Authorize the Apilio account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Apilio actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Apilio · Lyro

Everything else about Apilio

Setup, permissions, and the limits of what Lyro can do inside Apilio.

No. Every action this toolkit exposes is a read, covering variables, conditions, logicblocks, and time or Tuya conditions. Lyro can report exactly why an automation did or did not fire, but triggering it and changing a value still happen in Apilio.

Every action available in Apilio

All 8 actions your agent can call on Apilio, straight from the live MCP connection.

Get boolean variables
Fetch all boolean variables.
Get conditions
Retrieves all conditions from your Apilio account.
Get logicblocks
Retrieves all logicblocks for the authenticated Apilio user.
Get numeric variables
Retrieves all numeric variables from your Apilio account with their current values and metadata.
Get string variables
Fetch all string variables.
List time conditions
Fetch all time conditions of a user.
List tuya conditions
Retrieve all Tuya conditions from your Apilio account.
List variable conditions
Retrieve all variable conditions from your Apilio account.