Connect Hubla to Nevian

Time needed: about 10 minutesLast updated:

Connect Hubla so sales and payment changes reach Nevian and can be matched to the visit that brought the buyer.

What you need

  • A Hubla account with permission to configure notifications.
  • An active Nevian plan and an owner, admin or member role. Viewers cannot connect integrations.
  • Keep the checkout and Nevian tabs open side by side.

Steps

  1. In Nevian, open Integrations → Add integration (Connect provider in an empty workspace), choose Hubla and click Next with the platform open in another tab.

    Drawing: Connect Hubla. 1 · Open platform: Have your account open in another tab; 2 · Copy the URL: Next creates your private connection URL

  2. Copy the complete Webhook URL. Keep it private and leave this window open while you configure Hubla.

    Drawing: Connect Hubla. Webhook URL: https://track.example.com/wh/hubla/••••••••; Hubla webhook token: Required account fields are saved with Next

  3. In Hubla, open Integrações → Webhooks → Ativar Integração. Under Configurações, choose Adicionar regra.

    Drawing: Hubla · webhook configuration. Integrações: Webhooks; Configurações: Adicionar regra; URL: Paste the Nevian URL

  4. Name the rule, paste the URL, select Todos for products and the invoice and subscription events. Use the delivery mode that sends one notification per sale, then choose Criar regra.

    Drawing: Hubla · delivery settings. Destination: Your private Nevian Webhook URL; Scope: The products and events described in this step

  5. Return to Nevian, if you use the optional token, enter Hubla webhook token and click Next to save it before sending an event. Use the same value configured for this webhook; for a token you generate yourself, use that exact value in both places. Leave an optional token empty in both places if you do not use it.

    Drawing: Connect Hubla. Hubla webhook token: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Open the rule’s actions and use Enviar eventos. Hubla test events are recorded as tests; Histórico shows whether delivery reached the receiver. Back in Nevian, look for Connected, then click Done.

    Drawing: Connect Hubla. Connection: Connected; Last event: Received just now

The optional Hubla webhook token comes from Hubla’s Autenticação section and is sent in x-hubla-token. Save the same value in Nevian before testing.

Check that it works

  • Open Logs → Webhooks and confirm the provider, order ID, event and result. A delivered webhook can be logged without creating a sale when the event is informational.
  • Use the script on the page linking to pay.hub.la; it adds sck. Hubla invoice events identify the sale, and subscription events update its lifecycle.

Problems

Waiting for the first event…

Check the complete URL, event subscriptions and product scope. If you rotated the integration key, replace the URL in the provider too.

The call was rejected

Read the reason in Logs → Webhooks. Check the secret when one is configured, then resend the original event after fixing the configuration.

No matching click

Check the click ID instructions above on a real ad visit. A provider test usually has no ad click; that alone does not mean delivery failed.

Still stuck? Write to [email protected].

Images are our own drawings and configuration diagrams, not screenshots. Use the current values from your account; the examples contain no live credentials.