Connected workflows · Early access
Help that can use your connected tools.
Connect a question to a supported next step. Use selected tools for your own work, a shared team task, or a customer request, with the relevant context and a result you can inspect.
Get Help.ai updates- Choose the accounts and tools
- Reuse task instructions with Skills
- Inspect tool inputs and results
A connection becomes useful when the task is clear.
Start with one repeated job: find information, clarify a request, prepare a response, or use a supported action in another service. Give the agent the account access, tool, and instructions that job needs. Help.ai keeps those choices alongside the conversation, rather than treating a connected account as permission to do everything.
Bring the right service into the task
Use an authorized connection for a supported lookup or action. Help the person making the request get to the next step, while keeping the agent’s access tied to that job.
Give the agent a defined set of tools
Select the enabled workspace tools and relevant knowledge for the task. Reusable Skills can provide instructions and tool choices for recurring work.
See what happened
Inspect a tool’s inputs, result, or error in the conversation. When it requests approval, review the proposed action and approve or reject it before that step continues.
Start with one useful, bounded workflow.
Choose the task and confirm the capability
Describe the intended result and identify the exact service and action it needs. Check that the required provider and tool are available for your workspace.
Connect, assign, and explain
Authorize the account, select the agent’s tools and knowledge, and provide clear instructions. Keep access and the requested work aligned with the intended task.
Review the result before relying on it
Run the supported task in conversation. Check any requested approval, inspect the returned result, and handle missing information or a failed connection before continuing.
Connect assistance to the next piece of work.
The tool and its permissions determine what can happen. These are useful starting points for a workflow you can define and review.
Look up information for a response
Combine relevant Library knowledge with an enabled lookup or search tool. Find what you need for a decision, help a colleague, or explain an answer to a customer using the returned information.
Prepare a follow-up from the conversation
Use the discussion and supplied context to draft a summary or response. Sending it through another service requires a separate supported action and the necessary permissions.
Collect the missing details
Ask a focused clarification or use a structured form when the task needs consistent information. Check the details before using them in the next step.
Support a repeatable customer task
Give a customer-facing agent the knowledge and enabled tools needed for a defined request. Keep your team involved when the case requires judgment or an unsupported action.
Build on the workspace capabilities you already use.
Connections, tools, knowledge, and Skills have different roles. A useful workflow makes each role explicit.
- Connected accounts
- Manage authenticated service connections and their available capabilities. Provider status and permissions affect which connection can be used and what it can do.
- Agent tools and MCP connections
- Select enabled tools for an agent and configure supported MCP servers where needed. The available catalog determines the integrations and actions you can build around.
- Reusable Skills
- Keep task instructions and allowed tools in a reusable workspace Skill. Select the Skill for the conversation or supported deployment configuration where it should apply.
- Action and approval states
- Tool cards show the proposed inputs and returned outcome. Approval controls appear for steps that request a decision; a suggested next action on its own is not an executed workflow.
Questions about Connected workflows
Does connecting an account enable every action in that service?
No. The provider, authorized permissions, available tools, and agent configuration determine the supported actions. Check the particular capability your workflow needs.
Is every provider shown in the catalog ready to connect?
The catalog can include providers that are not currently available. The connection UI shows their status and prevents selecting unavailable entries. Build around the providers and authentication methods available to your workspace.
Does every tool action require my approval?
The conversation shows approval controls when a tool step requests approval. That does not mean every tool is configured to ask. Review the selected tools and their behavior before using them for a process.
Does this create scheduled or unattended automation?
Connecting an account does not create a scheduled workflow. This page describes tools used within supported conversations and agent flows. Confirm a specific automation, its trigger, and its available actions before relying on it.
What if the connection or action fails?
Inspect the reported result or error and check the connection and required information. A requested or suggested action should not be treated as completed until its actual outcome is confirmed.
Make the next step useful to the person asking.
Get Help.ai updates for connected work you do yourself, coordinate with a team, or provide through a customer-facing agent.
We’ll email when access opens. Privacy Policy