Skip to content

Commit 02b1e09

Browse files
committed
add last section
1 parent acdf360 commit 02b1e09

File tree

1 file changed

+12
-13
lines changed
  • src/connections/destinations/catalog/actions-webhook-extensible

1 file changed

+12
-13
lines changed

src/connections/destinations/catalog/actions-webhook-extensible/index.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -49,12 +49,12 @@ You've now completed setup, and your destination is ready for event mapping and
4949

5050
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:
5151

52-
1. From your destination's setting page, click **Mappings**, then **+New Mapping**.
52+
1. From your destination's settings page, click **Mappings**, then **+New Mapping**.
5353
2. On the Activate data screen, select the action you want to use.
5454
3. Define your event trigger, then click **Load Test Event From Source**.
5555
4. In the Map field section, define the API endpoint (URL) and the HTTP method (`POST`, `PATCH`, `PUT`).
5656
5. Map payload fields:
57-
- Map individual fields or select a specific object from a test event.
57+
- 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.
5858
- (Optional) Use a [destination insert function](/docs/connections/functions/insert-functions/) to transform the payload according to the API specification.
5959
6. Configure optional parameters:
6060
- **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
6363
8. Click **Save**, then click **Next**.
6464
9. Give your mapping a name, then click **Save and enable**.
6565

66-
Your mapping is now enabled.
66+
Your mapping is now enabled. Go to the next section to finish setup.
6767

68-
> **Note**: Segment supports batching the entire payload but not specific objects within the payload.
68+
## 4. Enable the destination
6969

70-
## Known limitations
70+
Follow these steps to enable your new destination:
7171

72-
- **Token Expiration Issue**: If a token expires before a test event is sent, the test event may fail with a 401 error. Workarounds include:
73-
1. Using the **Event Tester** to validate connections.
74-
2. Reconnecting OAuth by editing and saving settings to fetch a new token.
75-
76-
## Enabling the destination
72+
1. Return to the **Basic Settings** in your destination's **Settings** tab.
73+
2. Toggle **Enable Destination** to on, then click **Save Changes**.
7774

78-
1. Enable the destination in the **Settings** page if it is not already enabled.
79-
2. Save the configuration to ensure "Extensible Webhooks" is live.
75+
Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints.
8076

81-
Congratulations! Your Extensible Webhooks destination is now set up and ready to send data to your webhook endpoints.
77+
## Troubleshooting
8278

79+
- **Token Expiration Issue**: If a token expires before a test event is sent, the test event may fail with a 401 error. Workarounds include:
80+
1. Using the **Event Tester** to validate connections.
81+
2. Reconnecting OAuth by editing and saving settings to fetch a new token.

0 commit comments

Comments
 (0)