Power Automate
There is no dedicated HousingSurvey Pro connector in the Power Automate gallery — instead, the same OpenAPI specification that documents the REST API imports directly as a custom connector.
What it is
The REST API’s OpenAPI 3.0 specification is written to double as a Power Automate custom connector definition. Importing it gives Power Automate the same five resources — surveys, properties, tenancies, contractors and work-orders — that any other REST API caller gets, using the same bearer-key authentication and the same scopes. Nothing about this is a separate integration surface with its own behaviour; it’s the REST API, wrapped for a low-code tool.
Before you start
This needs a REST API key with the scopes your flow will use (see API keys and scopes), and the Platform plan.
How to do it
- Mint an API key with the scopes your flow needs.
- In Power Automate, create a new custom connector and choose Import an OpenAPI file, using the specification served at
/api/openapi.yaml. - Some Power Automate tenants require OpenAPI 2.0 rather than 3.0 on import — if yours does, convert the file with any OpenAPI 3-to-2 converter before importing.
- Configure the connector’s authentication as a bearer token, and supply your API key when you use the connector in a flow.
- Build your flow against the same endpoints documented at
/developers/and/api/docs/— there is nothing Power-Automate-specific to learn beyond the import step itself.
How it integrates
Because this is the REST API underneath, every behaviour documented in The REST API applies unchanged: the same rate budget, the same pagination via cursor/nextCursor, the same lineageId/versionNo/supersedes fields on a revised report, and the same audit-log entry for every call, whether it came from a flow or a hand-written script.
Common problems
- Power Automate rejects the import. Your tenant may require OpenAPI 2.0 — convert the specification before importing rather than editing it by hand.
- A flow step fails with an authentication error. Confirm the connector’s bearer token is set to a current, unrevoked API key.
- A flow step fails with “missing scope”. The key used doesn’t carry the scope that endpoint needs — mint a new key with the right scopes.