> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.drimify.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Configuring Webhook Integrations Within Your App

# Configuring Webhook Integrations Within Your App

Once you have created your webhook integrations at the account level (Settings → Integrations), you can activate and configure them individually within each Drimify app. This is done from the **Integrations** step inside the app editor.

## Overview

The in-app Integrations panel has a master toggle at the top. When enabled, it exposes two configuration areas:
* **Add Webhook Integrations** — select which of your saved integrations should be active for this specific app
* **Send data to integrations** — control exactly when participant data is transmitted

## Adding Webhook Integrations to an App

Use the **Add Webhook Integrations** field to search for and attach one or more of the integrations you have already configured in your account. Only integrations that have been made available to the current workspace will appear here.

You can attach multiple integrations to a single app if needed — for example, sending data to both HubSpot and a Custom API simultaneously.

## Send Data to Integrations

This section controls the trigger events that cause data to be sent. Each trigger can be independently toggled on or off.

| Trigger | Description | Availability |
| ---- |
| **After login** | Fires as soon as a participant logs into the experience | Combo™, Dynamic Path™, and Advent Calendar only |
| **After form submission** | Fires when a participant submits a form within the app | All app types |
| **At game completion** | Fires when a participant completes the game or experience | All app types |

### After Login
> ⚠️ **This trigger is only available for Combo, Dynamic Path, and Advent Calendar apps.**

When enabled, the webhook fires immediately after a user successfully authenticates into the experience — before they interact with any content. This is useful for syncing login events or pre-populating CRM records as soon as a known participant enters your experience.

### After Form Submission

When enabled, the webhook fires each time a participant submits a form inside the app. This is ideal for capturing lead data, registration details, or opt-ins in real time.

### After Game Completion

When enabled, the webhook fires once the participant reaches the end of the experience. This is the most common trigger, as it ensures all data (score, time taken, prize, etc.) is available and complete before being transmitted.

## Recommended Configurations

* If your goal is **lead capture**, enable **After form submission** so data is sent even if the participant does not finish the experience.
* If your goal is **results and scoring**, enable **At game completion** to ensure all game data fields (e.g. `score`, `timeTaken`, `levelsPlayed`, `prizeRef`) are populated before the payload is sent.
* For **Combo, Dynamic Path, or Advent Calendar** apps with gated access, enabling **After login** lets you sync participants to your CRM the moment they enter, regardless of how far they progress.
* You can enable **multiple triggers simultaneously** if you need data sent at several points during the participant journey.