Skip to main content
Workexe

Webhook Integrations

Send Workexe events to Slack, Jira, Zapier, Make, n8n or your own endpoint. Verify deliveries with HMAC signatures, replay failed payloads, and scope webhooks per project.

September 3, 20252 min read

Outgoing vs incoming webhooks

Outgoing webhooks push Workexe events to your stack when something changes (rank drop, audit finished, report exported). Incoming webhooks let external tools trigger Workexe actions (create task, start crawl) via a signed POST.

  • Outgoing: Workexe → your URL (most common)
  • Incoming: your tool → Workexe API (automation platforms)
  • Both support JSON payloads with schema version v1
  • Per-project endpoints so client data never crosses projects

Supported event types

Subscribe to all events or pick a subset. Payloads include project ID, event name, timestamp (ISO 8601), and a normalized data object.

  • keyword.position_changed
  • backlink.new_or_lost
  • site_audit.crawl_completed
  • report.export_ready
  • task.created
  • workflow.run_failed
  • integration.connected

Setup in 3 steps

Available on Pro and Agency plans. No code required for native connectors; raw URL for custom stacks.

  • Settings → Integrations → Webhooks → Add endpoint
  • Paste URL, pick events, copy signing secret
  • Send test event, confirm 2xx response in delivery log
  • Enable live delivery once test passes

Security and verification

Every delivery includes X-Workexe-Signature (HMAC-SHA256 of raw body + timestamp). Reject requests older than 5 minutes to prevent replay attacks.

  • Rotate signing secret without downtime (overlap window 24h)
  • Optional IP allowlist on Enterprise
  • TLS 1.2+ required on destination URLs
  • Secrets never returned after creation, store in your vault

Retries, logs and debugging

Failed deliveries retry automatically. Full request/response bodies are stored for 90 days.

  • 3 retries: 1 min, 5 min, 30 min backoff
  • Delivery log: status, latency, response code, payload hash
  • Manual replay from log row (one click)
  • Alert email when endpoint fails 10 times in 1 hour

Native connectors

Prefer a UI over raw URLs? Use built-in connectors that wrap the same webhook engine.

  • Slack: channel picker, rich blocks for rank alerts
  • Jira: auto-create issues with labels and assignee
  • Zapier / Make / n8n: official Workexe app triggers
  • Google Sheets: append row on export or rank change
webhook integrations setup
  1. 1
    Open Project

    Launch the webhook integrations module from your project panel.

  2. 2
    Connect Sources

    Add GSC, GA4 and any required CSV imports.

  3. 3
    Set Scope

    Choose location, language, device and alert thresholds.

  4. 4
    Validate

    Confirm the first scan against a known page or query.

Frequently Asked Questions