Skip to content
Notis

Connect GitHub to Amcards

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

When this happens · Trigger

Fires when a new GitHub Actions workflow artifact is created in a repository.

Do this · Action

Retrieves a page of cards associated with the authenticated Amcards account.

Examples

Ways Notis can move work from GitHub to Amcards

Check Outreach Contacts After a Code Scanning Alert

When GitHub reports a new code scanning alert, retrieve Amcards contacts so you can identify relevant people to notify using your existing process.

Bring Amcards Contacts Into New Issue Triage

When a GitHub issue is created, retrieve Amcards contacts to help you check whether the issue affects a customer, partner, or other person you already track.

Review Amcards Cards After a Pull Request Review

When a GitHub pull request review is submitted, retrieve your Amcards cards to keep card tracking available during release or stakeholder follow-up.

Check Amcards Cards When a Workflow Run Changes State

When a GitHub Actions workflow run changes status or conclusion, retrieve Amcards cards to support your team's release or incident follow-up review.

Keep Card Context Handy for New Issue Comments

When a new comment lands on a GitHub issue, retrieve Amcards cards to keep your existing tracking context nearby while you decide whether to follow up.

Review Project Cards When a GitHub Collaborator Joins

When a repository gains a collaborator, retrieve Amcards cards as a prompt to review project tracking and any onboarding follow-up you manage there.

Make a Card Inventory Part of Repository Issue Triage

When an issue is added to a GitHub repository, retrieve Amcards cards to help you review ongoing commitments alongside the incoming work.

Review Work in Flight When a Pull Request Opens

When a GitHub pull request is created, retrieve Amcards cards as context for reviewing work in flight and planning any stakeholder follow-up.

Keep Amcards Cards in View for New Deployments

When GitHub creates a deployment, retrieve Amcards cards to bring tracking context into release coordination and follow-up.

Supported Triggers and Actions

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

GitHub triggers

Amcards actions

Recurring trigger

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

TriggerScheduled

Get Cards

Retrieves a page of cards associated with the authenticated Amcards account.

ActionInstant

Webhook trigger

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

TriggerInstant

Get API Schema

Retrieve the complete API schema.

ActionInstant

New Workflow Artifact Created

Fires when a new GitHub Actions workflow artifact is created in a repository.

TriggerPolling

Get Contacts

Retrieves Amcards contacts with optional name or email filters.

ActionInstant

Branch Changed

Fires when a branch’s commits or protection status or settings change.

TriggerPolling

Get Category

Retrieve details of a card template category.

ActionInstant

New Branch Created

Fires when a new branch is created in a GitHub repository.

TriggerPolling

Get Category Schema

Retrieve the schema for the read-only Category resource.

ActionInstant

Check Run Status / Conclusion Changed

Fires when a GitHub check run’s status or conclusion changes.

TriggerPolling

Get Gift

Retrieve details of a gift, including its price and availability.

ActionInstant

Check Suite Status / Conclusion Changed

Fires when a GitHub check suite changes status or conclusion for a reference.

TriggerPolling

Get Public Template

Retrieve details of a public template.

ActionInstant

New Code Scanning Alert Created

Fires when a new code scanning alert is created in a repository.

TriggerPolling

List Categories

Lists card template categories by priority, with optional filters.

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 GitHub and Amcards

Connect any two apps with Notis in the middle.

GitHub and Amcards, 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 Amcards.