Connect external requests to an Amcards card review
When another system signals that a card review is due, let its webhook cue Notis to retrieve the current list.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.
Why this helps
A review task is raised elsewhere, then stalls because you have to remember to open Amcards and check it yourself.
- Turn an external review signal into a card-list lookup.
- Make it easier to follow through on checks raised in another system.
- Receive a concise result without manually starting the search.
Setup
Build it in a few focused steps.
- 1Connect Amcards to Notis once through the portal.
- 2Create a webhook-triggered automation in the portal or ask Notis to retrieve Amcards cards when an external review request arrives.
- 3Describe the card overview you need in one plain-language instruction.
- 4Choose the report channel, connect the external system to the webhook, and test with one real request.
Questions about this workflow
Can it schedule or change the cards?
No. This workflow retrieves cards after an external request and summarizes them; it does not modify them.
Can a backend start the lookup?
Yes. A custom backend or external tool can send the HTTP request to the Notis webhook trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Amcards. A trigger fires from one place; an action lands in another.
Telegram triggers
Amcards actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Connect any two apps with Notis in the middle.
Telegram and Amcards, 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 Amcards.