From b898af1e23532b786ed2e4f655ca910319be43da Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 17:11:21 -0600 Subject: [PATCH 01/14] add front matter --- .../destinations/catalog/extensible-webhooks/index.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 src/connections/destinations/catalog/extensible-webhooks/index.md diff --git a/src/connections/destinations/catalog/extensible-webhooks/index.md b/src/connections/destinations/catalog/extensible-webhooks/index.md new file mode 100644 index 0000000000..fb87e98e5c --- /dev/null +++ b/src/connections/destinations/catalog/extensible-webhooks/index.md @@ -0,0 +1,4 @@ +--- +title: Extensible Webhooks Destination +id: 66b1f528d26440823fb27af9 +--- \ No newline at end of file From 88bcfe33bf528efb9b6e9818f339ec3899eed23c Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 17:22:56 -0600 Subject: [PATCH 02/14] rename parent folder and add getting started section --- .../actions-webhook-extensible/index.md | 20 +++++++++++++++++++ .../catalog/extensible-webhooks/index.md | 4 ---- 2 files changed, 20 insertions(+), 4 deletions(-) create mode 100644 src/connections/destinations/catalog/actions-webhook-extensible/index.md delete mode 100644 src/connections/destinations/catalog/extensible-webhooks/index.md diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md new file mode 100644 index 0000000000..1dea382a32 --- /dev/null +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -0,0 +1,20 @@ +--- +title: Extensible Webhooks Destination +id: 66b1f528d26440823fb27af9 +--- + +{% include content/plan-grid.md name="actions" %} + +Segment's Extensible Webhooks destination lets you send custom data payloads to any webhook endpoint. With support for flexible payload configuration, multiple authentication methods, and real-time data flow, Extensible Webhooks can help you integrate with internal systems or tools not covered by Segment’s standard destinations. + +Segment maintains this destination. For any issues, [contact Segment Support](friends@segment.com). + +## Getting started + +1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Extensible Webhooks." +2. Select **Extensible Webhook** and Click **Add destination**. +3. Select an existing source to connect to the destination. +4. Enter a name for the destination and click **Create destination.** + +By default, the new destination is disabled. You'll need to enable it later in the **Settings** page. + diff --git a/src/connections/destinations/catalog/extensible-webhooks/index.md b/src/connections/destinations/catalog/extensible-webhooks/index.md deleted file mode 100644 index fb87e98e5c..0000000000 --- a/src/connections/destinations/catalog/extensible-webhooks/index.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: Extensible Webhooks Destination -id: 66b1f528d26440823fb27af9 ---- \ No newline at end of file From 055b0617d7965d2be1cd8f1db2a2f68e2aa1f2b1 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 18:13:30 -0600 Subject: [PATCH 03/14] some formatting stuff --- .../destinations/catalog/actions-webhook-extensible/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 1dea382a32..68443387cd 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -9,12 +9,13 @@ Segment's Extensible Webhooks destination lets you send custom data payloads to Segment maintains this destination. For any issues, [contact Segment Support](friends@segment.com). -## Getting started +## 1. Create a new Extensible Webhooks destination 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Extensible Webhooks." 2. Select **Extensible Webhook** and Click **Add destination**. 3. Select an existing source to connect to the destination. 4. Enter a name for the destination and click **Create destination.** -By default, the new destination is disabled. You'll need to enable it later in the **Settings** page. +By default, the new destination is disabled. You'll enable it in the next section. +## 2. \ No newline at end of file From 45cd3303c6f61e121577ae6783ea170322622f14 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 18:38:24 -0600 Subject: [PATCH 04/14] add authentication section --- .../actions-webhook-extensible/index.md | 53 ++++++++++++++++++- 1 file changed, 52 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 68443387cd..b01a4c1c90 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -18,4 +18,55 @@ Segment maintains this destination. For any issues, [contact Segment Support](fr By default, the new destination is disabled. You'll enable it in the next section. -## 2. \ No newline at end of file +## 2. Set up authentication + +Before you can enable the new destination, you'll first need to choose an authentication option: + +1. On the new destination's page, navigate to **Settings > Authentication.** +2. Choose one of the following authentication options: + - **No authentication**: Segment doesn't manage authentication. + - **Bearer token**: Segment automatically includes a bearer token in the API request header. + - **OAuth 2.0**: Segment manages the OAuth token lifecycle, including fetching and refreshing tokens. +3. For OAuth 2.0, select one of the following flows: + - **Authorization code**, which requires the following fields: + - Client ID + - Client secret + - Authorize URL + - Access Token URL + - Refresh Token URL (usually the same as the Access Token URL) + - Scopes + - **Use client credentials**, which requires the following: + - Client ID + - Client Secret + - Access Token URL + - Refresh Token URL (usually the same as the Access Token URL) + - Scope +4. Save the settings, then click **Connect** to activate the connection. + +You've now completed setup, and your destination is ready for event mapping and data configuration. + +## Mapping and data configuration + +1. Define the API endpoint (URL) and the HTTP method (POST, PATCH, PUT). +2. Configure optional parameters: + - **Batch Size**: Specify batch size if the API supports batching entire payloads. + - **Headers**: Add required headers (e.g., `content-type` defaults to `application/json`). +3. Map payload fields: + - Map individual fields or select a specific object from a test event. + - (Optional) Use a destination insert function to transform the payload according to the API specification. +4. Send a test event to validate the setup. Debug any errors related to payload configuration or authentication. + +> **Note**: Segment supports batching the entire payload but not specific objects within the payload. + +## Known limitations + +- **Token Expiration Issue**: If a token expires before a test event is sent, the test event may fail with a 401 error. Workarounds include: + 1. Using the **Event Tester** to validate connections. + 2. Reconnecting OAuth by editing and saving settings to fetch a new token. + +## Enabling the destination + +1. Enable the destination in the **Settings** page if it is not already enabled. +2. Save the configuration to ensure "Extensible Webhooks" is live. + + From acdf360d9a0d02532067e3df0c599a1f28dd9351 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 18:51:45 -0600 Subject: [PATCH 05/14] add mapping instructions --- .../actions-webhook-extensible/index.md | 26 +++++++++++++------ 1 file changed, 18 insertions(+), 8 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index b01a4c1c90..541022a9b0 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -45,16 +45,25 @@ Before you can enable the new destination, you'll first need to choose an authen You've now completed setup, and your destination is ready for event mapping and data configuration. -## Mapping and data configuration +## 3. Mapping and data configuration (optional) -1. Define the API endpoint (URL) and the HTTP method (POST, PATCH, PUT). -2. Configure optional parameters: - - **Batch Size**: Specify batch size if the API supports batching entire payloads. - - **Headers**: Add required headers (e.g., `content-type` defaults to `application/json`). -3. Map payload fields: +With authentication in place, you can now define how data flows from Segment to your webhook endpoints. Follow these steps to configure mappings and test the setup: + +1. From your destination's setting page, click **Mappings**, then **+New Mapping**. +2. On the Activate data screen, select the action you want to use. +3. Define your event trigger, then click **Load Test Event From Source**. +4. In the Map field section, define the API endpoint (URL) and the HTTP method (`POST`, `PATCH`, `PUT`). +5. Map payload fields: - Map individual fields or select a specific object from a test event. - - (Optional) Use a destination insert function to transform the payload according to the API specification. -4. Send a test event to validate the setup. Debug any errors related to payload configuration or authentication. + - (Optional) Use a [destination insert function](/docs/connections/functions/insert-functions/) to transform the payload according to the API specification. +6. Configure optional parameters: + - **Batch size**: Specify batch size if the API supports batching entire payloads. + - **Headers**: Add required headers (for example, `content-type`, which is required, defaults to `application/json`). +7. Send a test event to validate the setup. Segment logs the response from your destination so that you can debug any errors (which are usually related to the payload configuration or authentication issues). +8. Click **Save**, then click **Next**. +9. Give your mapping a name, then click **Save and enable**. + +Your mapping is now enabled. > **Note**: Segment supports batching the entire payload but not specific objects within the payload. @@ -69,4 +78,5 @@ You've now completed setup, and your destination is ready for event mapping and 1. Enable the destination in the **Settings** page if it is not already enabled. 2. Save the configuration to ensure "Extensible Webhooks" is live. +Congratulations! Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. From 02b1e09b7083f40ccb1beb28555a2b093b6c3f20 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 18:58:37 -0600 Subject: [PATCH 06/14] add last section --- .../actions-webhook-extensible/index.md | 25 +++++++++---------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 541022a9b0..23e035909f 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -49,12 +49,12 @@ You've now completed setup, and your destination is ready for event mapping and With authentication in place, you can now define how data flows from Segment to your webhook endpoints. Follow these steps to configure mappings and test the setup: -1. From your destination's setting page, click **Mappings**, then **+New Mapping**. +1. From your destination's settings page, click **Mappings**, then **+New Mapping**. 2. On the Activate data screen, select the action you want to use. 3. Define your event trigger, then click **Load Test Event From Source**. 4. In the Map field section, define the API endpoint (URL) and the HTTP method (`POST`, `PATCH`, `PUT`). 5. Map payload fields: - - Map individual fields or select a specific object from a test event. + - Map individual fields or select a specific object from a test event. Segment supports batching the entire payload but not specific objects within the payload. - (Optional) Use a [destination insert function](/docs/connections/functions/insert-functions/) to transform the payload according to the API specification. 6. Configure optional parameters: - **Batch size**: Specify batch size if the API supports batching entire payloads. @@ -63,20 +63,19 @@ With authentication in place, you can now define how data flows from Segment to 8. Click **Save**, then click **Next**. 9. Give your mapping a name, then click **Save and enable**. -Your mapping is now enabled. +Your mapping is now enabled. Go to the next section to finish setup. -> **Note**: Segment supports batching the entire payload but not specific objects within the payload. +## 4. Enable the destination -## Known limitations +Follow these steps to enable your new destination: -- **Token Expiration Issue**: If a token expires before a test event is sent, the test event may fail with a 401 error. Workarounds include: - 1. Using the **Event Tester** to validate connections. - 2. Reconnecting OAuth by editing and saving settings to fetch a new token. - -## Enabling the destination +1. Return to the **Basic Settings** in your destination's **Settings** tab. +2. Toggle **Enable Destination** to on, then click **Save Changes**. -1. Enable the destination in the **Settings** page if it is not already enabled. -2. Save the configuration to ensure "Extensible Webhooks" is live. +Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. -Congratulations! Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. +## Troubleshooting +- **Token Expiration Issue**: If a token expires before a test event is sent, the test event may fail with a 401 error. Workarounds include: + 1. Using the **Event Tester** to validate connections. + 2. Reconnecting OAuth by editing and saving settings to fetch a new token. From 8e3d972a95dd6e5be26ad6b241db57d17a7e557d Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 19:04:09 -0600 Subject: [PATCH 07/14] add overview steps [netlify-build] --- .../catalog/actions-webhook-extensible/index.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 23e035909f..f6164457f9 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -9,6 +9,15 @@ Segment's Extensible Webhooks destination lets you send custom data payloads to Segment maintains this destination. For any issues, [contact Segment Support](friends@segment.com). +## Overview + +To set up and use Extensible Webhooks, you'll follow these four main stages: + +1. **Create the new destination**: Add the Extensible Webhooks destination to your workspace and link it to a source. +2. **Set up authentication**: Configure the required authentication settings to activate the destination. +3. **Map and configure data**: Define how data flows from Segment to your webhook endpoints by mapping fields and customizing the payload. +4. **Enable the destination**: Complete the setup by enabling the destination to start sending data. + ## 1. Create a new Extensible Webhooks destination 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Extensible Webhooks." @@ -76,6 +85,6 @@ Your Extensible Webhooks destination is now set up and ready to send data to you ## Troubleshooting -- **Token Expiration Issue**: If a token expires before a test event is sent, the test event may fail with a 401 error. Workarounds include: - 1. Using the **Event Tester** to validate connections. - 2. Reconnecting OAuth by editing and saving settings to fetch a new token. +### I ran into an issue where my test event failed with a `401` error. What should I do?** + +This error can occur when a token expires before the test event gets sent. To resolve this, use the Event Tester to validate the connection and verify the token is still active. Alternatively, reconnect OAuth by editing and saving the settings. This will fetch a new token and allow the test event to proceed successfully. \ No newline at end of file From 28555a27f3455a136a6a98e09ec74eb66d8e2d25 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 19:04:38 -0600 Subject: [PATCH 08/14] add beta to front matter --- .../destinations/catalog/actions-webhook-extensible/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index f6164457f9..8f1217cd54 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -1,6 +1,7 @@ --- title: Extensible Webhooks Destination id: 66b1f528d26440823fb27af9 +beta: true --- {% include content/plan-grid.md name="actions" %} From ec421a957c27b4f86e820ae31c2bd243bfd52053 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 19 Jan 2025 19:05:06 -0600 Subject: [PATCH 09/14] update front matter [netlify-build] --- .../destinations/catalog/actions-webhook-extensible/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 8f1217cd54..f255b9a005 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -2,6 +2,7 @@ title: Extensible Webhooks Destination id: 66b1f528d26440823fb27af9 beta: true +hidden: true --- {% include content/plan-grid.md name="actions" %} From 0ab2ce7f6b614aeb43ae0c0b8ecf5cae57c8ba20 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 23 Jan 2025 11:29:30 -0600 Subject: [PATCH 10/14] delete troubleshooting section, not needed anymore --- .../catalog/actions-webhook-extensible/index.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index f255b9a005..6d1eb939f2 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -83,10 +83,4 @@ Follow these steps to enable your new destination: 1. Return to the **Basic Settings** in your destination's **Settings** tab. 2. Toggle **Enable Destination** to on, then click **Save Changes**. -Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. - -## Troubleshooting - -### I ran into an issue where my test event failed with a `401` error. What should I do?** - -This error can occur when a token expires before the test event gets sent. To resolve this, use the Event Tester to validate the connection and verify the token is still active. Alternatively, reconnect OAuth by editing and saving the settings. This will fetch a new token and allow the test event to proceed successfully. \ No newline at end of file +Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. \ No newline at end of file From 5c9dda98cc05cbdf5472bf36625201ad78fc65a6 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 23 Jan 2025 11:31:18 -0600 Subject: [PATCH 11/14] cleanup --- .../destinations/catalog/actions-webhook-extensible/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 6d1eb939f2..2fc34b7492 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -27,7 +27,7 @@ To set up and use Extensible Webhooks, you'll follow these four main stages: 3. Select an existing source to connect to the destination. 4. Enter a name for the destination and click **Create destination.** -By default, the new destination is disabled. You'll enable it in the next section. +By default, **the new destination is disabled**. You'll enable it in the next section. ## 2. Set up authentication From 993cf109c3012720f110c46475f810034ce72b99 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 23 Jan 2025 11:33:39 -0600 Subject: [PATCH 12/14] more cleanup [netlify-build] --- .../catalog/actions-webhook-extensible/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index 2fc34b7492..d385be883b 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -51,12 +51,12 @@ Before you can enable the new destination, you'll first need to choose an authen - Client Secret - Access Token URL - Refresh Token URL (usually the same as the Access Token URL) - - Scope + - Scopes 4. Save the settings, then click **Connect** to activate the connection. You've now completed setup, and your destination is ready for event mapping and data configuration. -## 3. Mapping and data configuration (optional) +## 3. Mapping and data configuration With authentication in place, you can now define how data flows from Segment to your webhook endpoints. Follow these steps to configure mappings and test the setup: @@ -68,7 +68,7 @@ With authentication in place, you can now define how data flows from Segment to - Map individual fields or select a specific object from a test event. Segment supports batching the entire payload but not specific objects within the payload. - (Optional) Use a [destination insert function](/docs/connections/functions/insert-functions/) to transform the payload according to the API specification. 6. Configure optional parameters: - - **Batch size**: Specify batch size if the API supports batching entire payloads. + - **Batch size**: Specify the batch size if the API supports batching entire payloads. - **Headers**: Add required headers (for example, `content-type`, which is required, defaults to `application/json`). 7. Send a test event to validate the setup. Segment logs the response from your destination so that you can debug any errors (which are usually related to the payload configuration or authentication issues). 8. Click **Save**, then click **Next**. @@ -80,7 +80,7 @@ Your mapping is now enabled. Go to the next section to finish setup. Follow these steps to enable your new destination: -1. Return to the **Basic Settings** in your destination's **Settings** tab. +1. Return to **Basic Settings** in your destination's **Settings** tab. 2. Toggle **Enable Destination** to on, then click **Save Changes**. Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. \ No newline at end of file From 764655c43ca3f11a275ddf0cfe4909f414f10977 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 23 Jan 2025 11:35:42 -0600 Subject: [PATCH 13/14] add private beta flag on PM request [netlify-build] --- .../destinations/catalog/actions-webhook-extensible/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index d385be883b..ca7f70a960 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -11,6 +11,9 @@ Segment's Extensible Webhooks destination lets you send custom data payloads to Segment maintains this destination. For any issues, [contact Segment Support](friends@segment.com). +> info "Private beta" +> The Extensible Webhooks is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. + ## Overview To set up and use Extensible Webhooks, you'll follow these four main stages: From 8a2f919bc55de2d78c353cb86c9900233e3be095 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 23 Jan 2025 12:13:24 -0600 Subject: [PATCH 14/14] fix typo --- .../destinations/catalog/actions-webhook-extensible/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-webhook-extensible/index.md b/src/connections/destinations/catalog/actions-webhook-extensible/index.md index ca7f70a960..25e1f96e13 100644 --- a/src/connections/destinations/catalog/actions-webhook-extensible/index.md +++ b/src/connections/destinations/catalog/actions-webhook-extensible/index.md @@ -12,7 +12,7 @@ Segment's Extensible Webhooks destination lets you send custom data payloads to Segment maintains this destination. For any issues, [contact Segment Support](friends@segment.com). > info "Private beta" -> The Extensible Webhooks is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. +> Extensible Webhooks is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. ## Overview @@ -86,4 +86,4 @@ Follow these steps to enable your new destination: 1. Return to **Basic Settings** in your destination's **Settings** tab. 2. Toggle **Enable Destination** to on, then click **Save Changes**. -Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints. \ No newline at end of file +Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints.