Webhook

Use ORQO's built-in Webhook app to integrate with any HTTP-capable system. The Webhook app uses the DirectAdapter (no external adapter container) and supports both sending and receiving HTTP requests.

Category	Integration
Capabilities	Send + Receive
Adapter	DirectAdapter (built-in, no adapter URL needed)
Auth method	None required (optional signature verification)

Prerequisites

• An external system that can send or receive HTTP requests
• Access to the ORQO Settings area

Setup

1. Install the Webhook App in ORQO

1. Navigate to Settings → Integrations in ORQO.
2. Find the Webhook tile and click Install.
3. The app is created with the DirectAdapter — no adapter URL is needed.

2. Configure Inbound Webhooks (Receive)

Open the Webhook card in Settings → Integrations and copy the Webhook URL field. It looks like:

POST https://orqo.ooopps.com/api/v1/webhooks/<your-webhook-token>

The trailing string is a unique per-install token, not an app ID — copy the whole URL straight from the card.

Configure your external system to send HTTP POST requests to this URL with a JSON payload:

{
  "workflow_id": 15,
  "task": "Process the incoming event",
  "metadata": {
    "source": "external-system",
    "event_type": "new_order"
  }
}

3. Secure the Webhook (Optional)

For production use, add signature verification:

1. Add a signing secret credential to the app.
2. Configure the signature header and algorithm.
3. Sign outbound requests from your external system with HMAC:

PAYLOAD='{"workflow_id": 15, "task": "Process this"}'
SIGNATURE=$(echo -n "$PAYLOAD" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -X POST https://orqo.ooopps.com/api/v1/webhooks/<your-webhook-token> \
  -H "Content-Type: application/json" \
  -H "X-Signature-256: sha256=$SIGNATURE" \
  -d "$PAYLOAD"

tip

Always use signature verification in production. Without it, anyone who discovers your webhook URL can trigger workflow runs.

4. Verify the Connection

Click Verify on the Webhook app card in ORQO. Send a test request to the webhook URL and confirm ORQO receives it.

Available Tools

The Webhook app exposes a general-purpose HTTP tool:

Tool	Description
http_request	Make an HTTP request to any URL (GET, POST, PUT, DELETE)

This tool can be assigned to agents via Skills, allowing them to call external APIs as part of workflow execution.

Platform-Specific Behavior

• DirectAdapter — Unlike other integrations, the Webhook app does not use an external adapter container. ORQO handles inbound and outbound HTTP directly.
• Flexible payloads — Inbound webhooks accept any JSON payload. The payload is passed to the workflow or Chief of Staff as-is.
• No contact requirement for API triggers — When using webhooks purely for API triggering (not messaging), the Contact restriction does not apply. See Use the API for details.
• Workflow triggering — Inbound webhooks can specify a workflow_id to trigger a specific workflow, or omit it to route through Chief of Staff.

What's Next

• Apps & Channels for the full architecture
• Configure Webhooks for detailed webhook setup
• Use the API to trigger workflows programmatically