Tactiq integrations let you send meeting transcripts, AI summaries, and workflow outputs to connected apps. If an action fails, use this guide to check the connection, confirm access to the destination, and retry the affected action.
Identify where the error occurs
The action that fails helps you decide whether to check authorization, destination access, or the workflow setup.
Identify the integration involved.
Note whether the error appears while connecting, authorizing access, selecting a destination, sharing a transcript, or running a workflow.
Save the complete error message, including any reference number.
Note the date, time, and time zone of the failed attempt.
Use the table below to choose your starting point. An error message alone does not confirm the cause.
Error or symptom | What to check |
A | Check whether the error occurs on the authorization page, in Tactiq, or when opening the destination. Start the action again from Tactiq rather than reusing the failed authorization link. |
| Check the connection used by the affected action. Reauthorize it where available. |
A permission error appears | Confirm that the connected account and the integration have permission to access and write to the destination. |
The integration shows as connected, but sharing fails | Check the destination and required permissions, then refresh the affected connection. |
A workflow does not send data | Check whether it started, paused for input, failed at a step, or completed without the expected content. |
For example, if Notion connects successfully but a database does not appear, check whether that database was included in the pages authorized for Tactiq.
Check the account and destination
A successful connection does not guarantee access to every folder, page, channel, or CRM record.
Before reconnecting:
Confirm that you are signed in to the correct Tactiq account.
Confirm which account and workspace you connected in the other app.
Open the destination directly in that app and check that you can add the content you want to send.
Check that the destination still exists and that its permissions have not changed.
Use these checks for the affected integration:
Integration | What to check |
Google Drive | Confirm that the connected Google account can create files in the selected folder. |
Notion | Confirm that the page or database is included in the access granted to Tactiq. Your own access to it does not automatically give the integration access. |
Slack | Confirm that you connected the correct workspace and added the Tactiq app to the destination channel. See How to set up Tactiq for Slack channels. |
HubSpot or Pipedrive | Confirm that you connected the correct CRM account and can access the record selected by the integration action. |
Tactiq must be added to the Slack channel before it can share content there. Tactiq Help Center
If access has changed, ask the destination owner or workspace administrator to restore it, or select another destination.
💡 Note: If authorization says administrator approval is required, ask your organization’s administrator to review the request. Reconnecting does not override organization-level restrictions.
Refresh the affected connection
Reauthorizing can restore access when a connection is no longer valid or needs updated permissions. The connection controls depend on the integration and how you use it.
For integrations managed in account settings
Open the Tactiq dashboard and go to
Account & Settings→Integrations.Find the affected integration and select
Disconnect, where available.Select
Connectand sign in with the account that should access the destination.Review and grant the permissions required for the action.
Return to the transcript or workflow and retry.
Google Drive’s automatic transcript-saving integration is managed from this page. See How to set up Google Drive integration. Tactiq Help Center
For connections used inside a workflow
Go to
My Workflowsand open the affected workflow.Open the integration step that is failing.
Complete any connection or authorization prompt shown for that step.
Confirm the selected destination and save any changes.
Google Drive workflows can prompt you to authorize access from the integration step. Pipedrive’s documented reconnection process starts in the workflow’s Build tab. Follow the instructions for the affected integration rather than assuming every connection is managed from account settings. Tactiq Help Center
If the connection cannot be disconnected or reauthorized, contact Support with the error details.
💡 Note: After reconnecting, review the destination and any automatic-saving settings before testing again.
Check a workflow that does not send data
A workflow can fail to deliver content because it did not start, is waiting for input, encountered an error, or has an incomplete output step.
Go to
My Workflowsand open the affected workflow.Review the failed run in its activity history, if available.
Note the failed step, complete error message, and run time.
Check the integration step’s connection, destination, and content fields.
Confirm that the output includes the transcript or AI result you want to send.
Use the workflow’s behavior to narrow the cause:
It did not start: Check its trigger and conditions. An automatic workflow starts only when the configured conditions are met.
It is waiting for input: Complete the requested selection or confirmation. HubSpot and Pipedrive actions may require you to select a contact before continuing.
An integration step failed: Check that step’s connection and destination permissions.
It completed with missing content: Check that the destination fields include the intended meeting data or output from an earlier AI step.
An automatic trigger does not remove the need for a CRM contact selection when the action requires one. Tactiq Help Center
For example, if the AI step succeeds but the Google Drive step fails, start with the Google Drive step’s connection and folder access.
Test authorization in a separate browser session
A separate browser session can help check whether saved sign-in data or another extension is affecting authorization.
Use this optional step if the authorization page fails to open or repeatedly redirects:
Open an Incognito window in Chrome.
Sign in to Tactiq with the same account used for the affected action.
Sign in to the connected app with the intended account.
Start the connection process again from Tactiq.
If authorization succeeds there, retry in your usual browser profile after checking its sign-in accounts and extensions.
💡 Note: A new standard Chrome window uses the same browser profile and saved sign-in data. It does not create a separate session.
Retry and confirm the result
The action is successful when the expected content appears in the intended destination.
Save any connection, destination, or workflow changes.
Retry the affected sharing action or run the workflow for one selected meeting.
Complete any contact-selection or confirmation prompt.
Open the destination and confirm that the expected transcript or summary is present.
Check the destination before repeating the action to avoid sending the same content more than once.
Contact Tactiq Support
If the issue continues, send Support enough detail to identify the failed action and investigate it.
Include:
The affected integration and what you were trying to do.
A screen recording showing the steps and error, or a screenshot of the complete error message.
The workflow URL, if the issue involves a workflow.
The troubleshooting steps you have already tried.
Support will review the details and explain the available next step or request any additional information needed.
Need help? Contact [email protected].