How To Create Automations from Imported App Events

Installed Marketplace apps can expose live event streams to SheevChat. The Imported App Event trigger turns those mapped values into Automation triggers and variables.

Requirements

  • Install an app that provides one or more event streams.
  • Complete its required connection or authentication.
  • Confirm its Installed Apps card lists Event Streams.

The exact events depend on the package. Examples may include a device state, smart-home event, application status, active scene, score, or another value supplied by the connected app.

Prepare the Event Stream

  1. Open Marketplace → Installed Apps.
  2. Find the app and expand Event Streams.
  3. Turn on Enabled.
  4. Turn on Route automations.
  5. Enable Auto-start if it should start whenever SheevChat opens.
  6. Enable Reconnect when the stream should recover after losing its connection.
  7. Click Start for a manual stream.

The stream card shows its status, event count, last event, mapped values, and the {event.key} variables it provides.

Create the Automation

  1. Open Bot Commands → Automations.
  2. Click New.
  3. Enter a clear name.
  4. Select Imported App Event as the Trigger Event.
  5. Choose the installed Action library.
  6. Choose its Event stream.
  7. Optionally enter a Mapped value key.
  8. Optionally enter the value it must equal.
  9. Add one or more actions.
  10. Save the Automation.

Choose a specific app and event stream for normal use. Leaving them broad may allow unrelated imported events to fire the same Automation.

Filter by a Mapped Value

Suppose the stream provides:

{event.state}

To run only when that state becomes ready:

Mapped value key: state
Mapped value equals: ready

The comparison is not case-sensitive. If you provide a key without an expected value, the Automation matches when that mapped value exists and is not empty.

Use Event Variables

Every Imported App Event can provide general variables such as:

{app}
{library}
{libraryId}
{eventStream}
{eventStreamId}
{eventText}
{eventJson}

Package-defined mapped values appear as variables such as {event.state}, {event.user}, or {event.scene}. Use the variable chips displayed by the stream or Automation helper instead of guessing their names.

Example message action:

The {app} status changed to {event.state}.

Test with a Sample Event

  1. Save the Automation.
  2. Return to Marketplace → Installed Apps → Event Streams.
  3. Review or edit Sample mapped values. It must contain a JSON object.
  4. Click Send Sample.
  5. Confirm the Automation runs and its variables resolve correctly.

A sample is generated locally and does not contact or control the third-party app. Afterward, test one real event and verify the stream's event count, latest values, and Automation timestamp.

Common Problems

  • No apps or streams appear: Install or reload a package that declares event streams.
  • Stream is stopped: Enable it and click Start, or enable Auto-start.
  • Events arrive but Automation does not run: Enable Route automations and check the selected app, stream, key, and expected value.
  • Variable appears literally: Use one of the mapped output variables shown for that stream.
  • Sample JSON fails: Enter a JSON object such as {"state":"ready"}.
  • Stream disconnects: Test its connection and enable Reconnect if the package supports it.
  • Repeated events fire too often: Add an Automation cooldown or narrow the mapped-value filter.