Skip to main content
Use this guide when a plugin is missing, stuck, disconnected, or returning less context than expected.

​
Plugin status meanings

​
If setup does not open

1

Allow pop-ups

Allow pop-ups for Babbily, then choose Connect, Continue, or Reconnect again.
2

Finish the app flow

Sign in to the connected app and approve the permissions you are comfortable granting.
3

Return to Babbily

Go back to Settings > Plugins and wait for the status to refresh.
4

Try the plugin in chat

Ask for the connected app by name, choose it from the composer, mention it with @, or use / when plugin-specific commands are available.

​
Reconnect after the Plugin migration

Babbily retired former Smithery connections when Plugins moved to Composio. Credentials were not transferred between providers. If an app appears under Previous connection history, choose the current Plugin in Settings > Plugins and complete the new authorization flow. An older Scheduled Task may also show Plugin reselection required. Edit that task, choose the connected Plugins it may use now—even if the choice is none—and save it before running or resuming the task.

​
If Babbily cannot find something

Plugin answers depend on what your connected-app account can access. Try:
  • Name the app, folder, channel, project, repository, board, person, or time window.
  • Confirm you can open the item directly in the connected app.
  • Check whether your app role has permission to view it.
  • Use Manual tool mode and choose the plugin directly.
  • Reconnect if your app permissions recently changed.

​
If an action needs approval

Some plugin actions ask for approval before running. Review the content and destination before approving:
  • Recipients and subject lines.
  • Documents, sheets, slides, pages, tasks, or records being changed.
  • Billing, customer, payment, or support context.
  • Automations or workflow changes.
The approval card appears in the conversation as soon as Babbily prepares the action. Choose Allow to run the action, or Send for an email draft. Choose Cancel to decline it. Nothing runs until you make a choice on the card.
Typing “approved” or “yes” in the chat doesn’t approve an action. Babbily tells you that nothing has run and points you to the waiting card. Scroll to the card and choose Allow or Send. You can do this later in the same chat, even after sending other messages.
Approval cards and email drafts expire 24 hours after they appear. When a card expires, Babbily cancels it, nothing runs, and the card is removed. Ask again to create a new request.
A waiting approval card or email draft counts as active work in the chat. Choose Allow, Send, or Cancel on it first. If you leave it unanswered, Edit message and Retry become available again when the card expires.
If you see “The Plugin action completed, but I could not continue the response. Please try a new message.”, the action already ran. Choose Retry or send a new message to continue.
“Gmail couldn’t finish this.” means the connected app didn’t complete the action. Check the request and ask again.“Babbily couldn’t confirm whether Gmail finished this. Check Gmail before asking again.” means the outcome is unknown. Open the connected app and check before you ask again, so the action doesn’t run twice. Babbily shows the name of the Plugin you used in these messages.
Do not approve a plugin action unless you understand what it will do.
In a chat that uses shared project instructions, Babbily may ask for approval even when a Plugin only reads information. Review the app and requested access before choosing Allow.

​
If Deep Research doesn’t use a Plugin the way you expect

Deep Research reads from Plugins you select only for steps that read data. It doesn’t send, create, or update anything in a connected app, and it doesn’t pause for approval. If you need an action in a connected app, ask for it in a regular message after the report is ready. If a selected Plugin seems to be missing from a report, confirm the Plugin is connected, then try a narrower request that names the app and what to look for. In a chat that uses shared project instructions, Deep Research may skip Plugin reads.

​
If you want to remove access

Use Settings > Plugins to disconnect apps where controls are available. If you cannot remove access from Babbily, revoke access in the connected app’s own settings and contact support if you still need help. Removing plugin access does not delete content inside the connected app.

Plugins

Connect apps and understand approval-required actions.

Plugin capabilities

See what each plugin can help you find, reference, draft, or update.

Data controls FAQ

Review plugin privacy and access controls.

Contact support

Learn what to include when a plugin still fails.