Start with the right context.
Give the agent a focused task, an available model from your AI account, and the knowledge sources that help it answer. Supply the workflow data the task actually needs.
Bring instructions, knowledge, and selected tools together in a reusable agent. Make it part of a workflow your team can understand, test, and improve.
An illustrative support workflow using Desk + Automation. Agents can also run in Automation with your connected services.
Choose what it knows, what it can do, and where a person takes over. Keep those choices together as a version you can use again.
Give the agent a focused task, an available model from your AI account, and the knowledge sources that help it answer. Supply the workflow data the task actually needs.
Select supported operations and verified connections. Set execution limits, review requirements, and an expected output before you publish the agent.
Inspect the recorded run, tool calls, and outputs. Review a failed or uncertain action before retrying, then improve the next version with what you learned.
Gather context, summarize a request, or help route work. Put a human approval before the external action that needs review, and keep predictable steps as explicit rules.
A customer message. A scheduled check. An event in another app. Give each one a clear next step.
Bring your model, knowledge, and selected operations into the same workflow.
Ask for approval before the next action. Give your team an explicit place in the process.
Conditions and AI decisions route each request to the next appropriate action.
Inspect workflow runs and step results. Follow the work back to what actually happened.
Use supported service actions, HTTP requests, and agent tools to connect the work.
Bring customer conversations into the same workspace as the process. Connect the request, the decision, and the follow-up without rebuilding the story in another app.
Explore NodeHub DeskYes. Automation supports agents for work across connected services. Workflows that read or change native NodeHub tickets, customers, or companies need Desk + Automation. The support example above uses both products.
Choose from the models available through the AI accounts configured in your workspace. Provider support, account permissions, and model availability determine what you can select. Model usage is billed separately by your provider.
No. An agent uses its selected tools and configured accounts. Review each operation and its permissions before publishing. A verified connection confirms account access, not that every possible action should be allowed.
No. A Hub workflow installs as a private draft. Configure its model, knowledge, and tools; test the published agent version; then review the workflow before enabling it.
The configured request can include instructions, selected knowledge, supplied workflow context, and tool results. Review your provider's terms and your workspace configuration before sending sensitive information.
Build the agent. Test the result. Connect the next step.
Get started with Automation