Troubleshooting TenantPoint in Zapier

#Start safely

Start with a tp_test_ connection and synthetic data. Do not share the API key or a full request payload with support. Contact TenantPoint support with the request ID, Zap step, environment, and a redacted description of the failure.

#Common API responses

• 401 Unauthorized: the key may be invalid, revoked, malformed, or from the wrong environment. Use the correct dedicated key; do not replace a test key with a live key as a workaround.
• 403 Forbidden: the key lacks a required permission or the workspace does not entitle the operation. An Owner or Admin should review least-privilege access rather than broadening access unnecessarily.
• 404 Not Found: the selected record may no longer exist or may not be accessible in the connected workspace. Re-select a workspace record or provide a UUID that belongs to it.
• 409 Conflict: a source operation ID may have been reused with a different payload, or a requested work-order transition is not valid. Keep the same ID and payload for a retry; use a new source event for a new operation.
• 422 Validation error: correct the named field, including required create fields and supported category values.
• 429 Too Many Requests: Zapier receives the API's Retry-After value, or a 60-second fallback when none is supplied. Wait before retrying and do not fan out duplicate Zap runs.

#Empty selectors

If a selector is empty, confirm that the selected workspace contains matching accessible records. Use its search field where available or map a UUID from a trusted previous step. A blank result never means that Zapier can see another workspace.