Stop Duplicate Leads Before They Clutter Your Database
One person, one record.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A lead fills out your form multiple times, or they're already in your CRM from a previous interaction. You don't find out until weeks later, and your database is full of junk.
- Catch duplicate leads instantly
- Reduce CRM data cleanup work
- Improve lead data quality automatically
- Never waste time chasing duplicate accounts
Setup
Build it in a few focused steps.
- 1Connect Amcards to Notis via the portal.
- 2Tell Notis: 'When a lead submits my web form, check Amcards to see if they already exist in my database.' Set this up in Automations with a webhook.
- 3Notis will provide a webhook URL. Add it to your form platform (Typeform, Zapier, custom API, etc.).
- 4Get notified via email or Slack when duplicates are detected so you can merge records or skip adding them.
- 5Test by submitting a form with an email that already exists in Amcards and confirm the duplicate detection works.
Questions about this workflow
What counts as a duplicate?
Notis checks email, phone, and name. You can customize the matching criteria to fit your needs.
What happens when a duplicate is found?
Notis alerts you with the existing record details. You decide to merge, skip, or add as a new contact.
Does this work with all form platforms?
Yes. Use the webhook URL with any form tool (Typeform, Wufoo, custom APIs, etc.).
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Amcards. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.