Connect your quote workflow. Let QuoteNag handle the follow-up.

1. 1
   Create an API key

   Open Integrations > API Keys. Give the key a clear label and copy it when it appears. The full key is shown once.

2. 2
   Test the connection

   Send an authenticated request to GET /api/v1/account. A valid connection returns safe account details and API version v1.

3. 3
   Create a campaign

   Send the client and quote details to POST /api/v1/campaigns. Include external_reference so workflow retries do not create duplicates.

4. 4
   Receive QuoteNag events

   Add your automation tool's HTTPS URL under Integrations > Webhooks. Filter incoming events by the exact event names documented below.

Authorization: Bearer qn_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Test Your Connection

Use this endpoint before creating campaigns. It confirms the key, account, subscription access, and API version without returning campaign or billing data.

GET https://quotenag.gottools.co/api/v1/accountAuthorization: Bearer qn_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Accept: application/json

HTTP 200 response

{
  "data": {
    "id": 123,
    "name": "Lyte Painting",
    "api_version": "v1"
  }
}

Existing events followup.failed and integration.test also remain available. They are not part of the four Pabbly trigger mappings above.

Stable event envelope

{
  "id": "evt_11111111111111111111111111111111",
  "event": "campaign.created",
  "sent_at": "2026-07-10T19:00:00+00:00",
  "occurred_at": "2026-07-10T19:00:00+00:00",
  "api_version": "v1",
  "data": {}
}

The event ID stays the same across retry attempts for one logical event. Receivers should ignore unknown additive fields so future compatible additions do not break the workflow.

Webhook signing

QuoteNag signs the exact raw request body with the endpoint's signing secret. The signature is a lowercase hexadecimal HMAC-SHA256 digest with the sha256= prefix.

X-QuoteNag-Event: campaign.created
X-QuoteNag-Event-ID: evt_11111111111111111111111111111111
X-QuoteNag-API-Version: v1
X-QuoteNag-Signature: sha256=<hex HMAC digest>

Verify the signature against the raw body before parsing or acting on the payload.

Delivery and retries

• Any HTTP 2xx response counts as successful delivery.
• Transport errors, HTTP 408, 425, 429, and 5xx responses receive up to three synchronous attempts.
• Other HTTP 4xx responses are not retried.
• Each attempt has a 10-second timeout and redirects are not followed.
• Delivery requires PHP cURL and is pinned to a validated public destination IP to reduce server-side request forgery risk.
• QuoteNag does not currently provide a delayed replay queue or dead-letter screen.

Webhook Event Payloads

These sanitized examples are loaded from the same checked fixtures used to verify QuoteNag's production serializers.

{"error":"Example unavailable"}

{"error":"Example unavailable"}

{"error":"Example unavailable"}

{"error":"Example unavailable"}

Receive QuoteNag events in Pabbly

1. Create a workflow in Pabbly Connect.
2. Choose the appropriate Webhook by Pabbly trigger and copy its generated HTTPS webhook URL.
3. In QuoteNag, open Integrations > Webhooks, create an endpoint, and paste the Pabbly URL.
4. Use Send test to confirm connectivity. This sends integration.test.
5. To capture the fields for a real trigger, perform the matching action in a test campaign: create a campaign, accept or decline it, or let a scheduled follow-up send.
6. In Pabbly, capture the request and filter it using the mapping below.

Create QuoteNag campaigns from Pabbly

1. Create a QuoteNag API key and store it in Pabbly's protected authentication or header field.
2. Add an HTTP/API request action in Pabbly.
3. Set the method to POST and the URL to https://quotenag.gottools.co/api/v1/campaigns.
4. Add Authorization: Bearer YOUR_QUOTENAG_API_KEY and Content-Type: application/json.
5. Map the four required fields and a stable external_reference from the source quote or estimate.
6. Test the request, then confirm the campaign appears in QuoteNag.

{
  "client_name": "Jamie Rivera",
  "client_email": "jamie@example.com",
  "quote_title": "Roof repair quote",
  "quote_summary": "Repair damaged shingles and flashing.",
  "external_reference": "estimate-1042"
}

{
  "error": "Client email is invalid.",
  "code": "validation_error",
  "field": "client_email",
  "reason": "invalid_email"
}

• Keep API keys private

  Store them in protected credential fields. Never add them to URLs, screenshots, source control, normal logs, or support messages.

• Revoke compromised keys

  Revoke the affected key under Integrations > API Keys. Revocation takes effect on the next request.

• Verify webhook signatures

  Generate HMAC-SHA256 from the exact raw request body and compare it with X-QuoteNag-Signature.

• Use HTTPS

  Use HTTPS for API calls and all new webhook endpoints. QuoteNag keeps HTTP webhook support only for backward compatibility with existing consumers.

• Expect account isolation

  API keys, campaign lookups, duplicate checks, and webhook endpoints stay inside the owning QuoteNag account.