Skip to content

add information about Source Function usage #4548

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.

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 2 commits into from
Apr 11, 2023
Merged
Changes from all commits
Commits
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
4 changes: 3 additions & 1 deletion src/connections/destinations/catalog/repeater/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,12 @@ This destination is maintained by Segment and is not available to customers on t

## Getting Started

The Repeater destination forwards events from a source back into another source, as though that event occurred in the second source.
The Repeater destination forwards events from a source back into another source as though that event occurred in the second source.

Events are not cached in the Repeater, so it only handles real-time events. You can specify multiple sources as Repeater destinations.

If you need to send events to a Source Function, please use the [Webhooks (Actions)](/docs/connections/destinations/catalog/actions-webhook/) destination instead. The Repeater bypasses the code of a Source Function and sends data only to the write key. The Webhook destination allows data to be sent through the Source Function code as expected.

## Configuration

Add the Repeater as a destination for the source that you want to replicate events from.
Expand Down