Skip to main content
Once an app is connected, there’s nothing to learn. You don’t pick tools or build workflows — you ask for outcomes, and your assistant figures out which apps and actions get you there.

​
Ask in plain language

  • “Pull this week’s new signups from HubSpot and give me the highlights.”
  • “File a GitHub issue for the crash Priya reported, with the log attached.”
  • “Move the launch tasks in Linear to next sprint.”
  • “What did the team decide in Notion about pricing?”
Requests can span apps, too: “check the new leads in HubSpot and post a summary to Slack” is one instruction, not two.

​
Put apps on a schedule

Connected apps really pay off in recurring tasks. Describe the routine once and your assistant runs it on schedule:
  • “Every Monday at 9, summarize open Jira tickets by priority and email me.”
  • “Each morning, check HubSpot for new leads and message me the ones worth a call.”
Scheduled work uses the same permissions as everything else — tools set to Ask every time still wait for your approval.

​
When something’s missing

Your assistant is upfront about gaps rather than guessing:
  • App not connected? It tells you, and points you to the Integrations tab — then carries on with whatever it can do in the meantime.
  • Tools still syncing? Right after you connect an app, it may say the tools are syncing and will be available shortly.
  • Missing permission? If an action needs a scope you didn’t grant, it explains and asks you to reconnect the app with the extra access.

​
Apps without a gallery entry

The gallery is the easy path, but it isn’t the boundary of what your assistant can reach:
  • Any service with an API. Store a credential as a custom secret and your assistant can work with the service’s API directly — it can integrate with virtually any service that offers one.
  • Any app with a screen. Your assistant has its own computer and browser. For apps with no API at all, it can work the same way you would — signing in and clicking through the interface.

​
During onboarding

Connecting your first app is one of the onboarding checklist steps — clicking the row opens the Integrations tab, and connecting any one app from the gallery completes it. Your assistant narrates as you go, and if you’d rather be shown than told, it will happily walk you through on a screen-share call.
A good first app is the one your day already revolves around — your CRM, your ticket tracker, or your team’s knowledge base. Connect it, then ask your assistant a question you’d normally dig for manually.