Find contact matches from a Slack DM
Get the contact search started from the private conversation where the question came up.
Trigger
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
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
A contact question in a DM can get buried while someone switches apps to search a separate list.
- Starts a lookup without leaving the DM context.
- Makes possible matches easier to review before someone responds.
- Reduces the chance that a private request is forgotten during app switching.
Setup
Build it in a few focused steps.
- 1Connect Slack and Amcards to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for a DM contact lookup.
- 3Write one plain-language prompt describing how to identify the person and report possible matches.
- 4Select the Direct Message Received trigger, choose a run-report channel, and test with one real DM.
Questions about this workflow
Does this read every Slack DM?
The selected trigger fires for new direct messages sent to the user across DM channels. Use a clear prompt and channel permissions appropriate to your workflow.
Can it confirm identity from a name alone?
No. It retrieves contact records for review; similar names should be treated as possible matches, not confirmed identities.
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.