Review Amcards cards when your Airtable schema changes
When your Airtable structure changes, get a timely look at your Amcards inventory so card-related follow-up does not disappear into a forgotten base.
Trigger
Base Schema Changed
Triggers when tables, fields, or views change in an Airtable base.
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
Schema changes can disrupt the context behind outreach tracking, leaving founders unsure which card assets still need attention.
- Bring card inventory into the same review moment as a base change.
- Reduce the need to switch between Airtable and Amcards to remember what to inspect.
- Surface a concise review based on the cards Amcards actually returns.
Setup
Build it in a few focused steps.
- 1Connect Airtable and Amcards once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis the outcome in plain language from any channel.
- 3In one instruction, ask Notis to review the returned Amcards cards after the Airtable schema changes and report relevant cards for manual review.
- 4Pick the Airtable Base Schema Changed trigger and choose where run reports should go.
- 5Test with one real schema change and confirm the report reflects available card data.
Questions about this workflow
Does this automation update Airtable or Amcards?
No. The available Amcards action retrieves cards. Notis can summarize the returned data in its run report, but this workflow does not write changes to either app.
Can it tell which cards are affected by a changed field?
Only if the returned card data and the context you provide make that relationship clear. The listed action does not provide Airtable field history or a mapping between Airtable fields and cards.
What happens when the schema changes?
The Airtable event starts the automation. Notis retrieves Amcards cards and reports a focused review based on the prompt you gave it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtable to Amcards. A trigger fires from one place; an action lands in another.
Airtable 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.
Base Metadata Changed
Triggers when an existing Airtable base changes its name or permission level.
Base Schema Changed
Triggers when tables, fields, or views change in an Airtable base.
User Profile Changed
Triggers when the connected Airtable user's profile information changes.
View Created
Triggers when a new view is created in an Airtable base.
View Deleted
Triggers when a previously known Airtable view is deleted.
View Metadata Changed
Triggers when an Airtable view changes its name or type.
Connect any two apps with Notis in the middle.
Airtable 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.