Skip to content
Notis

Connect Trello to GitHub

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

When this happens · Trigger

Triggers when a file or link is attached to a card.

Do this · Action

Accept a pending repository invitation.

Examples

Ways Notis can move work from Trello to GitHub

Assign GitHub owners from new Trello work

Turn a fresh Trello task into an owned GitHub issue so implementation never waits in an unassigned queue.

Label GitHub issues from Trello intake

Apply useful GitHub labels when a Trello card enters your product or bug intake board.

Update GitHub assignees after Trello planning

When a Trello card is updated during planning, keep the related GitHub issue assigned to the person now carrying the work.

Add release labels from Trello card updates

Mark related GitHub issues for the right release when their Trello cards are updated during release planning.

Cancel obsolete GitHub runs from archived cards

Stop a related queued or in-progress GitHub workflow when the underlying Trello work is archived.

Approve fork runs after Trello review activity

Approve a waiting GitHub Actions run from a trusted fork when Trello shows the review is ready to proceed.

Check pull request merge status for new Trello follow-ups

Verify whether a pull request is merged when a Trello follow-up card is created, so next steps start from the right state.

Verify GitHub assignee eligibility from Trello updates

Check that the person named in an updated Trello task can be assigned in the related GitHub repository.

Check GitHub collaborator access from Trello activity

Confirm a collaborator has access when Trello activity signals they are joining a code task.

Supported Triggers and Actions

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

Trello triggers

GitHub actions

Recurring trigger

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

TriggerScheduled

Accept a repository invitation

Accept a pending repository invitation.

ActionInstant

Webhook trigger

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

TriggerInstant

Abort Repository Migration

Aborts a queued or ongoing repository migration.

ActionInstant

Attachment Added To Card

Triggers when a file or link is attached to a card.

TriggerInstant

Add email for auth user

Add email addresses to your account.

ActionInstant

Attachment Removed From Card

Triggers when an attachment is removed from a card; its URL is omitted.

TriggerInstant

Add app access restrictions

Allow apps to push to a protected branch.

ActionInstant

Board Added To Workspace

Triggers when a board is created in or moved into the watched Workspace.

TriggerInstant

Add a repository collaborator

Add a user as a repository collaborator or update their access.

ActionInstant

Board Label Created

Triggers when a label is added to the board’s label set.

TriggerInstant

Add field to user project

Adds a custom field to a user-owned project.

ActionInstant

Board Label Deleted

Triggers when a label is deleted from the board; its text and color are omitted.

TriggerInstant

Add a repository to an app installation

Grant an app access to a repository.

ActionInstant

Board Label Updated

Triggers when a board label changes.

TriggerInstant

Add item to user project

Adds an issue or pull request to a user-owned project.

ActionInstant
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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,700+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
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.

Notis

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.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect Trello and GitHub

Connect any two apps with Notis in the middle.

Trello and GitHub, or any other combination from 1,700+ 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 GitHub.