# Connect Reverse ETL Source to PostScript

This guide takes you through the steps to connect a Reverse ETL source to the PostScript destination.

{{< info >}}
This destination supports mapping data only via the [JSON Mapper]({{< ref "data-pipelines/reverse-etl/developer-guides/json-data-mapping.md" >}}). 

Mapping via [Visual Data Mapper]({{< ref "data-pipelines/reverse-etl/developer-guides/visual-data-mapper.md" >}}) is not supported for this destination.
{{< /info >}}

## Set up the connection 

{{< warning >}}
**The Reverse ETL feature supports only source-driven pipeline configuration.**

Make sure you have [set up a RETL source]({{< ref "sources/reverse-etl/_index.md" >}}) and connected it to your PostScript destination before following the below steps.
{{< /warning >}}

1. [Confirm the connection settings]({{< ref "destinations/streaming-destinations/postscript/setup-guide.md#connection-settings" >}}) for PostScript destination and click **Continue**.
2. Set the [Sync mode]({{< ref "data-pipelines/reverse-etl/developer-guides/sync-modes.md" >}}) to specify how RudderStack should sync the data to PostScript.
3. Choose the **Event Type** — RudderStack supports sending data to PostScript as **Identify** or **Track** events.
4. In **Choose identifier**, specify the **User ID** and **Anonymous ID** from the dropdown. RudderStack uses these identifiers to identify your records.

You will see the snippet of your data in the resulting preview — you can select and edit the columns you want to send to PostScript.

{{< image src="images/event-stream-destinations/postscript-json-mapper-preview.webp" alt="PostScript JSON mapper preview" >}}


5. Specify the [Sync Schedule Settings]({{< ref "data-pipelines/reverse-etl/developer-guides/sync-schedule-settings.md" >}}) to specify how and when RudderStack should sync the data to PostScript.
6. Specify the [Sync Observability Settings]({{< ref "data-pipelines/reverse-etl/developer-guides/sync-observability.md#sync-settings" >}}) to specify how RudderStack retains the sync logs and tables, and retries any failed records for this connection.

## FAQ

#### Why can't I add a Reverse ETL source from the destination page?

The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.

See [Reverse ETL FAQ]({{< ref "data-pipelines/reverse-etl/developer-guides/faq.md" >}}) for more information.

<br />