Connect Trello to Coassemble

When something happens in Trello, Notis takes the next step in Coassemble. 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 Trello to Coassemble

View example

Match new Trello cards to Coassemble courses

When a Trello card is created, review Coassemble courses and return the closest course matches with a short rationale.

View example

Review training progress after Trello activity

When Trello activity occurs, retrieve Coassemble tracking data and summarize progress that may affect current work.

View example

Check learner readiness when a Trello card changes

When a specific Trello card is updated, retrieve Coassemble users and summarize the people relevant to the changed work.

View example

Add Coassemble client context to every new Trello board

When a Trello board is created, retrieve Coassemble clients and return likely organization context for the new workspace.

View example

Review training progress when a Trello card is archived

When a Trello card is archived, retrieve Coassemble tracking data and summarize training progress connected to the completed work.

View example

Send a daily Coassemble progress digest

On a schedule, retrieve Coassemble tracking data and summarize progress changes, completions, and items needing attention.

View example

Review the Coassemble course catalog every week

On a weekly schedule, retrieve Coassemble courses and summarize new, changed, or potentially useful training options.

View example

Look up Coassemble users from an external request

When an HTTP request arrives, retrieve matching Coassemble users and return a concise roster summary for the requesting process.

View example

Retrieve Coassemble client context from a webhook

When an HTTP request arrives, retrieve Coassemble clients and return the records relevant to the supplied organization or onboarding context.

Supported Triggers and Actions

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

Trello triggers

Coassemble actions

Recurring trigger

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

TriggerScheduled

Get Clients

Tool to retrieve a paginated list of clients. use when you need to browse or process organisation records sequentially.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Courses

Tool to retrieve all courses with optional filters and pagination. use when you need to list courses after setting identifier and client identifier, and control page size and number.

ActionInstant

Card Archived Trigger

Triggered when a card is archived in the specified board

TriggerInstant

Get Trackings

Tool to retrieve tracking objects with filters. use when you need to fetch learner progress data filtered by course id, date range, identifier, or completion status.

ActionInstant

New Activity Trigger

Triggered when there is activity in Trello.

TriggerInstant

Get Users

Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.

ActionInstant

New Board Trigger

Triggered when a board is created in the specified workspace

TriggerInstant

New Card Trigger

Triggered when a card is created in the specified board

TriggerInstant

Card Updated Trigger

Triggered when a specific card is updated

TriggerInstant

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.