Contact support

1. 1Work through the common issues triage page.
2. 2Follow the specific troubleshooting guide for your symptom.
3. 3Confirm a general question works, which isolates the problem to authorisation or data.
4. 4Check whether the behaviour is a documented limitation.

• What you were trying to do, in one sentence.
• What happened instead, as the exact error text.
• When it happened, approximately.
• Which workspace and which provider, by name only.
• Whether a general question works and whether a narrow private-data question works.
• Browser and device, if the issue is visual.

• Your provider password, in any form.
• Access tokens, refresh tokens or client secrets.
• Provider credentials of any kind.
• Full copies of private business data.

If you suspect a data exposure or a vulnerability, stop using the affected flow, revoke the relevant session or connection, and report it with the timeline and the workspace involved. Do not continue investigating in a way that spreads the data, and do not include the exposed content in your message.

If the product behaves differently from what these guides describe, the verified current behaviour wins. Report the discrepancy with the page and the actual behaviour so the documentation can be corrected rather than trusted over reality.

Most slow reports are slow because they lack one specific fact. Including these turns a week of back-and-forth into one answer:

• The exact error text, copied rather than paraphrased.
• The account email you signed in with, and the workspace.
• Whether a general question works and whether a narrow private-data question works.
• What you changed immediately before it started failing.

A short, precise report is faster than a long narrative. If you cannot state the failing gate, say which question reproduces it.