As you explore Kitetags Apps available for tap Interactions, you will want to understand what these different Apps are. One key thing about Kitetags, and NFC, is that no mobile phone app is required. This is a huge avantage over QR codes and even traditional phone apps. There is inherent friction in requiring a user to install an application. For QR codes, in a phone, it requires you to launch a camera app or a special QR scanner. This too has some friction involved.

Kitetags are different. You can experience ann application within the time it takes to tap your phone and allow the browser to launch. The variety of possibilities range from simple website redirect to a complete AI powered integration on Zapier.com.

Internal Apps

These apps are offered by Kitetags and ready for use with your Kitetag Interactions. We will be adding new apps to expand the capabilities of your Kitetags.

URL Redirect Starter KI

This is the first interaction you will experience when claiming your first tag. It is simply a redirect to an internal web page that shows off your callsign and UID, and gives you a call to action. You can remove this from your tag configuration at any time.

Test Flight

Displays the UID, built-in data (e.g. callsign), and location data (if enabled) on the phone’s browser. Useful for testing Kitetags and troubleshooting. It also shows off the capabilities of HTML5 Geolocation.

URL Redirect

Redirects a phone’s browser to a target URL after tappinng a Kitetag. The target URL you provide is the URL to send the user to after a tap.

Requirements:

  • Minimally you will need a KDS for a “Target Url”. Any other data provided by a KDS will be ignored.

Use Cases:

  • Product Marketing websites
  • Company Websites
  • Freelancer Websites
  • Event Pages
  • A Web Form
  • a mobile App launcher

vCard

Creates a vCard from the Kitetag Data and enables download to a phone’s contact app.

Requirements:

  • A Contact Info KDS is recommended
  • Care must be taken not to use KDS types that aren’t supported by the VCard specification

Use Cases:

  • A contact sharing application
  • A company contact info list
  • A dynamic datastore for contact information (you can update the data contained in the VCard at any time)

Webhooks

Generates a JSON body from the Kitetag Data and sends a POST request to the specified URl endpoint. Any data provided in the KDS will be sent when the tag is tapped.

Requirements:

  • It is recommended to include any data you would like to transmit in the webhook

Use Cases:

  • A cloud integration with your favorite SaaS service
  • custom / proprietary service integration

External Third-party Integrations

These apps allow you to build Kitetag Interactions that integrate with third-party apps and services. Typically, you’ll need an account with these other services.

Zapier

Triggers a zap which can use the Kitetags Data for actions in the following steps of a workflow. Requires a Zapier account and authenticating with an Kitetag API Key. After connecting Kitetags with Zapier, build and publish zaps that are triggered when a Kitetag is tapped.

Requirements:

  • Please use any data you need to send into zapier
  • You must obtain your kitetags API key from here: https://kitetags.com/apps

Use Cases:

  • AI powered Zapier workflow: Use Zapier AI prompts to generate your workflows
  • Custom integration with arbitrary services: imagine, a tap triggers a Zapier webhook which then has an action of data being sent into a google sheet which then sends an SMS message and then inserts data into a CRM

References

Last updated 07 Jun 2025, 15:48 +0900 . history