Skip to content

Commit 3289f92

Browse files
authored
Merge pull request #6419 from segmentio/redo_of_PR-5101
Adding FAQs
2 parents 206c692 + eb1f3b5 commit 3289f92

File tree

1 file changed

+16
-0
lines changed
  • src/connections/destinations/catalog/actions-webhook

1 file changed

+16
-0
lines changed

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

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,3 +27,19 @@ Segment's Webhooks (Actions) destination uses internet protocol and HTTP callbac
2727
## Batch size limits
2828

2929
In Webhook Actions mapping, the default value of batch size is `1000`. You can change this value, but there's a maximum batch size limit of `4000`.
30+
31+
## FAQs
32+
33+
### Why is a Webhooks (Actions) Destination helpful with end-to-end tests?
34+
The easiest way to test whether a source's events are sending through the Segment pipeline is with an end-to-end test. Use the steps below to monitor the events arriving to your Segment source and whether they're successfully sending to your destinations. Connecting a Webhooks (Actions) Destination to your sources makes these requests easy to see. For example, if you connect a Webhooks Destination (Webhook Actions Destination) to your source, you'd be able to see the events received by that source and sent to that destination.
35+
36+
#### Connect a Webhook Actions destination to your workspace
37+
1. [Add a new Webhook (Actions) destination](https://app.segment.com/goto-my-workspace/destinations/catalog/actions-webhook) to your source. Make sure you select the intended source to connect this destination to.
38+
2. Visit the webhook's site, and copy the endpoint to your clipboard. An example site you can use is [https://webhook.site/#!/]([url](https://webhook.site/#!/)), but use whichever webhooks site you prefer.
39+
3. Add a mapping to the Webhook Actions destination, and configure Step 1's conditions to allow for all types of events that you're currently sending through that source.
40+
4. Add the endpoint you copied from Step 2 to the Webhook Actions Mapping's URL in Step 3.
41+
5. Enable the Mapping.
42+
6. Enable the Webhook Actions destination.
43+
7. Begin sending events to your source.
44+
8. Verify those events throughout the Segment pipeline (source debugger/ event delivery).
45+
9. Verify the webhook's website which shows the raw JSON for all of the events successfully received by your Segment source and its Webhooks Actions destination.

0 commit comments

Comments
 (0)