Skip to content
Build a Doc
Home Documentation Support
This documentation is currently in preview, therefore subject to change.

Connector FAQ

This page collects the frequently asked questions about the Build a Doc Power Automate connector. It covers connection creation, authentication, API key lifecycle, permissions, tenant/shared-flow behaviour, and support-level diagnostics.

Quick Answers

How do I create the connection?

Create a new connection when prompted in Power Automate. Give your connection a name (can be anything appropriate that you choose), paste your Build a Doc API key into the connection dialog, and save.

What permission does the connector need?

None special inside Power Automate beyond the ability to create connections and call connector actions. The API key is the credential - treat it like a password and do not publish it.

Why am I getting 401 / invalid API key?

Your API key is missing, revoked, or mistyped. Copy and paste the full API key from the portal (no extra spaces) and retry.

Why am I getting 403?

The API key is valid but the subscription or key lacks permission to perform the requested operation. Verify subscription plan/feature access in the portal.

What causes 429 (rate limit)?

Too many requests in a short window for your subscription tier. Add retries/backoff or reduce request frequency; consider upgrading your plan for higher throughput.

Connection creation / authentication

Q: How do I create the connection in Power Automate?

Answer:

  • Add any Build a Doc action in your flow (for example, Convert Word Document).
  • When prompted, click + Add new connection.
  • Give the connection a name and paste your API key from the Build a Doc portal.
  • Click Create.

Q: The connection dialog disappears / “connection failed” - what now?

Fix:

  • Reopen the connection dialog and paste the API key again (don’t type manually).
  • Ensure there are no leading/trailing spaces.
  • Try the most recently created API key from the portal.
  • If the error mentions network/CORS, check that your network/proxy allows outbound HTTPS to Build a Doc endpoints.

API keys & security

Q: How do I rotate / revoke an API key?

Answer:

  • Rotate keys from the Build a Doc portal. After rotation, update any Power Automate connections that use the old key.
  • Revoke immediately if you suspect that your API key is no longer secure.

Q: Can I store the API key in Azure Key Vault or a secrets store?

Answer:
Yes. Best practice is to store keys in a secure vault and surface them to flows via a secure service account or managed identity rather than pasting the same key into many personal connections.

Permissions, tenants, and shared flows

Q: If I share a flow, will others see my API key?

Answer:
No - Power Automate stores connection credentials centrally. However, flows that use your connection will run under your credentials. For shared execution, create and use a service-account connection that is not tied to an individual user.

Q: Does the connector work across tenants?

Answer:
Connections are user- and tenant-specific. To operate in another tenant, create a connection (API key) in that tenant or use a centrally managed service account available in that tenant.

Common connection errors & fixes

401 Unauthorised / “Invalid API key”

  • Cause: API key wrong, expired, or revoked.
  • Fix: Re-enter the API key from the portal; confirm subscription is active.

403 Forbidden

  • Cause: API key valid but subscription or key lacks permission.
  • Fix: Verify subscription features and plan; contact your org admin.

429 Too Many Requests

  • Cause: Exceeding rate limits for your subscription.
  • Fix: Implement retries/backoff, reduce request rate, or increase subscription throughput.

Network/CORS / Connection refused

  • Cause: Network or proxy blocking outbound requests to Build a Doc endpoints.
  • Fix: Whitelist the connector endpoints or work with your network admin.

Debugging checklist

  1. Check the flow run history and inspect the failing action’s error for HTTP status code and request ID.
  2. Confirm which connection the flow is using (connection dropdown inside the action).
  3. Recreate the connection: Select a Build a Doc action. Select ‘Change Connection’. Click to + Add new connection, paste the API key, and save.
  4. If the error indicates rate limits, check your subscription quota/usage.
  5. If network errors appear, test connectivity from your environment to the Build a Doc API endpoints.

Support & escalation

If you’ve followed the checklist and still need help, send support the following items:

  • Timestamp (UTC) of the failing run.
  • Flow run ID and failing action name.
  • Connection name used by the flow.
  • HTTP status code and request id from the action error (if present).
  • A minimal reproduction step showing how to reproduce the connection failure. For faster response, reproduce the problem with a single minimal flow that demonstrates the connection issue.