Connect commercial property operations to the tools your team already uses.

TenantPoint's Zapier integration is currently private and available only to invited workspaces. It is not listed in the Zapier App Directory. This page describes the integration and its planned public submission; it does not announce public availability.

When the App Directory version is approved, TenantPoint will update this page with the public connection instructions. Existing private connections will not be migrated or changed as part of that preparation.

The integration can trigger when a vendor is created or updated, a work order is created or updated, or a work order note is created. Each trigger carries a compact immutable event snapshot. If a workflow needs the latest record, add a Find step using the TenantPoint ID from the event.

The current package provides Create Vendor, Update Vendor, Create Work Order, Update Work Order, Add Work Order Note, Find Vendor, Find Property, and Find Work Order. TenantPoint will keep the initial public set focused on workflows with a clear operational outcome rather than expose actions just to increase the count.

An Owner or Admin creates a dedicated TenantPoint API key from Settings → Developers → API keys. Give it only the scopes the Zap needs. For the full currently implemented set, the least combined scope set is properties:read, vendors:write, work_orders:write, and webhooks:write; a write scope includes read access only for that same resource.

Start in the isolated TenantPoint test sandbox with synthetic records and a tp_test_ key. A test key cannot access live data, and a tp_live_ key cannot access the test sandbox. Use a separate live key only after the workflow is ready, and revoke that dedicated key when the connection is retired or suspected to be exposed.

• Do not paste an API key into an action field, spreadsheet, ticket, or message.
• Use the connection test to confirm the intended workspace and environment before turning a Zap on.
• Retain the safe request ID from an error when contacting support; never send the key or webhook URL.

TenantPoint creates one integration-owned subscription for each selected trigger. Unsubscribing disables that subscription with the same connection key. Human-managed webhooks stay separate from Zapier subscriptions and cannot manage or reveal their receiver URLs.

Zapier trigger deliveries are verified with ES256/P-256 against a public-key ring. TenantPoint keeps the private signing key; no private JWK, HMAC secret, or shared webhook secret is placed in the Zapier package. The verifier binds the exact raw body, timestamp, event ID, subscription ID, signing-key ID, and environment, and rejects events outside the replay window.