Workflow WebhooksWorkflow Webhooks

How to connect Paddle to Shopify Flow

Paddle is a merchant of record for digital products and subscriptions. It notifies you about transactions, subscriptions, refunds and customer changes. Workflow Webhooks turns that call into a Shopify Flow trigger, so your store can react to it: tag a customer, add an order note, send an internal email, update a metafield - anything Shopify Flow can do.

This guide sets up the whole path - Paddle sends, Workflow Webhooks receives and verifies, Shopify Flow acts - with Paddle's HMAC signature checked on every request, so nothing but Paddle can start your workflow.

What you can build

  • Tag a Shopify customer who also holds a Paddle subscription, so they see the right pricing or content.
  • Email your team when a subscription is cancelled and the customer has recent Shopify orders.
  • Write the current plan onto the customer record as a metafield.

Typical events to send: transaction.completed, subscription.canceled, adjustment.created (refund), customer.updated.

Before you begin

  • Workflow Webhooks installed on your Shopify store.
  • Shopify Flow installed, which is free from the Shopify App Store.
  • An account on Paddle with permission to create webhooks.

Step 1 - Create the webhook in Workflow Webhooks

  1. Open Workflow Webhooks -> Webhooks -> Create webhook and give it a name you will recognise in Flow, such as Paddle events.
  2. Under Authentication, choose HMAC.
  3. Under Signature provider, pick Paddle. The app fills in the header, algorithm, signed payload and replay window for you - there is nothing else to configure.
  4. Leave the secret empty for now and Save. Copy the webhook URL shown on the page.

See Authentication for the other authentication modes, and Payload mapping and Flow variables for choosing which fields reach Flow.

Step 2 - Add the endpoint in Paddle

In Paddle, open Developer tools -> Notifications, add a destination with the URL you copied, and pick the events. The secret key is shown on the destination.

How to find your Paddle signing secret

The secret key of the notification destination (Paddle -> Developer tools -> Notifications).

Paddle's own documentation on webhook signatures has the exact wording and screenshots for your account.

Paste that secret into the webhook's Secret field in Workflow Webhooks and save. From that moment every Paddle delivery is verified before it reaches Flow.

What this checks

What Value
Signature header Paddle-Signature
Where the signature sits In the h1 value of that header, which carries key=value pairs separated by semicolons
What is signed {timestamp}:{body}
Signature HMAC-SHA256, hex encoded
Timestamp The ts value of the signature header, as Unix seconds
Replay protection Requests whose signed timestamp is more than 5 minutes away from now are rejected
The secret Used as plain text. Paste it exactly as the sender shows it

In the signed payload, {body} is the raw request body, byte for byte, and {timestamp} is the timestamp above.

A request that fails any of these is rejected with 401, is recorded in History and troubleshooting, and never starts a workflow.

Step 3 - Build the Shopify Flow workflow

  1. In Shopify Flow, create a workflow and choose the Workflow Webhooks trigger.
  2. Press Record events, then send a test event from Paddle (or use Send test in Workflow Webhooks) so Flow learns the shape of your data.
  3. Every webhook you own fires the same Flow trigger, so add a first condition on the webhook id to keep this workflow to Paddle only. The id is shown on the webhook page.
  4. Add your actions - tag a customer, add a note, send an internal email, update a metafield.

Step 4 - Test it end to end

Trigger a real event in Paddle. In Workflow Webhooks -> History you should see the invocation with status Success. If the signature was wrong you get a failed entry with the reason instead, and Verifying signed webhooks explains the signature tester that shows you exactly which step failed.

The signature does not match▾

In this order: the secret (the most common cause - an extra space, or a key from the wrong environment), whether the sender is using a different endpoint's secret, and whether anything between Paddle and the app rewrites the body. Signatures cover the raw bytes, so a proxy that re-formats JSON breaks them. The signature tester on the webhook page shows the exact text that was signed.

I get 401 on every request▾

Check that the webhook's authentication is set to HMAC with the Paddle provider selected, that the secret is filled in, and that Paddle is posting to the URL exactly as the app shows it, including the code at the end.

Nothing appears in History▾

The request never arrived. Re-check the URL in Paddle, and look at Paddle's own delivery log for the response it got. A 404 means a wrong or deleted webhook, a 429 means you are over your plan's invocation limit - see Plans and usage.

The workflow runs for the wrong events▾

Every webhook in your store fires the same Flow trigger. Add a condition on the webhook id as the first step of the workflow, or narrow the events you send from Paddle.

Requests fail with "timestamp outside tolerance"▾

Paddle signs a timestamp and the app rejects anything more than 5 minutes old. This is normally a clock problem on the sending side, or a delivery that Paddle retried much later with the original timestamp. Retries from the same original request cannot pass; ask Paddle to send a fresh event.