> ## Documentation Index > Fetch the complete documentation index at: https://docs.inflection.io/llms.txt > Use this file to discover all available pages before exploring further. # Goldcast > Send data from Goldcast to Inflection using inbound webhooks. This guide covers how you can create inbound webhook connection and configure Goldcast for ingesting events data in Inflection * You can create a new **Inbound Webhook** under: * **Assets → Inbound Webhook** Inbound Webhook section under Assets in Inflection * Click **"New Connection"** * Provide a connection **name** and an optional **description** New connection form with name and description fields * Select an **Authentication Method**: No Auth / Basic Auth / API Key. * Enable or disable **"Create New Contact"**: * ✅ If enabled, Inflection will create a **new contact** whenever a new email ID is received * ❌ If disabled, no new contacts will be created Authentication method and Create New Contact options * Click **"Generate webhook"** to create connection * Copy and configure the **webhook URL** and authentication details (if applicable) in Goldcast Generated webhook URL shown after creating the connection ### Step 1: Installing the Webhooks App 1. **Access the Marketplace:** * Go to the [Goldcast Marketplace](https://www.goldcast.io/marketplace) and locate the Webhooks tile. Webhooks tile in the Goldcast Marketplace 2. **Initiate the Connection:** * Click the **Connect App** button to start the installation process. Connect App button for the Webhooks app in Goldcast 3. **Installation Process:** * After clicking, you will be redirected to Goldcast Studio's Integrations page. * A pop-up titled **Install Webhooks** will appear—click the **Install** button. Install Webhooks pop-up in Goldcast Studio 4. **Authentication and Confirmation:** * You will see a confirmation pop-up after the installation. * Complete the authentication process on the next screen, then click **Finish** to finalise the set Installation confirmation pop-up in Goldcast Authentication screen with Finish button in Goldcast ### Step 2: Configuring the Webhook for a Webinar 1. **Create a Test Webinar:** * Log in to Goldcast Studio with your credentials. * Navigate to the **Events** tab, create a new test webinar (select any upcoming date and time you prefer), then open that test webinar's Event Dashboard. 2. **Access the Integrations Section:** * Open the **Integrations** tab within the dashboard. 3. **Go to Webhooks:** * On the Integrations page, select the **Webhooks** option. Integrations tab within the Goldcast event dashboard Webhooks option on the Goldcast Integrations page 4. **Create a New Webhook:** * Click the **Create Webhook** button to open the configuration popup. * **Name:** Enter a descriptive name (for example, "Inflection\<>Goldcast Webhook"). * **Webhook URL→** Paste the **Webhook URL** generated from Inflection. * **Headers:** Leave this field blank as authentication is not required for this test. * **Trigger Activities:** Toggle the options for **Registered** and **Attended** to activate them. * Finally, click **Create** to save your new webhook configuration. Create Webhook configuration popup in Goldcast Newly created webhook listed in Goldcast When a trigger activity occurs, Goldcast sends the data to Inflection. You can view the submission count on the **Connection Details** page. Submission count on the Connection Details page in Inflection ### Step 1 - Enable fields for mapping * Go to "Submission Fields" tab * Enable the required fields and click **Save**. Submission Fields tab with fields enabled for mapping ### Step 2 - Mapping fields * Go to "Connection mapping" tab and click on "Edit" * Here you can define mapping for goldcast submission fields to Inflection contact fields. Mapping the **"Email"** Contact field is required for data to flow into Inflection * Additionally, map other essential fields like `magicLinkUrl` * `magicLinkUrl` is the unique invitation link for each user. You can later use it in email campaigns sent via Inflection. Connection mapping tab showing Goldcast fields mapped to Inflection contact fields Based on your mapping rules: * New contacts will be created in Inflection for each unique email. * Contact fields will be updated accordingly. * Once the Email field is mapped, you can use submission data for journey targeting. You can use Goldcast submissions within **Journeys** as shown below 1. Navigate to: **Journeys → Create New Journey** 2. Add a condition: **Performed a Marketing Activity → Inbound Webhook Sync** Example: An audience filter for all users who **registered** for the webinar. Journey audience filter targeting users who registered for the webinar See expected `activityType` values in Goldcast's doc: [Goldcast Webhooks Payload Structure](https://help.goldcast.io/en_US/7805597141275-Webhooks/17571696255131-goldcast-webhooks-payload-structure). These are the values you'll need to target **registrants** vs. **attendees**. Note that **attended on-demand** will not come over as a separate event; it will come over as **attended** with an `engagementType` that indicates it's on-demand. `engagementType` is a property only on the attended event; this means an attended event will need to fire in order to map the field in Inflection. ### Create email with tokens You can personalise emails for sending - * Registration confirmation * Follow-ups * Feedback requests * And more... Email editor using mapped Goldcast fields as personalization tokens You can also use Goldcast submissions in **Branch by Filter** to tailor communications based on attendee status. Branch by Filter step using Goldcast submission data Goldcast Webhooks Integration Help: [Webhooks Integration](https://help.goldcast.io/en_US/7805597141275-Webhooks/16670925425819-webhooks-integration) List of events - [Goldcast Event Engagement Activities](https://help.goldcast.io/general-integrations/4404985089691-goldcast-event-engagement-activities) All payloads - [Goldcast Webhooks Payload Structure](https://help.goldcast.io/en_US/7805597141275-Webhooks/17571696255131-goldcast-webhooks-payload-structure#1-registration-0)