Anow

Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.

Planned workflows

Planned for Anow:

You text	What would happen in Anow
“Inspection done at 44 Elm”	Updates the order status

These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.

Before you start

Anow publishes guides for named integrations such as QuickBooks, MercuryNOW, TotalNOW and ACI export. Those features do not by themselves establish a general-purpose third-party write API. Anow integrations and add-ons.

Developer setup — vendor approval first

1. Ask Anow whether a custom integration can read orders, add inspection notes/photos and update assignments or statuses for the intended customer account.
2. Request partner requirements, API entitlement, current authentication documentation, endpoint reference, test access and rate limits.
3. Confirm what each write does: an internal note, client-visible update and final report delivery must be distinguished.
4. Build against the approved route and document credential rotation and customer revocation. Do not infer API access from a built-in export feature.

Customer setup — after access is confirmed

1. Identify the appraisal firm’s Anow account and an owner/admin authorized to approve the integration.
2. Have that administrator request the specific integration entitlement from Anow.
3. Follow the vendor’s account-authorization or dedicated-credential procedure. Store any secret in the secure setup flow, not a text message.
4. Record the firm/account ID, permitted team members and allowed order/status operations.
5. Select a test order with the vendor and operator. Confirm notification settings and which changes become visible to clients.

Verify write access

Read the designated order, add an agreed internal test note through an approved endpoint and verify the result in Anow. Test status updates separately, checking attribution and client notifications. Repeat a request to confirm the connector does not duplicate notes or tasks.

Disconnect and unresolved details

Have the admin revoke the vendor-issued grant or credentials, then stop queued work and remove local secrets. Require a failed follow-up access check before declaring it disconnected. Publicly confirmed self-service API-key menus, scopes and general order-write endpoints were not available in this review; those details must come from Anow before customer connection instructions can become executable.

Who completes the work?

An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.

Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.