Automations

Automations starts an approved assistant in the background without an open chat. An incoming email, authenticated webhook, or schedule can trigger the run. Each automation belongs to one assistant and one defined instruction.

Before starting, meinGPT checks the execution user and current workspace membership. The assistant receives only its approved tools and that user’s permissions. Sender rules and limits for frequency and parallel runs bound execution. Expected tool evidence shows whether the intended action actually took place.

Every start creates its own history with status, timestamps, result, and errors. Repeated failures or insufficient credit can pause the automation automatically. For a deliberately started, multi-step process, a workflow remains the better form. Automations is in private beta and should be used only for narrowly defined, inspectable tasks.