NNextsAI Docs

Automation & Extensions: Combine Capabilities for Repeatable Work

Choose workflows, scheduled tasks, or Bot routines, then add the skills, tools, and connections they need.

Automation determines the order and timing of repeated work. Extensions supply the methods, tools, and account connections used to perform it.

What is in this category?

FeatureUseful forWhere to start
WorkflowsSave multiple steps as a visual processActivity bar → Workflows; see Workflows
Scheduled tasksRun once at a time or on a recurring scheduleTasks; see Scheduled Tasks
Bot routinesGive a long-term assistant recurring responsibilitiesBot details → Routines; see Bots
Skills and recordingReuse methods and demonstrated actionsSkills · Skill Recording
Plugins and MCPAdd tools required by the processPlugins · MCP
Connected appsAuthorize email, calendar, and other accountsConnected Apps

Choose how to run the work, then add its required capabilities. Installing a skill or plugin does not create a schedule, and creating a schedule does not authorize an account.

Which option should I use?

  • One task, once: describe it in chat.
  • The same method, started by you each time: save a skill.
  • Multiple steps, conditions, or human approvals: create a workflow.
  • A particular time: schedule the task or a runnable workflow.
  • Ongoing responsibility for one assistant: configure a Bot routine.

Example: prepare a weekday task list

  1. First ask in chat to read today's calendar and prepare a task list.
  2. Confirm the account and output format are correct.
  3. For a single recurring task, save the objective, account, and format in a scheduled task. Use a workflow if it needs several steps.
  4. Set the time, recurrence, and time zone, then check the next run time.
  5. Run it manually and review the output before enabling recurrence.
  6. After its first automatic run, check the record and confirm the host and connections worked.
Every weekday morning, organize today's calendar into a task list.
Use my work account, sort by start time, and flag scheduling conflicts.
Keep the result in the task; do not send it to anyone.

Result: task or workflow history shows the execution status and result. Desktop tasks require the host to remain on, online, and running Nexts. Do not assume they continue in the cloud after shutdown.

Extend an existing process

Identify the missing piece: add a skill for a consistent method, a plugin or MCP for missing tools, an account connection for external data, or a Bot for long-term context. Test the new step manually before resuming automatic runs.

Troubleshoot the specific failed task or node. Before retrying a send, submission, or deletion, check whether the previous action already succeeded.

Detailed guides: Workflows · Scheduled Tasks · Extensions.

On this page