Skip to main content
While the Organization Brain handles internal knowledge and Corgtex’s UI handles interactions, you often need the rest of your company’s software ecosystem to respond when decisions happen. Corgtex uses a robust event-driven architecture, publishing domain events whenever key mutations occur (e.g., a proposal is approved, a spend request is filed, an article is published). You can subscribe to these events using Outbound Webhooks.

​
Configuring an Endpoint

To set up a webhook:
  1. Navigate to your Workspace Settings → Developers → Webhooks.
  2. Click Add Endpoint.
  3. Provide an HTTPS endpoint URL (e.g., https://api.yourcompany.com/webhooks/corgtex).
  4. Select the specific events you want to subscribe to.
  5. Save the configuration. Corgtex will provide a Signing Secret that you must securely store on your receiving server.

​
Example Event Payload

When an event triggers, Corgtex sends a POST request with a standardized JSON payload: 
{
  "id": "evt_123456789",
  "type": "proposal.approved",
  "timestamp": "2024-03-21T10:00:00Z",
  "workspaceId": "ws_abc123",
  "data": {
    "proposalId": "prop_987654",
    "title": "Allocate $10k to Marketing for Q2 Ads",
    "approvedBy": "usr_789"
  }
}

​
Security: Verifying Signatures

Corgtex signs every webhook payload. You are strongly encouraged to verify the signature on your receiving server to ensure the payload was genuinely sent by Corgtex and has not been tampered with. The signature is sent in the x-corgtex-signature HTTP header. It is generated by computing an HMAC with the SHA-256 hash function, using your endpoint’s Signing Secret as the key and the raw request body as the message.

​
Webhook Deliveries and Event Replay

Corgtex does not just fire-and-forget. The platform records the success or failure of each delivery attempt. If your receiving server goes down and returns a 500 error, you can navigate to the Webhooks dashboard, view the failed WebhookDelivery log, and click Replay to manually resend the event once your server is healthy again. This guarantees that you never permanently drop a critical business event like an approved spend request.