Check Amcards contacts from a Slack outreach request
When a team member posts an outreach request in Slack, retrieve Amcards contacts and report likely matches so the team can check existing relationships before reaching out.
Connect Slack to Amcards
When something happens in Slack, 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
Triggers when a new channel is created.
Do this · Action
Retrieves a page of cards associated with the authenticated Amcards account.
Examples
Ways Notis can move work from Slack to Amcards
Look up an Amcards contact from a Slack DM
When a direct message asks about a person or organization, retrieve Amcards contacts and return possible matches in the run report for quick review.
Retrieve Amcards cards when a Slack message gets a chosen reaction
When a message receives the team's chosen reaction, retrieve the Amcards card list and summarize the available cards in the run report as a reference for follow-up.
Check available Amcards cards during campaign planning
When a campaign planning message appears in Slack, retrieve the current Amcards cards and report the list so the team can consider available options during planning.
Check Amcards contacts during event invitation planning
When Slack discussion turns to inviting people to an event, retrieve Amcards contacts and report possible matches for the names or organizations mentioned.
Retrieve contact context when a Slack follow-up is assigned
When a channel message assigns a follow-up involving a person, retrieve Amcards contacts and report possible matches to help the owner prepare the next step.
Check Amcards card availability from a Slack DM
When a DM asks which cards are available, retrieve the Amcards card list and report it so the person can answer without opening another tool.
Retrieve Amcards cards when a campaign channel is created
When a new Slack channel is created, retrieve Amcards cards and report the list as an initial reference for the team's campaign or project setup.
Use a Slack reaction to request a contact lookup
When a message receives the team's chosen reaction, retrieve Amcards contacts and report possible matches for people mentioned in that message.
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.
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 Channel Created Trigger
Triggers when a new channel is created.
TriggerInstant
Get Contacts
Retrieves Amcards contacts with optional name or email filters.
ActionInstant
Channel Message Received
Triggers when a message is posted in a channel, excluding direct messages.
TriggerInstant
Get Category
Retrieve details of a card template category.
ActionInstant
Direct Message Received
Triggers when a new direct message, including a thread reply, is sent to a user.
TriggerInstant
Get Category Schema
Retrieve the schema for the read-only Category resource.
ActionInstant
Message Reaction Added
Triggers when a reaction is added to a message.
TriggerInstant
Get Gift
Retrieve details of a gift, including its price and availability.
ActionInstant
Message Reaction Removed
Triggers when a reaction is removed from a message.
TriggerInstant
Get Public Template
Retrieve details of a public template.
ActionInstant
New Bot Message Received Trigger
Triggers when a bot posts a new message in a channel.
TriggerInstant
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,500+ 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.
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 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything 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 Slack and Amcards
Connect any two apps with Notis in the middle.
Slack and Amcards, or any other combination from 1,500+ 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.