Integration Access, Reconnects, and Provider Errors
Use this guide to get a connection working again, find a missing integration or resolve an action that cannot access the expected file, mailbox or record. Start with the message shown and the account connected to Hatz.
Match the issue to the next check
Integration missing: check that it is available in the selected workspace and product surface.
Sign-in or authorization expired: use Connect or Reconnect and complete the separate sign-in flow. Enter credentials there, rather than in Chat.
Administrator consent needed: ask the provider administrator to approve the required access, then finish your personal connection if needed.
Connected, but access denied: open the resource directly in the provider product using the connected account. Check that account’s permissions for the requested action.
Hatz access denied: review the user’s role, group, feature and shared-item access.
Timeout, throttle or provider error: read the error and check the provider’s status page. Follow any retry timing shown.
Resource missing or stale: check the source resource and the integration’s sync status or timing.
Check which connection the task uses
A connection can belong to an individual user, a workspace, a service account or an API Member. Reconnect your own expired connection through the action offered in Hatz. For an administrator-managed connection, ask its owner to update the credential.
Confirm the workspace and account used by the Agent, workflow or automation. Sharing a Workshop item does not transfer its creator’s personal connection. An interactive chat can discover tools during a run; a saved automation uses its saved tools and execution setup.
If reconnection succeeds but the action still fails, check the requested resource and supported action. A failed availability check or missing tool needs its own investigation. Before repeating a send or update whose result is unclear, check the external system to see whether it completed.
Microsoft 365 and PSA checks
Microsoft 365: identify the feature involved—Hatz sign-in, Entra SAML/SCIM, Outlook, Calendar, Teams, OneDrive, SharePoint, Excel, the file picker or generated-file export. Each uses its own permissions and connection flow.
OneDrive and SharePoint: open the file, folder or site directly with the connected Microsoft account. For an Agent, also review its saved file/folder scope.
PSA connectors: in ConnectWise, Autotask, Halo or the relevant provider, check the API Member or service account, security role and permissions for the specific object.
Supported actions: check the tools available for the integration in Hatz. Provider access and Hatz tool availability both need to cover the requested action.
Get help from Support
Contact Support when a supported action still fails after these checks, the same connector fails for several users, or you need help confirming integration availability.
What to include in a support ticket
The workspace, affected user, provider and connected account or service-account name.
Where the action ran: Chat, Agent, classic workflow, saved automation, file picker, export or API. Add the visible chat or run link.
The action, expected result, actual result and time with timezone.
The error text or screenshot and any displayed correlation ID. Say whether reconnect changed the result and whether the account can access the resource directly.
For Custom MCP, the server address, authentication method and tool or endpoint involved.
Before you open a ticket
Check the integration guide for the actions your account supports. Availability, permissions and sync timing vary by provider and account configuration.
Remove passwords, tokens, API keys, signed URLs and private document content from diagnostic details. Support can arrange an approved path if further information is needed.
