AWRA OpsHub Search

AWRA Help Center

Find answers, support paths, and rollout guidance fast

Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.

Product help Implementation Security reviews Billing & support
Friendly support team helping users find the right answer
3550
Articles
20
Help sections
IQ
Bot-ready

Browse Help Sections

Docs, guides, troubleshooting, billing, security, integrations, mobile, and releases

Each article is backed by approved public knowledge and links back to the authoritative AWRA resource for deeper context. Tap a section to expand it.

Show all sections

Integrations

224

APIs, webhooks, sync patterns, QuickBooks, connectors, and external system implementation.

AWRA Blog

The REST API: Tokens, Permissions and Limits

Two APIs: a published Developer API that reads your records and writes their master data, with keys you issue in Settings, and the larger API the app runs on. Which to build on, why a user token carries that user's permissions, and why continuous two-way sync is not a shape either supports.

AWRA Blog

The QuickBooks Sync: A One-Way Push

"Sync" does more work on integrations pages than any other word in software marketing. Ours pushes vendors, items, purchase orders, customers, invoices and payments received out on a button and reads nothing back — including a note on where our own connector copy used to overstate it.

AWRA Blog

The Field That Is Checked and Discarded

A sale from a till app can name the warehouse it came out of. The field is validated and then thrown away in favour of the counter’s own — which is the safe answer, and it leaves the field sitting in the one place a value that does nothing can still do something.

AWRA Blog

The Receipt the Provider Gave You

When a message is handed to a mail or messaging provider, the provider hands back an identifier — its receipt for what it just accepted. There is a place to keep that identifier and nothing puts anything in it, so our record of a message and theirs cannot be joined.

AWRA Blog

The Pause That Nothing Ends

A workflow can be built with a wait in the middle — do this, pause three days, then do that. The pause works. Everything before it runs, the run is marked paused, and the log names the date it will continue. Nothing in the product ever comes back to it.

AWRA Blog

The Name Is the Join Key

A supplier in your workspace and a supplier in QuickBooks are decided to be the same supplier by the display name, matched exactly, on every run. Everything downstream hangs off that one comparison — including what happens the day somebody renames one.

AWRA Blog

The Fallback Line Nobody Reads

Every Slack message this system sends carries its content twice — once as a formatted card, once as a plain line nobody in the channel sees. Drop the second and the phone notification that actually reaches somebody goes blank.

AWRA Blog

The Same Button for Two Kinds of Account

One Microsoft sign-in button serves a corporate directory account and a personal one, and the profile it returns is the same shape for both. Knowing which way that decision went tells you what the button can enforce.

AWRA Blog

The Second Identical Request

Two mechanisms stop a request being processed twice, and they disagree about almost everything — including whether an identical second request is a duplicate or a legitimate new one. Both are right for where they sit.

AWRA Blog

The Password That Is Different Every Time

The password on an M-Pesa request is not stored anywhere. It is built fresh for every call out of three pieces — one of which is the current time — which makes your server clock part of getting paid.

AWRA Blog

The Sender ID Is Optional Until It Is Not

Three SMS providers, one missing sender name, three behaviours: one omits the field, one substitutes a default, one refuses to send. A connector that assumed any of them would break on the other two.

AWRA Blog

The Plain-Text Part Nobody Writes

Almost nobody writes the plain-text version of a transactional email, and almost every spam filter notices. This connector builds one from the HTML — three characters of code, a measurable difference.

AWRA Blog

The Folder It Can See

Connecting Google Drive to a business system usually hands over the whole Drive. This connector asks for a scope that reaches only files it created itself — a boundary Google enforces rather than one we promise.

AWRA Blog

The ID You Look Up and the Name You Send

The schema call identifies a table's key column by an opaque identifier. The write call wants its human name. A connector missing the translation fails on every table anybody has ever tidied.

AWRA Blog

The Number That Cannot Go Backwards

A revenue authority identifies your invoice by a number you choose. Three kinds of document were each choosing from their own sequence — two documents claiming one filing, invisible from inside.

AWRA Blog

The Envelope Is the Hard Part

A Teams notification is a card inside an attachment inside a message. Get the innermost part perfect and the wrapper wrong and nothing arrives — and two of the three layers carry no content at all.

AWRA Blog

The Same Eight Keys Every Time

An automation platform learns what a payload looks like from one sample and builds every mapping against it, which makes a field that is sometimes absent worse than a field that is always empty.

AWRA Blog

The Field You Have to Create First

Before this connector writes a single record, somebody adds a custom field to your Salesforce org. Not a step we could have avoided — it is what makes every sync afterwards idempotent.

AWRA Blog

The Name on the Message Is a Field

On a Discord webhook the sender name is a value in the message body, chosen per message, with nothing checking it. Which makes the name in that channel a claim rather than a fact.

AWRA Blog

The Key Tells You Which Server

A Mailchimp API key ends with the name of the server your account lives on. The credential carries its own routing — so a key with the suffix missing is not a credential at all.

AWRA Blog

The Push Is Not the Payment

The response to a payment request is two identifiers and a suggestion to ask the customer for their PIN. Everything that matters arrives later, from a party that signs nothing.

AWRA Blog

The Role You Have to Name

Send a contract naming a role the template does not define and everything succeeds — the document is created, the email goes out, and there is nothing for the recipient to sign.

AWRA Blog

The Shape of a Value

The same email address has to be sent four different ways depending on what the destination column was declared as. Guess wrong and the whole record is refused.

Page 4 of 10 · 224 articles

Still need a human answer?

For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.