All posts

Connect an app without starting the explanation again

Connecting an app should help finish the task you already described. Start with the outcome, add the missing source, and continue from there.

Upfyn · 3 min read

You have explained the report you need. The assistant understands the audience, the date range, and the questions to answer. Then you reach the missing piece: the information is in an app that has not been connected.

Starting a new conversation at this point means doing the briefing twice. A more useful connection adds the needed tools to the work already in progress.

That is the purpose of connecting apps from the Upfyn conversation.

Start with what the information is for

It is tempting to begin by opening a catalogue and connecting everything. A smaller starting point is easier to understand: choose one result and connect the source it needs.

For example:

Prepare a morning brief from recent customer emails. Show who needs a reply, what they are waiting for, and any deadline mentioned. I want drafts for review after I choose the messages.

The request establishes why Gmail access is useful. It also separates the initial review from later actions, so you can judge the connection with a clear task.

Check the account before continuing

Open Connectors, choose the available service, and follow the provider's sign-in and authorisation flow. Many people have both personal and work accounts, so check which one you are connecting.

A successful sign-in to the wrong account can still produce plausible information. Naming the intended account or organisation in the task helps avoid that confusion.

Return to the same conversation when authorisation completes. The authorised tools should become available there, allowing you to continue with the briefing you already gave.

Ask for a small result you can inspect

For the first request, use a short period or a familiar set of records. Ask for source links or clear identifiers so you can check what was read.

In the inbox example, review a small group of messages before asking for a wider summary. In a sheet, inspect the columns and a few records before requesting changes.

This helps answer two separate questions: did you connect the right source, and did the assistant understand the job?

Extend the workflow deliberately

Once the source is right, continue in the same chat:

Draft a reply to the first message using the approved delivery information in this project. Show me the wording before sending.

Or, for a sheet:

Propose updates for these confirmed records. Explain any item you cannot match before writing the changes.

Connecting an account makes tools available within the access granted by the provider. Upfyn's active tool permissions and your instructions determine how those tools may be used. Reading, drafting, and sending need not have the same permission.

Keep the context when a connection needs attention

If authorisation fails or expires, check the connector status and reconnect the intended account. Return to the existing task so you can continue from its instructions.

If a tool is unavailable, the assistant should identify the missing access. A summary that quietly omits the main source is less useful than a clear explanation of what needs reconnecting.

The current desktop catalogue is the place to check which services and actions are supported. Availability can change, and a familiar app name does not guarantee every possible action.

Reuse the result before repeating the job

After the first useful result, you can keep refining the task or make a suitable preparation step recurring in Analyst. Test the connected workflow before scheduling it, and keep the required desktop and connections available.

Try the spreadsheet workflow · Try an inbox brief

Keep reading