01
Start with what happens.
Choose a supported trigger: a webhook, schedule, ticket event, or manual run. Map the incoming data into the steps that need it.
NODEHUB AUTOMATIONGive the work a path.
Give the work a path.
Keep control of every turn.
Connect events, tools, AI decisions, and people in a workflow you can inspect. Start from a webhook, a schedule, or a customer request.
Customer request to coordinated response Illustrative configuration
Scroll the canvas to explore every step.
FROM EVENT TO OUTCOME
A process your team can follow.
Build automation around the job. Bring in the services it needs, define the next step, and see what happened when it runs.
02
Make the next step explicit.
Use conditions to choose a path, a bounded AI decision for judgment, and a human approval where the next action deserves review.
03
Follow the result.
Inspect run history and step outputs. Find the failed operation, review its configuration, and decide how the process should recover.
TOOLS, INTELLIGENCE, AND HUMAN JUDGMENTGive every agent a job.
Give every agent a job.
Give every action a boundary.
Choose a model from your configured AI accounts, connect the knowledge and tools it needs, and put approval steps before actions that require a person.
01 / TRIGGERS
Start with a signal.
A customer message. A scheduled check. An event in another app. Give each one a clear next step.
02 / INTELLIGENCEAn agent with a job.
Meet your next agent An agent with a job.
And the tools to do it.
Bring your model, knowledge, and selected operations into the same workflow.
Model
Tools03 / HUMAN JUDGMENT
You decide where AI stops.
Ask for approval before the next action. Give your team an explicit place in the process.
04 / LOGIC
Every path, intentional.
Conditions and AI decisions route each request to the next appropriate action.
Notify the team05 / VISIBILITY
Keep the trail.
Inspect workflow runs and step results. Follow the work back to what actually happened.
06 / CONNECTIONS
Your stack belongs here.
Use supported service actions, HTTP requests, and agent tools to connect the work.
BETTER TOGETHERThe workflow does the work.
The workflow does the work.
Desk keeps the context.
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 DeskDeskThe customer context
AutomationThe work that follows
THE PRACTICAL DETAILSBefore you
Before you
get started.
Can I use Automation without a support inbox?
Yes. A workflow can begin with a webhook, schedule, or manual run. Customer conversations are another possible starting point, not a prerequisite for building automation.
Does every workflow need AI?
No. Use explicit conditions and service actions when the process is predictable. Add AI decisions or agents where their configured capabilities fit the job.
Are AI provider costs included?
Model usage depends on the AI account and provider you configure. Connecting a model does not make its usage free. Check the provider's charges and set run limits before enabling an AI workflow.
What happens when an action fails?
Run history records step results and errors. Inspect the failure and use the controls supported by that step. Configure retries carefully for external writes so a repeated request does not create a duplicate action.
Does a template run immediately?
No. Installing a Hub workflow creates a private draft. Review its configuration, connect the required accounts, and test the process before publishing it.
Build your next clear step.
Start with one process. Connect the tools that make it work.
Get started with Automation