Skip to content
Notis

Check an Ably channel resource on a schedule

Run a small, repeatable command on schedule and bring the result back to your report channel.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Run Terminal Command

Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.

Why this helps

A lightweight channel check can be forgotten when it depends on someone remembering to run a command.

  • Run an established check command on schedule.
  • Capture standard output, errors, and exit code.
  • Make routine checks visible in a chosen report channel.

Setup

Build it in a few focused steps.

  • 1Connect Ably and Codeinterpreter once in the Notis portal.
  • 2Create an automation in the portal or tell Notis in plain language from any channel.
  • 3Describe the existing command or script to run and what its output should indicate.
  • 4Choose notis_cron as the trigger and select where run reports should go.
  • 5Test with one real command and confirm the report is understandable.

Questions about this workflow

Does this workflow subscribe to Ably channel events?

No. It runs from a recurring Notis schedule. Ably trigger events are not available in this package.

What should the command check?

Use a command or script that is already supported by the connected environment and specify the resource and expected result in your instruction.

What happens when the command fails?

The terminal action returns stdout, stderr, and an error code. Notis can include those results in the run report.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Ably to Codeinterpreter. A trigger fires from one place; an action lands in another.

Ably triggers

Codeinterpreter actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Sandbox

Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Execute Code

Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.

ActionInstant

Get File

Get a file from the sandbox and returns the file. the files should be read from /home/user folder.

ActionInstant

Run Terminal Command

Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.

ActionInstant

Upload File

Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.

ActionInstant

Connect any two apps with Notis in the middle.

Ably and Codeinterpreter, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Codeinterpreter.