> ## Documentation Index > Fetch the complete documentation index at: https://loops.so/docs/llms.txt > Use this file to discover all available pages before exploring further. # Incoming webhooks > Send data to Loops from supported platforms using webhooks. export const SupabaseIcon = () => { return ; }; Incoming webhooks allow you to: * Create and update contacts * Send events to trigger workflows This feature lets external platforms send webhook events directly to Loops, making it straightforward to create or update contacts in Loops automatically when changes happen in other platforms. You can also trigger events when webhooks arrive in Loops so you can send automated email after something happens in your other accounts. ## How it works First, you create webhook endpoints in your Loops account. These allow other platforms to send data automatically and directly to Loops. You then create webhooks in the external platforms, which send event data to your Loops endpoint URLs. Note: we only process webhook events listed for each provider (and which contain an email address). We return helpful messages in responses if there is an issue processing a webhook event. Check the webhook logs in your external platforms for more details. For each type of webhook event, you can sync customer data like names and assign user groups, as well as trigger workflows via [events](/events). Incoming webhook configuration ### Syncing contacts The primary use case for incoming webhooks is to create and update contacts in your Loops audience. When data arrives in Loops, we grab the email address to create and update contacts in your Loops audience. To this end, we only support incoming events that contain an email address. You can choose to update first and last name data from the webhook event as well. Additionally, you can assign a user group value to each new contact, which helps create segments from webhook-created contacts. Any new contact created via a webhook will have a source like "Stripe webhook" so you know where it originated from. For events that reference record deletion, like Stripe's `customer.deleted` event, you can choose to unsubscribe or delete contacts in Loops. ### Subscribing to mailing lists You can subscribe contacts to [mailing lists](/contacts/mailing-lists) when they are created or updated via a webhook. ### Sending emails Incoming webhooks can trigger emails if you connect events to [workflow triggers](/workflows/triggers). This can be useful if you want to automatically send emails when something has happened in the external platform, for example a successful payment in Stripe or a new sign up in Clerk. Just create a workflow using the **Event received** trigger and select the event you want to trigger on. Event received trigger You can also trigger custom events from incoming webhooks if you specify an event in the **Trigger an additional custom event** section in the configuration. ## Create webhook endpoints in Loops To start sending webhook events to Loops, go to your chosen [integration's settings page](https://app.loops.so/settings) in Loops. A webhook endpoint will be created for you. Copy the endpoint URL and paste it into your external platform. For Stripe, install the Loops app, which lets you skip the creating of webhooks as it's handled for you. Endpoint form You may need to copy-paste signing secrets between the platform and Loops for extra security (we will prompt you when this is necessary and give you the steps to do it). ## Supported platforms Learn more about how to configure webhooks for each platform, and see which events we support, below.