Skip to main content

Automation settings, team, audit log and AI pages

Automation's own settings — your name, the workspace's name in Automation — the Team page and its roles, API keys for running flows from your systems, the audit log, the AI pages and the plan bar.

M
Monfri Team
Updated ·4 min read

Most of what governs Automation is set in the Hub — people, roles, plan and billing. Automation itself has a few pages.

Settings

  • Profile — your First Name and Last Name as Automation shows them; the Email comes from your Monfri account. Save Changes.
  • Project Settings — the workspace's name inside Automation (Project Name) and its Project ID. Renaming here does not rename the workspace in the Hub.
  • Danger Zone — This workspace is managed by your Monfri account and can't be deleted here. Deleting the workspace is done in the Hub: Cancel, export or delete.

Team

Team lists who can open Automation in this workspace and their role. People and roles come from your Monfri workspace — to add someone or change what they can do, follow Members in Monfri: Service access.

Role In Automation
Owner, Admin Everything in Automation.
Editor Creates, changes, publishes and runs flows, and manages connections.
Viewer Sees flows and runs, with customers' personal data hidden. Cannot change or run anything.

API Keys

An API key lets your own systems run flows and read their runs — a form on your site, a back-office script. Owners and admins make them.

  1. API Keys → Create API Key.
  2. A Name, the Scopes — Read (list flows, read a flow and its runs) and Execute (run a flow) — and, if you like, an Expiration (optional).
  3. Create Key. The key is shown once: Copy your API key now. You won't be able to see it again!

A key acts as the person who made it, in this workspace only: if their role drops to Viewer, it can no longer run flows; if they lose access, it stops working. Rotate key gives a new one and stops the old at once; Revoke key ends it.

Calls go to https://auto.monfri.net/api/v1, with the header Authorization: Bearer <your key>:

Call Scope Does
GET /projects/{projectId}/flows Read the flows — the Project ID is on Settings
GET /flows/{flowId} Read one flow
GET /flows/{flowId}/runs and GET /flows/{flowId}/runs/{runId} Read its runs
POST /flows/{flowId}/run with {"input": {…}} Execute runs it now; the steps read the values as {{trigger.input.…}}; the answer has the run's runId

Any other call with a key is refused. A run started this way counts like any other: Usage and limits.

Audit Logs

Audit Logs records every change in Automation — who, what and when: flows created, changed, published, switched on and off, deleted; connections; members and roles; settings; and the AI's work (Agent Started, Agent Completed, Approval Requested and the rest).

Filter by Action and Resource Type; Clear filters shows everything. View details on a line shows what exactly changed and from which IP Address.

AI Usage, AI Runs, Knowledge Base

The AI the workspace's flows used, the requests of Monfri's AI chat, and the documentation the AI builder may read: AI in Automation.

The plan bar

A bar at the top of every page says when the plan affects Automation:

  • Over the plan limit: … Nothing is blocked. — amber, for owners and admins, with See plans: Usage and limits.
  • Your Monfri trial has ended, Payment is overdue or Your Monfri plan has ended — automations and sending are paused until a plan is active. — red: nothing runs, nothing sends, and you can keep editing. Manage plan goes to billing: Plans, the trial and read-only.
  • This workspace is suspended. Contact [email protected].

If something doesn't work

I changed my name, but the Hub shows the old one

Automation keeps its own copy. Change your name in the Hub for the rest of Monfri: Your profile.

Someone is missing from Team

They have no access to Automation in the Hub, or have not opened Automation yet — a person appears after their first visit.

API keys can list flows, read a flow and its runs, and run a flow — nothing else

The call is not one of the five a key may make. Use the calls in the table above.

Invalid or expired API key

The key is wrong, revoked or past its Expiration. Create a new one.

The person who made this API key is no longer here — create a new key

Its maker lost access to the workspace. Someone who has access creates a new key.

More in Settings

Help

Recipes: ready-made automations

What a recipe is made of, where you find the recipes, what each card state means, which recipe e-mails count as marketing, and the settings that apply to all of them.

Read →
Help

Launch, test, pause and stop a recipe

A recipe's page step by step — its settings, launching, the test e-mail, the discount code, pausing, resuming, re-activating after a change, and removing it.

Read →
Help

What each recipe needs before it can send

The services, the data from your shop and your site, the sender and the discount codes the recipes depend on — and the recipes that need something extra or do not send yet.

Read →
Help

A recipe's results: the funnel, revenue and how it is counted

The results on a recipe's page — the eight tiles, the funnel from audience to order, engagement and deliverability, people between messages, recent runs — and exactly how orders and clicks are counted.

Read →
Help

Welcome recipes: new contacts, sign-ups and first orders

The four recipes that greet new people and turn them into first-time buyers — welcome series, registered but never purchased, first-purchase converter and newsletter signup welcome — with their timing, settings and codes.

Read →
Help

Abandonment recipes: carts, checkouts, products and browsing

The six recipes that bring back shoppers who left — abandoned cart, abandoned checkout, product, category and browse abandonment and high intent — with their audience, timing, push reminders, settings and codes.

Read →

Didn't find your answer?

Write to us and tell us what you were trying to do.