--- title: How to Create a Trigger Webhook in the ID Management System (IDMS) description: "Learn how to configure a trigger webhook in [the ID123 ID Management System](https://www.id123.io/id-management-system/) to send real-time data to external systems when a specific event occurs. This guide walks you through each step of the setup, from choosing the events that…" url: "https://www.id123.io/knowledgebase/how-to-create-a-trigger-webhook/" updated: "2026-10-16" category: ID Management System / Integrations --- # How to Create a Trigger Webhook in the ID Management System (IDMS) Learn how to configure a trigger webhook in [the ID123 ID Management System](https://www.id123.io/id-management-system/) to send real-time data to external systems when a specific event occurs. This guide walks you through each step of the setup, from choosing the events that fire the webhook to mapping your data and configuring authentication. ## What is a Webhook? A webhook is a way for one system to send real-time data to another system whenever a specific event takes place. It works by sending an automated HTTP request to a pre-defined URL. Webhooks are ideal for integrating external applications, enabling them to stay synchronized with your internal data changes. ## What is a Trigger Webhook? A trigger webhook is a type of webhook that activates when a specific event or condition occurs within [the ID Management System (IDMS)](https://www.id123.io/id-management-system/). When the trigger condition is met—such as a new card being created—the webhook sends data to an external service or application via a specified URL. ## Before You Begin: Open the Webhook Creation Page - Log into your IDMS admin account. - In the left-hand navigation panel, click 'Integrations'. - Select 'Webhooks' from the options. - Click the 'Create A Webhook' button to begin the setup process. The setup has three steps: Webhook Type, Data Mapping, and Authorization. ![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-15-at-10.52.49-AM-scaled.webp) ## Step 1: Webhook Type - Enter a 'Webhook Name' to serve as an internal label that helps you identify the webhook in the webhooks table. - Select 'Trigger' as the webhook type. A trigger webhook automatically sends data from the IDMS to an external system when an event occurs. - Choose one or more event categories: Card Record Events, Card Status Events, Card Print Events, Barcode Scanner Events, or Card Moderation Events. Hover over a category to see all of the triggers it includes. - Choose which card record groups this webhook applies to: - **All Card Record Groups** (default): the webhook fires for events in every card record group. - **Specific Card Record Groups**: select a card record group from the dropdown. The webhook fires only for events in that group. - Once configured, click 'Next' to continue. ![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-15-at-10.54.06-AM.webp)![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-15-at-10.54.59-AM.webp) ## Step 2: Data Mapping - A summary at the top of the step shows your webhook name, webhook type, and selected events. - The 'Webhook Events' section lists the event values included in the categories you selected. To leave out an event value you don't need, click the trash icon next to it. ![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-15-at-10.55.35-AM.webp) ### Map Your Webhook Data Fields Below the 'HTTP Headers' section, use the 'Webhook Data Mapping' section to choose the card data you want to send in the request body. - Every available ID123 variable for your card record group is mapped by default. In the 'Payload Variable' column, change any name to match what your external application expects. - To remove a field you don't want to send, click the trash icon next to it. - To add a field back, select 'Add New Data Mapping Row' search for the ID123 variable by name, and click 'Add'. - To change your events or card record groups, select 'Back' to return to Step 1. When your mapping is complete, press 'Next'. ![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-15-at-10.56.15-AM.webp) ## Step 3: Authorization - Type in your 'Trigger URL.' This is the endpoint URL of the external system that will receive the webhook data. - Make sure the receiving system is ready to accept webhook requests at this URL. - Select the 'Authorization Header Type' your receiving system requires: - **None**: no authorization header is sent with the request. - **API Key**: the **Authorization Header Name** is pre-filled with `X-Api-Key`. Enter the API key from your receiving system in the **Authorization Header Value** field. - **OAuth 2.0**: enter the **Client Secret**, **Client ID**, **Supported Scope**, and **Access Token URL** from your receiving system, and confirm the **Trigger API URL**. The IDMS uses these credentials to get an access token and sends it in the `Authorization` header as `Bearer `. Click **Test Connection** to check the credentials before you save. - Click 'Save'. Your new trigger webhook appears on the Webhooks page. ![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-15-at-10.56.29-AM.webp)![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-16-at-3.08.48-PM.webp)![](https://www.id123.io/wp-content/uploads/2024/09/Screenshot-2026-10-16-at-3.10.38-PM.webp) For assistance please contact support: support@id123.io.