Review contacts when your Airtable team creates a view
A new view often signals a new way of organizing work. Let Notis bring your Amcards contacts into that moment so potential outreach follow-up is easier to spot.
Trigger
View Created
Triggers when a new view is created in an Airtable base.
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
New views can represent a fresh workflow or priority, but contact follow-up may stay scattered across apps and go unnoticed.
- Turn a new Airtable view into a prompt for an outreach contact review.
- Keep contact scanning close to the workflow change that prompted it.
- Use only contact details returned by Amcards and context supplied in your instruction.
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 summarize those relevant to the purpose or context you provide for the new view.
- 4Pick the Airtable View Created trigger and choose where run reports should go.
- 5Test with one real view creation and check that the contact review uses returned details accurately.
Questions about this workflow
Can Notis infer what the new Airtable view means?
Not from the event alone. Include the view's purpose or the criteria you want considered in your instruction; the listed trigger only signals that a view was created.
Can the automation send messages to contacts?
No. The listed Amcards action retrieves contacts. The workflow can produce a review in its run report, but it cannot send outreach.
Can I limit which Amcards contacts are returned?
The Get Contacts action supports parameters such as limit, skip, and filters. Notis can use a requested filter when supported, but the available fields may not correspond to Airtable view criteria.
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.