What does the Webhooks app do?

The Webhooks app generates a JSON payload from your Kitetag’s KDS data and sends it as an HTTP POST request to a URL endpoint you specify. Every field in the KDS is included in the payload.

The tapper does not need a phone app. The Kitetags platform processes the tap and delivers the webhook on the server side.

When should you use Webhooks?

Use Webhooks when you need tap events to reach your own infrastructure. This app is the right choice when:

  • You run a SaaS product that needs to react to NFC taps.
  • You have a custom or proprietary backend that processes tap data.
  • You are building IoT workflows where a physical tap triggers a server-side action.
  • You want full control over the data format and processing logic.

What are the requirements?

  • A KDS assigned to your tag with the data fields you want in the payload.
  • A publicly accessible URL endpoint that accepts HTTP POST requests with a JSON body.

How do you set up the Webhooks app?

  1. Prepare your endpoint. Set up a URL on your server that accepts HTTP POST requests and can parse a JSON body.
  2. Create a KDS in the Kitetags dashboard with the fields you want included in the JSON payload.
  3. Assign the KDS to your tag or Group.
  4. Fill in the KDS data for each tag.
  5. Set the app to Webhooks in the tag’s Kitetag Interaction (KI) settings. Enter your endpoint URL in the configuration.
  6. Tap the tag to test. Check your server logs to confirm the POST request arrived with the expected JSON payload.

What does the JSON payload look like?

The payload includes every field defined in the tag’s KDS. The exact structure depends on your KDS configuration. A typical payload looks like this:

  {
  "tag_uid": "04:A2:3B:C1:D4:E5:80",
  "callsign": "lobby-checkin-01",
  "kds_data": {
    "Location": "Building A Lobby",
    "Department": "Facilities",
    "Action": "check-in"
  },
  "tapped_at": "2026-03-27T14:32:00Z"
}

What are common use cases?

  • SaaS integration — Send tap data to platforms like Airtable, Notion, or your internal dashboard via their webhook ingestion endpoints.
  • Custom and proprietary services — Route tap events to your own backend for processing, logging, or triggering business logic.
  • IoT workflows — Use taps to trigger actions in connected systems, such as unlocking a door, starting a machine, or logging an equipment check.

Next steps

If you prefer a no-code approach to connecting taps with external services, try Zapier. For lower-level API access, see the developer guide.

Last updated 27 Mar 2026, 06:51 +0900 . history