Four small planes linked by dotted lines to one central platform

Putting your connected apps to work

Prompt patterns for email, files, docs, spreadsheets, chat, project, developer and billing apps.

Features

·

Plugins

·

·

3 min

Plugins let Babbily use live context from the apps you already work in, and prepare actions you approve. These examples are for when you know which app you want Babbily to use and want a sharper prompt to start from.

Babbily can only use the plugin access you authorize. Anything that sends a message, updates a record, changes workspace content or affects customer and billing data waits for your approval first.

Google Workspace

  • Gmail for email threads. “Use Gmail to find the latest thread with this customer. Summarize open questions, blockers, and suggested next steps.” Babbily can use several Gmail tools in one reply, so you can ask it to find a thread, summarize it and draft a reply together. Check recipients, subject, body and destination before you choose Send or Create draft.

  • Google Drive to find and reference files you can access. “Search Google Drive for recent planning docs about this launch and summarize the common themes.”

  • Google Docs to create, search or update documents. “Turn this chat into a Google Docs outline for a customer-facing implementation brief.” Review the destination and content before approving.

  • Google Sheets for rows, columns, formulas and ranges. “Use Google Sheets to summarize this pipeline sheet by status, owner, and next action.” Ask for proposed formulas or updates before approving changes.

  • Google Slides to inspect, draft or update presentations. Slide work goes best when you give the audience, the number of slides and the level of polish you need.

  • Google Calendar for schedule context and meeting prep. “Use Google Calendar to summarize my upcoming customer meetings this week and prepare a prep checklist.”

Microsoft

  • Outlook for email and calendar context. “Use Outlook to find recent emails from this partner and draft a concise follow-up.”

  • Excel for workbooks, tables, formulas, charts, filters and ranges. “Use Excel to summarize this workbook by region and flag rows that need follow-up.” Ask for a summary of proposed changes before approving updates to shared workbooks.

  • Microsoft Teams for chats, channels and meeting context. “Use Microsoft Teams to summarize decisions from this project channel and list open owners.”

Collaboration and project work

  • Slack to summarize channels, messages and threads. “Use Slack to find the latest decision about this launch and summarize who owns each next step.”

  • Notion to search pages, databases, notes and comments. “Use Notion to find project notes for this initiative and turn them into a current status summary.”

  • Asana for tasks, projects, owners and deadlines. “Use Asana to summarize this project’s current status, blocked tasks, and owners.”

Developer and operations

  • GitHub for repositories, issues, pull requests and code context. “Use GitHub to summarize this pull request, list risks, and draft review questions.” Repository permissions still control what Babbily can see.

  • Vercel for deployments, projects, logs and hosting context. Keep requests to visible deployment and project signals rather than sensitive operational details.

  • Sentry for issues, traces, release health and incident context. Use summaries and customer-safe details instead of pasting sensitive event payloads.

  • Supabase for authorized project context. Keep credentials, private keys and confidential data out of chat.

Customer and business

Stripe can reference authorized customer, billing, payment and subscription context. “Use Stripe to summarize this customer’s subscription status and prepare support notes.” Treat billing context carefully, and never paste card numbers or sensitive financial identifiers into chat.

When an answer seems incomplete

  • Confirm the plugin shows as connected in Settings > Plugins.

  • Check that your role in the connected app can access the item.

  • Be more specific about the app, folder, channel, project or person.

  • Use Manual tool mode and choose the plugin directly.

  • If you’ve just connected the app, wait until it finishes preparing its tools.

  • Revoke and reauthorize access if permissions changed.

If an action is waiting for approval, choose Allow or Send on its card in the chat. Typing approval in a message doesn’t run anything.

Read the full docs ↗

Category

Features

Product

Plugins

Date

Reading time

3 min

Start with a question

Auto picks the right model for every message, and you can start for free.