Refresh your contact review after an Airtable view changes
When a view changes, the work behind it may have shifted too. Prompt a fresh Amcards contact review with the updated context so priorities stay easy to revisit.
Trigger
View Metadata Changed
Triggers when an Airtable view changes its name or type.
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
Renamed or reworked views can make it harder to remember which contacts belong in a founder's current outreach focus.
- Use view changes as a reminder to reconsider outreach focus.
- Bring relevant Amcards contact details into a single automation report.
- Keep interpretation grounded in the context you provide, instead of assuming the view's meaning.
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.
- 3Ask Notis to retrieve Amcards contacts and organize a review using the updated view context you provide.
- 4Pick the Airtable View Metadata Changed trigger and choose where run reports should go.
- 5Test with one real view metadata change and confirm the report does not infer unavailable Airtable details.
Questions about this workflow
Does the trigger include the old and new view names?
The listed event says it fires when a view changes its name or type, but no event payload fields are specified here. Do not rely on old or new values unless they are available in your setup.
Will the workflow update contact priorities in Amcards?
No. Get Contacts retrieves contact information. Notis can organize a review in the run report, but this action does not update Amcards.
What context should I provide?
Describe what the view represents and the contact criteria you want Notis to consider. If a relevant status or history is not returned by Amcards, provide it separately.
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.