Connect HighLevel

Updated Oct 25, 2026 · 4 min read · Pro, Business and Agency plans

This article shows you how to send HighLevel payments, refunds and cancellations to PlayerMagick with workflow webhooks, so your sales are matched to the plays that sold them.

Available on: Pro, Business and Agency plans.

How it works

You add a Custom Webhook action to HighLevel workflows: one for payments, one for refunds and one for cancelled subscriptions. Each sends PlayerMagick a short message with the payment's details. HighLevel doesn't sign workflow webhooks, so two things protect you: the receiver address is secret (only you have it), and each message carries a webhook key PlayerMagick suggests, in a header.

Sales are matched by email: the buyer gave the same email address to one of your videos or funnels and watched in the 7 days before buying. For an exact match, add a hidden field to your order form (Step 5): when the player is on that page, PlayerMagick fills it with the play's code and the workflow sends it along.

Set up the workflows in each sub-account whose sales you want to count.

Step 1: Connect HighLevel in PlayerMagick

  1. Go to Settings → Sales platforms and click Connect a platform.
  2. Next to HighLevel, click Connect. Keep the suggested Webhook key and click Connect.
  3. The setup page shows your receiver address. Copy it now: PlayerMagick shows it only once. Keep the setup page open for the key.

Step 2: The payments workflow

  1. In HighLevel, open Automation → Workflows and create a workflow with the trigger Payment Received.
  2. Click + Add action → Send Data → Custom Webhook.
  3. Set Event to CUSTOM and Method to POST, and paste the receiver address as the URL.
  4. Add a header named X-PM-Key with the webhook key from PlayerMagick.
  5. Set Content-Type to application/json and paste this into Raw Body:
{
  "event": "sale",
  "orderId": "PAYMENT TRANSACTION ID",
  "amount": "PAYMENT AMOUNT",
  "currency": "PAYMENT CURRENCY",
  "email": "CONTACT EMAIL",
  "pm": "CONTACT FIELD pm_token",
  "product": "PRODUCT NAME"
}
  1. Replace each value in capitals with the matching field: click the tag icon and pick it (keep the quotes). Leave "pm" empty if you don't use the hidden field, and "product" if there is no product name field.
  2. Click Save Action and publish the workflow.

Recurring payments: to count them as renewals instead of new sales, create a copy of this workflow filtered to subscription payments, with "event": "renewal" and a "subscriptionId" field with the subscription's ID.

Step 3: The refunds workflow

Create the same workflow with the trigger Refund and this body:

{
  "event": "refund",
  "orderId": "TRANSACTION ID OF THE REFUNDED PAYMENT",
  "amount": "REFUNDED AMOUNT",
  "currency": "CURRENCY"
}

Without an amount, the whole payment is treated as refunded.

Step 4: The cancellations workflow (optional)

Create the same workflow with the trigger Subscription, filtered to cancelled subscriptions, and the body { "event": "cancel", "subscriptionId": "SUBSCRIPTION ID" }. Cancellations are shown in the log; they don't change your sales.

Step 5: The hidden field for exact matching (optional)

  1. Create a custom contact field named pm_token.
  2. Add it to your order form as a hidden field.
  3. Put the PlayerMagick video (or funnel) on the same page as the order form. When the viewer plays the video, or a funnel shows its offer, PlayerMagick fills the field with that play's code.
  4. Keep "pm" in the payments workflow set to the contact field pm_token.

Step 6: Check it works

  • Click Send a test sale on the setup page. The result says what a real sale would be matched to. Test sales never count.
  • In HighLevel, run Test Workflow with a test contact. The message appears under Recent notifications. A test run often has empty payment fields: it is then shown as "orderId missing" and ignored, which is expected.
  • HighLevel's Execution Logs show the answer PlayerMagick gave (200 means received).

Use the plain Webhook action instead

If your account doesn't offer Custom Webhook, use the Webhook action: paste the receiver address as the URL and add the same fields as Custom Data items (event, orderId, amount, currency, email, pm), plus pm_key with the webhook key. PlayerMagick reads them the same way.

Troubleshooting

  • Refused: the signature didn't match the saved secret. The X-PM-Key header (or pm_key) differs from the key in PlayerMagick. Copy it again; there are no spaces.
  • Ignored: sale: orderId missing. The workflow ran without a transaction ID (a test run, or the field wasn't picked with the tag icon).
  • Ignored: event … The "event" value isn't one of sale, renewal, refund, cancel.
  • Order not found (it may arrive later). A refund names a transaction PlayerMagick hasn't received. Use the same field for orderId in both workflows.

Was this article helpful?