AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

  • REST API guide
  • Authentication
  • API reference
  • MCP (AI agents)
  • SDKs
  • Quick actions

Webhooks

  • Overview
  • Quickstart
  • Events
  • Payloads and headers
  • Security and signing
  • Delivery and retries
  • Managing via API

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference

Webhooks

Quickstart

Create a subscription, receive your first event, verify its signature, and go live. This path takes you from zero to a trusted, real-time webhook.

  1. 1

    Create a subscription

    Create a subscription in the Atlas dashboard under Settings, then Webhooks, or call the API directly. Both take the same two required fields: url (a public HTTPS endpoint, max 2048 characters) and events (1 to 50 event patterns to subscribe to).

    curl -X POST https://api.example.com/v1/webhooks \
      -H "Authorization: Bearer atlas_pat_REPLACE_ME" \
      -H "Content-Type: application/json" \
      -d '{"url":"https://example.com/atlas/webhook","events":["task.completed","project.*"]}'

    The response returns { webhook, secret }. The webhook object holds the subscription details; secret is the signing key you use to verify every future payload.

    Copy your signing secret now

    The signing secret is shown only once, at creation. It cannot be retrieved later. If you lose it, you must rotate the webhook to generate a new one.
  2. 2

    Receive the event

    Stand up an endpoint that returns a 2xx response quickly. Atlas times out a delivery after 10 seconds, so acknowledge fast and push any heavy work onto an asynchronous queue rather than doing it inline.

    javascript
    app.post(
      "/atlas/webhook",
      express.raw({ type: "application/json" }),
      (req, res) => {
        // verify first (see Security), then enqueue and respond fast
        res.status(200).send("ok");
      },
    );
  3. 3

    Verify every payload

    You MUST verify the signature before trusting a payload. Recompute an HMAC-SHA256 over `${timestamp}.${webhookId}.${body}` keyed by your signing secret, then compare it against the x-atlas-webhook-signature header. See Security and signing for full verification code in five languages.

  4. 4

    Go live

    Send a test delivery from the dashboard, or call POST /v1/webhooks/{id}/test-delivery, which emits a webhook.test event. Watch it land in delivery history, confirm your endpoint verified and acknowledged it, then start relying on real events. See Delivery and retries and Events for what happens next.

Next step: secure your endpoint

Signature verification is required before you trust any payload. Continue to Security and signing for the full verification and replay-defense guide.

On this page

  • Create a subscription
  • Receive the event
  • Verify every payload
  • Go live