Skip to content

Adding FAQs #6419

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 29, 2024
Merged

Adding FAQs #6419

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
35c64ea
Adding FAQs
cmastr Apr 22, 2024
893186b
got carried away with copy
cmastr Apr 22, 2024
6b4a009
Update index.md
cmastr May 29, 2024
c92bfa3
Apply suggestions from code review
cmastr May 29, 2024
eb1f3b5
Update index.md
cmastr May 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions src/connections/destinations/catalog/actions-webhook/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,19 @@ Segment's Webhooks (Actions) destination uses internet protocol and HTTP callbac
## Batch size limits

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`.

## FAQs

### Why is a Webhooks (Actions) Destination helpful with end-to-end tests?
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.

#### Connect a Webhook Actions destination to your workspace
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.
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.
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.
4. Add the endpoint you copied from Step 2 to the Webhook Actions Mapping's URL in Step 3.
5. Enable the Mapping.
6. Enable the Webhook Actions destination.
7. Begin sending events to your source.
8. Verify those events throughout the Segment pipeline (source debugger/ event delivery).
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.