Periodic consumption report
Weekly summary of AI use by area and by model for management.
Automations
Your organization's recurring tasks, configured once and run regularly
Periodic reports, summaries of updates, pending follow-ups: a significant share of work repeats with the same structure. NiuCore lets you schedule it so operations continue without someone having to start it each time.
How it works
Defining the task
The user describes, in conversation, what needs to be done, with what information and with which skills.
Frequency
The schedule is stated in natural language—"every Monday at 8:00 a.m.," "the last business day of each month"—and NiuCore interprets and schedules it.
Execution
NiuCore carries out the task with the resources its author has access to: the libraries, connectors, rules and models of their areas. If the user indicated when scheduling it that it requires approval, the task stops until its execution is approved.
Delivery
The result of each run is available in the automations section of the application. The user can also schedule it to be sent to a notification channel they have configured, such as Gmail or Slack.
Governance
Automation subject to the same safeguards as manual work
An automation built with external tools operates outside the organization's controls. In NiuCore, every recurring task runs with active anonymization, with its author's identity and permissions, with the rules that apply to them, and with the platform's consumption record: it cannot do anything its author could not do manually. Automation is not an exception to AI governance, but an extension of it.
- Active anonymization on every run
- Identity, permissions and rules of the user who created it
- Prior approval of each run, when the user configures it that way
- Consumption recorded and attributed to its author's license
Use cases
Library updates
Digest of the documents added or modified in the period.
Follow-up on pending items
Preparation of the follow-up emails that correspond to each person responsible.
The week's agenda
Consolidation of the team's commitments from the calendar.
Operational continuity
Two complementary capabilities
An automation carries out previously defined work, at the established frequency. The next best action recommends a step based on the context and on the area's memory. The first provides regularity; the second, guidance. Both contribute to continuity of work.
Frequently asked questions
Who can configure an automation?
Any user with a license can create automations for their own tasks.
Under what identity does the task run?
With its author's identity and permissions: their areas, their libraries, the connectors they authorized with their account, and the rules that apply to them. An automation cannot do anything its author could not do manually.
Can an automation carry out actions without approval?
The user decides when scheduling it. If they indicate that the automation requires approval, the task stops on each run until it is approved.
How are pauses and failures handled?
From the automations section, the user can pause, resume, edit and delete their tasks. If a run fails, NiuCore notifies them in that same section.
What happens if the author runs out of allowance or no longer has a license?
The automation is paused. The user can resume it once they have niucredits or an active license again.
Do automations consume niucredits?
Yes. Each run consumes niucredits from its author's license, in the same way as a conversation, and is recorded in the consumption panel.