Claim Your Free Signal

Webhooks

Send Smart Signal context to your own workflow

When Queast creates a new Smart Signal, it can send the recommendation and account context to an endpoint your team controls. Your system can use that JSON to create a research queue item or route follow-up work, saving you from copying the summary between tools.

Talk to us about webhooks See the payload

What arrives

Keep the account context with the recommendation

Automatic delivery is available for IT-services workspaces with Smart Signals and integrations enabled. Each new Smart Signal queues a signal.published event for the active webhook connection.

How Smart Signals relate to your offering
  • The recommendation Signal ID, title and summary, plus context text containing links to the Signal and company in Queast. Your receiver can keep the explanation beside its own follow-up record.
  • The company Company ID and name, with available domain, website, description, headcount, location and technology context. Use the ID or domain to connect the handoff with your existing account records.
  • People and follow-up context Up to five available company contacts, drawn from the Signal’s recommendations or other people at the company. Names, roles and available email and phone fields accompany suggested follow-up text. Your receiver decides which fields to retain and how to use them.

Setup

Connect an endpoint your team controls

A workspace administrator opens Settings → Integrations → Webhooks, then chooses Configure on Generic Webhook. If integrations are disabled, contact Queast about enabling them for your workspace.

  1. Prepare the receiver

    Set up the endpoint and the workflow that will handle its incoming JSON. Queast supplies the payload; your system creates any downstream records or tasks.

  2. Enter the connection details

    Add the webhook URL and, if your receiver will verify signatures, a signing secret. The saved secret is not displayed again.

  3. Save and activate delivery

    Saving a new connection activates automatic delivery of newly created Smart Signals. The connection menu lets your administrator inspect its status, edit settings or disable future delivery.

For your implementation team

Build the receiver around this request

Queast sends an HTTP POST with an application/json body. These details let your team authenticate configured signatures, recognize repeat deliveries and accept the handoff.

Explore all integrations
  • Identify the event The envelope contains event_type, schema_version, event_id, tenant_id, occurred_at, produced_at, idempotency_key and event data. The Smart Signal event uses signal.published and schema version v1.
  • Verify optional signing When a signing secret is configured, X-Queast-Timestamp carries Unix seconds and X-Queast-Signature carries v1= followed by the hexadecimal HMAC-SHA256 digest. Verify it using the secret and the timestamp, a period, then the raw request body. Apply your receiver’s timestamp acceptance window.
  • Accept and deduplicate Use the Idempotency-Key header to recognize a repeated delivery before creating duplicate work. Return a 2xx response when your receiver has accepted the request.
  • Handle delivery failures Transport failures and HTTP 408, 429 or 5xx responses can be retried. Other 4xx responses stop delivery attempts; eligible failures also stop once retries are exhausted.

Start with the recommendation

Evaluate a Smart Signal for your sales approach

Tell us about your offering and target customers through the request form. We’ll assess whether a Smart Signal is available for your business, so you can evaluate the recommendation before planning its handoff.

Get a free signal