Check contact records while planning invitations
Look for existing contacts as the team discusses who to invite, without leaving Slack to start a separate search.
Trigger
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
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
Names mentioned during event planning can be lost or searched inconsistently when follow-up happens later.
- Brings possible contact matches into the invitation discussion.
- Helps avoid duplicate or disconnected contact records.
- Keeps names and lookup context close together.
Setup
Build it in a few focused steps.
- 1Connect Slack and Amcards to Notis once through the portal.
- 2Create an automation and write one plain-language prompt for looking up people mentioned in event invitation messages.
- 3Select the Slack Channel Message Received trigger.
- 4Choose a run-report channel and test with a real invitation-planning message.
Questions about this workflow
Does this send invitations?
No. It only retrieves Amcards contacts and reports possible matches.
What if the message mentions several people?
The prompt can ask Notis to report possible matches for each mentioned person, with uncertain matches flagged for human review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slack to Amcards. A trigger fires from one place; an action lands in another.
Slack 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 Channel Created Trigger
Triggered when a new channel is created in Slack.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Connect any two apps with Notis in the middle.
Slack 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.