Bring external contact requests into Amcards
When another system raises a contact question, a webhook can cue Notis to look in Amcards and report back for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Contact requests arrive through separate systems and lose momentum while you manually carry the details between them.
- Use a webhook to start a contact lookup from another system.
- Reduce manual copying between a request source and Amcards.
- Get a match summary in the selected run-report channel.
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 set up an Amcards contact lookup for incoming requests.
- 3Write one plain-language instruction explaining what contact request to handle and how to report matches.
- 4Choose a channel for run reports, connect the sending system to the automation webhook, and test one real request.
Questions about this workflow
Does the webhook create an Amcards contact?
No. This workflow uses the contacts retrieval action to find and summarize existing records.
Who sends the webhook?
An external tool or custom backend that you connect 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.