Get an Amcards card snapshot from a webhook
Request a current card inventory whenever your process reaches a planning checkpoint.
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
Planning workflows often need campaign asset context but have no simple handoff into Amcards.
- Connect external planning steps to Amcards
- Keep snapshots on demand
- Give collaborators a consistent review format
Setup
Build it in a few focused steps.
- 1Connect Amcards once in Notis.
- 2Create an automation for webhook based card snapshots.
- 3Tell Notis to retrieve Amcards cards and summarize them using the webhook context.
- 4Pick a Notis webhook trigger and choose where run reports go.
- 5Send one test webhook with a real campaign brief.
Questions about this workflow
What must the webhook include?
Include enough campaign or audience context for Notis to decide which cards matter.
Does the webhook create a card?
No. The action retrieves existing cards only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slackbot to Amcards. A trigger fires from one place; an action lands in another.
Slackbot 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.
Slackbot 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.