Skip to content
HelSup Help Center
Help Center/Channels & integrations
Channels & integrations

Webhooks

Notify an external system when supported ticket events occur and verify secure delivery.

2 min read · HelSup product documentation
On this page
  1. Overview
  2. When to use this
  3. Where to find the controls
  4. Who can make these changes
  5. Before you begin
  6. Follow these steps
  7. Settings reference
  8. Example workflow
  9. Good practices
  10. Important considerations
  11. If something does not work

Overview

Webhooks POST JSON about ticket events to URLs you register. Delivery is queued (system cron in production). Failures appear in integration logs and can retry. This is outbound from HelSup, not IMAP and not a customer messenger.

When to use this

ERP or logging stacks should learn about new tickets without polling REST every minute.

Where to find the controls

Settings → Integrations → Webhooks view. Logs: integration logs. Queue depth: System Status.

Who can make these changes

manage_integrations to CRUD endpoints. The receiving system uses the signing secret you set.

Before you begin

Add URL, secret, event list, and active flag. Verify TLS. Exclude secrets from backups you share. Rate and batch follow queue_batch_size.

Follow these steps

  1. Stand up an HTTPS listener.
  2. Register the webhook.
  3. Trigger a ticket event.
  4. Confirm the POST and signature.
  5. Return 2xx.
  6. On 5xx, watch retry after cron.

Settings reference

URL, secret, events, active, last status, last error, next retry. Payload includes ticket id and event name — treat PII per Privacy settings.

Example workflow

Event ticket.created POSTs to https://hooks.example.com/es. The listener writes a row in the ERP. Slack remains a separate optional connector.

Good practices

Idempotency: store event ids so retries do not double-create ERP rows. Keep listeners fast; do heavy work asynchronously.

Important considerations

HTTP listeners on HTTP (no TLS) leak ticket metadata. Do not log raw secrets. A dead cron looks like “webhooks broken”.

If something does not work

Webhook failed: non-2xx, TLS error, DNS, or queue backlog. Diagnose logs + System Status cron. Contact support if 2xx is recorded but your listener never ran — include timestamps, not the secret.

Let’s solve it together.

Can’t find what you need? Our support team can help with your next step.

Contact support ↗
LIFETIME PARTNER POLICY

One introduction.
A lifetime of shared growth.

Introduce HelSup to your customers, readers or community. Earn 30% on their first purchase and 20% on every subsequent purchase and renewal throughout their customer lifetime with HelSup.

Read our invitation to partners ↗
30%FIRST PURCHASE
20%Every subsequent
purchase & renewal

From recommendation to reward

  1. 01

    Get your personal link

    Sign in to your HelSup customer account and open Partner program to access your referral link.

  2. 02

    Recommend with confidence

    Share the link in a useful review, tutorial, customer proposal or with your community. Explain your partner relationship.

  3. 03

    Track your commission

    Follow attributed purchases and commission status in your partner dashboard. Eligible commissions are reviewed before payout.

YOUR CUSTOMER RELATIONSHIP KEEPS WORKING

A $100 first purchase earns $30.
A later $100 purchase or renewal earns $20.

Illustrative amounts, after discounts and excluding tax.

A customer relationship that lasts

30% first, 20% thereafter. Receive 30% on the customer’s first eligible paid purchase, then 20% on subsequent purchases and renewals throughout that customer’s lifetime on HelSup.

From link to lifetime attribution. The initial referral link is remembered for 30 days in the same browser. Once the referred customer’s first paid purchase is recorded, their partner relationship continues without needing another referral click.

Completed payments. Commission is calculated after discounts and before tax. Free orders and self-referrals do not qualify. Refunds reduce or reverse the associated commission.

Review and payout. Earnings appear as pending until reviewed by HelSup. Payout is processed manually after approval. Contact partner support for payment arrangements.