Automations
Workflows learned from the assistant or designed by the AI team. The browser is only one possible runtime – the same automation can run live with the user, headless in the background, or fully via APIs.
Runs in the employee's browser via the assistant – with the user watching and confirming.
Runs on the server in a headless browser. Works for web apps without an API.
Runs fully server-side against APIs and databases – preferred whenever an API exists.
Whenever a supplier record changes, the API worker loads the record, evaluates the Supplier Policy with the LLM and writes the compliance status back – no browser involved.
Every weekday morning a headless browser signs in to the Supplier Portal, completes missing master data from supplier documents, checks the Supplier Policy and saves the record.
Guides buyers through creating a supplier: reads the form, pulls data from uploaded documents, checks the policy and saves.
Creates the customer in CRM and ERP from the signed order form and notifies the account owner.
Fills missing account fields in the CRM from the Key Account Overview and recent emails.
Mixed workflow: loads approved suppliers via API, maps them with the LLM, enters them in the legacy ERP screen (no API) and asks Finance for approval.