AWRA Help Center

Open Settings → Integration Sync Hub. It is also in the API and the AWRA mobile app. Viewing it needs the view integration manager permission.

Connector Health

Four connectors are tracked: QuickBooks Online, outbound webhooks, payment providers and the Developer API. Each shows healthy, warning or failing, with its failures, retries, dead letters, mapping errors and last success, and the owner and runbook note you assign, so a failure at night reaches someone who knows what to do.

Replays Need A Second Person

1. Someone asks for a failed event to be replayed and says why.
2. A different person approves it. The person who asked cannot approve their own replay.
3. On approval it runs at once. A QuickBooks event is checked for mapping first; a webhook is resent with the same delivery id, so a receiver that has already seen it can recognise it as a repeat and not act twice.
4. Rejecting puts the event back to failed.

Asking for, approving and rejecting replays, and assigning owners, need the manage integrations permission, available on the Premium and Enterprise plans.

Before A Sync Goes Wrong

The hub shows data problems that will make a sync fail before it runs: a missing tax code, an unmapped account, a duplicate item name, a currency the other system does not support, or an expired connection token. An object map shows which of your records are linked to QuickBooks, and a reconciliation section compares the two sides.

API Keys And Usage

• Key rotation reminders go out weekly to the people who manage API keys, for keys expiring within 14 days or not rotated in 180 days.
• Usage flags on the hub mark a key whose calls in a day jump to five times its weekly average, a key with 30% or more of its calls refused, throttled calls, and calls still arriving on a revoked key.

Webhook Sandbox

From the hub, open the sandbox for one of your outbound webhooks. It sends nothing. It shows you:

• A sample payload for the event you pick, with its headers, signed exactly as a real delivery is: X-Awra-Signature: sha256=…, an HMAC-SHA256 over the timestamp and body with the webhook’s secret.
• A validate form: paste the body and headers your receiver got and AWRA checks the signature, that the timestamp is within five minutes, and the delivery id, and tells you whether your receiver is protected against a replayed message.

To send a real test delivery to your URL, use the separate Test action on the webhook. The sandbox needs the manage workflow connectors permission. See Developer API for the event list.

For The Mobile App

• An app older than the supported minimum is told to update, instead of failing in odd ways.
• Under Offline Operations, you can set an offline policy for your workspace: how many actions a phone may queue, how old a queued action may be, which kinds of action may be queued, the GPS accuracy required, and how long before a re-sign-in after being offline. For queue size and age, the phone uses whichever limit is stricter, its own or yours.
• Scanner sessions from the last 30 days are listed and can be revoked.

See Offline Operations Center, QuickBooks Sync and Integrations.