Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
AWRA OpsHub + Inbound Webhooks
Receive events from any external system.
What the Inbound Webhooks connector does
Give external systems a secure endpoint to push data into AWRA OpsHub. Each key is token-authenticated with HMAC signing and replay protection, and can create notifications or trigger workflows.
Every key is authenticated with a bearer token and an HMAC signature, with replay protection, so only legitimate senders ever get through. Incoming events can raise an in-app notification or kick off a workflow — turning AWRA into the hub that other systems push into.
At a glance
- Category
- Developer & Data
- Status
- Live
- Setup
- Paste your credentials
- Data flow
- Two-way
- Scope
- Per-organization
What you can do
Secure endpoint
Token auth, HMAC signatures and replay protection.
Trigger workflows
Inbound events can kick off automations.
Full logging
Every request is recorded for observability.
How it works
Generate an inbound key with its token and signing secret.
Point your external system at the endpoint.
Map events to notifications or workflow triggers.
Fully self-serve — no platform setup
You bring your own credentials — nothing to configure on the platform. They're encrypted at rest, scoped to your organization, and removable at any time.
Built for security & scale
Every connector rides the same hardened delivery layer that powers payments and accounting sync.
Connect Inbound Webhooks to your whole operation
Set it up in minutes — securely, scoped to your organization, and yours to switch off any time.