All modules

Automations

Hand routine to the system. Try it as a dry run first.

An automation runs on a schedule or when a record is created, changed or deleted. It's built from steps: find, create or update a record, send an e‑mail or a notification, call an external service. By default it runs as a whole: either all of it goes through, or nothing is saved.

switched on by an admin

The automation monitor in core3: enabled workflows, running processes, run history and the workflow list.The automation monitor in core3: enabled workflows, running processes, run history and the workflow list.
A real core3 screen with demo data of the fictional Slovak company Preciz SK s.r.o.

Worth a closer look

Dry run first

A dry run is a real run that rolls back at the end. It finds the same errors a live run would, but saves and sends nothing. Calls to external services and AI are only simulated.

Dry runOverdue tasks
StepResult
Every day at 7:00started
Find overdue tasks4 tasks
For each task4×
Notify the assigneenot sent

Nothing was saved or sent.

Runs with the rights you choose

Each automation has a persona it runs as, and if it can't resolve one, it doesn't start. Share it with employees or roles. When you build it, it warns about loops and cascades.

SettingsOverdue tasks
Run as
System automation
Run
all or nothing
Retry on error
3 times
Shared with
Project managers

Build a workflow from steps

Drag steps from the palette onto the canvas and they line up one under another. There are fourteen: record steps, e‑mail, notification, a loop over records, text and list helpers, an API call and an AI step. Conditions with and/or groups and values from earlier steps. Before saving, you try the workflow as a dry run.

Overdue tasksworkflow
Search stepsDry run

Records

  • Find record
  • Create
  • Update
  • Archive
  • Delete

Communication

  • E-mail
  • Notification
  • Teams invite

Container

  • For each

Other

  • Text and list helpers
  • API call
  • AI assistant
  • Transcription
  • In-app broadcast
  1. 1Startevery day at 7:00started
  2. 2Find recordoverdue tasks that are not done4 tasks
  3. 3For eachtask from step 24×
    1. Drop a step here
    2. 3.1Notificationto the task's assigneenot sent

Nothing was saved or sent.

Steps with a dot need Microsoft 365 or an AI provider.

Monitor and logs

A health overview, seven-day statistics and issues such as a stuck run or a missed schedule. Every run has a step-by-step log, and every 10 minutes inconsistencies fix themselves.

Monitor7 days
AutomationRunsStatus
Overdue tasks7healthy
Attendance reminder1healthy
Archive done tasks301 error

AI in Automations

When AI is switched on.

All about AI in core3
  • An AI step with your own instruction, its result for the next steps(live)
  • Transcribing an audio recording(needs another module or service)speech to text

Permissions in this module

An automation runs with the rights of the persona you choose, not of whoever changed the record. That persona can have more rights than the automation's author, so an administrator sets it.

How permissions work

Everything the module does

No embellishment. Each feature says whether it runs straight away, whether an admin switches it on, or what else it needs.

  • live
  • switched on by an admin
  • needs another module or service

Triggers

  • On a schedule: once or at an interval, with a time zone(switched on by an admin)
  • When a record is created, changed or deleted(switched on by an admin)

Steps

  • Find, create, update, delete and archive a record(switched on by an admin)
  • In-app notification and e-mail(switched on by an admin)e-mail needs a mail setup
  • Loop over records and helper steps(switched on by an admin)
  • Conditions with and/or groups(switched on by an admin)
  • External API call(switched on by an admin)
  • Teams invite(needs another module or service)Microsoft 365
  • AI assistant step and transcription(needs another module or service)an AI provider

Safety and operations

  • Dry run(switched on by an admin)
  • Run as a chosen persona(switched on by an admin)
  • All-or-nothing runs, time limit and retries(switched on by an admin)
  • Warnings about loops and cascades(switched on by an admin)
  • Monitor, step logs and self-repair(switched on by an admin)
  • Sharing with employees and roles(switched on by an admin)

Try core3 at your own address.

Set up a test environment for your company, such as yourcompany.core3.digital, and explore the modules from the inside.

Try the demo