From 5ca7c08bd567828bcb1e2404a2887fd7936199f7 Mon Sep 17 00:00:00 2001 From: Caio Pizzol Date: Thu, 28 May 2026 14:58:08 -0300 Subject: [PATCH 1/2] docs(paddle): narrow sample link scope to proxy-only The sample added in amp-labs/samples is proxy-only. Both link sites in the guide now make that scope explicit so the page does not imply a full read/write/proxy example exists. Pairs with amp-labs/samples PR adding paddle/amp.yaml. --- src/provider-guides/paddle.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/provider-guides/paddle.mdx b/src/provider-guides/paddle.mdx index 2acf6646..35199cba 100644 --- a/src/provider-guides/paddle.mdx +++ b/src/provider-guides/paddle.mdx @@ -48,7 +48,7 @@ The Paddle connector supports writing to the following objects: ### Example integration -For an example manifest file of an Paddle integration, visit our [samples repo on Github](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). +For a minimal Proxy Actions example manifest, visit our [samples repo on GitHub](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). This sample is proxy-only; Read and Write Action declarations are intentionally omitted. ## Creating an API key @@ -60,7 +60,7 @@ For an example manifest file of an Paddle integration, visit our [samples repo o This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Paddle: -- Create a manifest file using the [example](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). +- Create a manifest file using the [proxy-only example](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). To add Read or Write Actions, see the [manifest reference](/manifest-reference). - Deploy it using the [amp CLI](/cli/overview). - If you are using Read Actions, create a [destination](/destinations). - Embed the [InstallIntegration](/embeddable-ui-components#install-integration) UI component. From 9a39cd57600a52ec77c268fde6bb92c1d8cda7c7 Mon Sep 17 00:00:00 2001 From: Caio Pizzol Date: Sat, 30 May 2026 10:28:22 -0300 Subject: [PATCH 2/2] docs(paddle): describe sample as read-write-proxy --- src/provider-guides/paddle.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/provider-guides/paddle.mdx b/src/provider-guides/paddle.mdx index 35199cba..b1cf0ab0 100644 --- a/src/provider-guides/paddle.mdx +++ b/src/provider-guides/paddle.mdx @@ -48,7 +48,7 @@ The Paddle connector supports writing to the following objects: ### Example integration -For a minimal Proxy Actions example manifest, visit our [samples repo on GitHub](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). This sample is proxy-only; Read and Write Action declarations are intentionally omitted. +For an example manifest with Read Actions, Write Actions, and Proxy Actions, visit our [samples repo on GitHub](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). ## Creating an API key @@ -60,7 +60,7 @@ For a minimal Proxy Actions example manifest, visit our [samples repo on GitHub] This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Paddle: -- Create a manifest file using the [proxy-only example](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). To add Read or Write Actions, see the [manifest reference](/manifest-reference). +- Create a manifest file using the [example](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). Add or remove objects based on the Paddle data you want to sync or write. - Deploy it using the [amp CLI](/cli/overview). - If you are using Read Actions, create a [destination](/destinations). - Embed the [InstallIntegration](/embeddable-ui-components#install-integration) UI component.