Skip to main content
All CollectionsZapier IntegrationsIntroduction to Zapier
Difference Between "Tapper Created" and "Tapper Updated" Triggers
Difference Between "Tapper Created" and "Tapper Updated" Triggers

Understanding the Difference Between "Tapper Created" and "Tapper Updated" Triggers

Updated over a week ago


Cardtapp offers a myriad of features to help users manage their contacts efficiently. Among these features are the "Tapper Created" and "Tapper Updated" triggers. While they might sound similar, they cater to different events within Cardtapp. Distinguishing between the two is essential to ensure the accuracy and effectiveness of your automation workflows.

Tapper Created: The Birth of a New Contact

Definition: The "Tapper Created" trigger is activated whenever a new contact is introduced into Cardtapp.

Common Use Cases:

  1. New Business Leads: When a potential client provides their contact information, either through a web form or a manual entry, the "Tapper Created" trigger can activate a Zap to send a welcome email or add the lead to a CRM system.

  2. Event Attendees: After attending an event or webinar, a participant's details might be added to Cardtapp. This can trigger a follow-up email or a survey about the event.

Tapper Updated: Modifying Existing Information

Definition: The "Tapper Updated" trigger comes into action when there's a change in the details of a contact already present in Cardtapp.

Common Use Cases:

  1. Updating Contact Details: If a contact changes their phone number or address, this trigger can activate a Zap to update this information in other linked platforms, ensuring consistency across all systems.

  2. Status Changes: If a contact's status changes, such as moving from a "lead" to a "customer," the "Tapper Updated" trigger can initiate a series of actions, like sending a congratulatory email or offering special discounts.

Why Distinguishing Between the Two is Essential

  1. Relevance of Actions: By understanding which trigger is activated, users can ensure that the subsequent actions are relevant. For instance, you wouldn't want to send a welcome email to a contact whose details were merely updated.

  2. Resource Optimization: Differentiating between these triggers ensures that resources are used efficiently. This prevents unnecessary actions from being taken and reduces the risk of overwhelming contacts with irrelevant communications.

  3. Data Integrity: It ensures that data across various platforms remains consistent. For example, using the "Tapper Updated" trigger ensures that a contact's modified details are reflected everywhere, preventing discrepancies.


While both "Tapper Created" and "Tapper Updated" triggers play pivotal roles in the Cardtapp ecosystem, they cater to different events. By grasping the nuances between them, users can set up more accurate, efficient, and effective Zaps, ensuring a seamless experience for both themselves and their contacts.

Did this answer your question?