Connect Canvas to Cults

When something happens in Canvas, Notis takes the next step in Cults. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Canvas to Cults

View example

Find Cults models for new Canvas submissions

Search Cults for models related to a new Canvas assignment submission and return a short list of relevant results for review.

View example

Review Cults download history after grading

When Canvas grades a submission, check Cults download history for relevant activity and summarize what the available history shows.

View example

Add Cults model context to Canvas discussions

For each new Canvas discussion message, search Cults for related models and share a concise set of results in the run report.

View example

Check Cults collections for new discussion topics

When a Canvas discussion topic is created, review relevant Cults collections and report matching collection details for follow-up.

View example

Prepare a Cults creation link for a Canvas file

When a new Canvas course file is uploaded, prepare a Cults Share on Create link for the 3D file when the upload is suitable and the site is approved.

View example

Find relevant Cults storefronts for a new course

When a Canvas course is created, search Cults designer storefronts for relevant creators and report a short list for review.

View example

Keep Cults collections current from submissions

Use each new Canvas submission to identify useful Cults collection candidates and report whether an existing collection may need attention.

View example

Review approved Cults sharing origins

On a recurring schedule, retrieve the approved sharing origins from Cults and send a concise report for review before using Share on Create.

Supported Triggers and Actions

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

Canvas triggers

Cults actions

Recurring trigger

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

TriggerScheduled

Get Approved Origins

Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.

ActionInstant

Webhook trigger

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

TriggerInstant

Cults GraphQL POST

Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.

ActionInstant

Canvas Assignment Graded

Polls Canvas for newly graded submissions for a specific assignment.

TriggerPolling

Share on Create (FR)

Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.

ActionInstant

New Canvas Assignment Submission

Polls Canvas for new submissions to a specific assignment.

TriggerPolling

New Canvas Discussion Message

Polls Canvas discussion topics for new messages.

TriggerPolling

New Canvas Discussion Topic

Polls a Canvas course for new discussion topics.

TriggerPolling

New Course Created for User

Polls Canvas for newly created courses for a specific user.

TriggerPolling

New Canvas File Upload

Polls a Canvas course for new file uploads.

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.