A connector is valuable when it removes a handoff. You should be able to discuss an outcome, discover that the assistant needs an app, authorize it and continue in the same conversation.
The connection is not the job. It is a tool added to the job already in progress.
Begin from the outcome
Suppose you ask Analyst to prepare a morning brief from recent customer email. The assistant can understand the desired format before it has Gmail access. It should identify the missing capability and invite you to connect the available mail app.
That sequence is better than opening a catalog first and connecting everything. The request establishes why access is needed, which account matters and what the assistant is expected to do after authorization.
Upfyn currently exposes a smaller connector catalog than broad “hundreds of apps” platforms claim. The desktop app is the authority for what is available. Marketing should name the workflow and let the current catalog speak for itself rather than promising tools that are not installed.
What the OAuth step should do
OAuth lets the service confirm that you are granting access without giving Upfyn your password. Depending on the provider, the flow can open a browser, show the requested access and return to the desktop after approval.
When authorization completes, the connector status should update and its tools should become available to the current chat. You should not have to start a new chat, reattach files or explain the desired output again.
If the provider requires a device-style code, the desktop can show a short random code and a copy action, then detect completion after you authorize. When a direct “Authorize now” return is available, that path should be the smooth default. The goal is one account identity across the website, gateway and signed-in devices, with visible sessions that can be revoked from the user dashboard.
Connection is not unlimited permission
Authorizing an app establishes identity and the scopes the provider grants. Upfyn’s tool policy still determines how the assistant may use those capabilities.
An email connector can expose separate actions for reading, drafting and sending. A sensible first task allows reading and drafting while keeping send behind approval. A calendar connector can read availability without automatically creating or deleting events.
Treat “connected” as available, not pre-approved for every consequence. Review the tool settings and choose always, ask or off according to the action and your risk tolerance.
Keep account choice explicit
Many people have more than one Google, Microsoft or workspace account. Confirm which account completed the OAuth flow before asking the assistant to act. A connector attached to the wrong inbox can still return plausible information, which makes the mistake harder to notice.
State the expected account or organization in the instruction. For sensitive work, ask the assistant to report the connected identity and the time range it intends to read before it fetches content.
If authorization expires or is revoked, the assistant should identify the missing connection. It should not quietly replace that source with web search or another account.
Use the chat as the audit narrative
The conversation should record why the app was connected and what you asked the assistant to do with it. That makes the sequence understandable later: request, missing tool, authorization, tool use, result and any approval.
For recurring work, test the connector in a normal chat first. Confirm that the tool returns the expected data and that the output is useful. Then create the schedule in Analyst. Temporal can preserve the recurrence, while the selected connector and desktop environment supply the execution path required by the job.
A safe first connector task
Start with a read-only outcome. Ask for a short list of recent items, a classification or a draft that remains inside Upfyn. Do not make the first test send messages, change records or invite people.
For an inbox, ask for messages that need a reply, the sender, the reason and a proposed draft. For a calendar, ask for open time windows without creating events. For a project service, ask for the current status and links without updating issues.
Once the result is correct, add one controlled write action and keep it behind approval. This progression separates connection problems from action-policy problems.
Troubleshooting without losing context
If the authorization window closes early, return to the same chat and retry. If a code flow is used, copy the latest code rather than an older one. If the connector reports success but no tools appear, check its status and permissions before starting another conversation.
Do not paste access tokens into the chat. OAuth exists to keep credentials out of ordinary messages. If a provider shows a short verification code, treat it as temporary and use only the official authorization page opened by the desktop.
When you disconnect an app, expect future turns and scheduled jobs that depend on it to stop at that boundary. Revocation should be real, not a cosmetic toggle.
Ask Upfyn
Continue this task using the connected app. First confirm which account is authorized, list the exact tools you need, keep external writes behind approval, and preserve the outcome and context already established in this chat.